Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mfschunk cannot connect #74

Closed
zhs077 opened this issue Sep 29, 2017 · 8 comments

Comments

@zhs077
Copy link

commented Sep 29, 2017

master log:

Sep 29 16:57:28 mfsmaster[14326]: chunkserver disconnected - ip: 127.0.0.1.129 / port: 9422, usedspace: 3273105408 (3.05 GiB), totalspace: 35080790593536 (32671.53 GiB)
Sep 29 16:57:28 mfsmaster[14326]: server ip: 127.0.0.1.129 / port: 9422 has been fully removed from data structures
Sep 29 16:57:33 mfsmaster[14326]: chunkserver register begin (packet version: 6) - ip: 127.0.0.1.129 / port: 9422, usedspace: 3273105408 (3.05 GiB), totalspace: 35080790593536 (32671.53 GiB)
Sep 29 16:57:33 mfsmaster[14326]: connection with CS(127.0.0.1.129) has been closed by peer
Sep 29 16:57:33 mfsmaster[14326]: chunkserver disconnected - ip: 127.0.0.1.129 / port: 9422, usedspace: 3273105408 (3.05 GiB), totalspace: 35080790593536 (32671.53 GiB)
Sep 29 16:57:33 mfsmaster[14326]: server ip: 127.0.0.1.129 / port: 9422 has been fully removed from data structures
Sep 29 16:57:38 mfsmaster[14326]: chunkserver register begin (packet version: 6) - ip: 127.0.0.1.129 / port: 9422, usedspace: 3273105408 (3.05 GiB), totalspace: 35080790593536 (32671.53 GiB)
Sep 29 16:57:38 mfsmaster[14326]: connection with CS(127.0.0.1.129) has been closed by peer
Sep 29 16:57:38 mfsmaster[14326]: chunkserver disconnected - ip: 127.0.0.1.129 / port: 9422, usedspace: 3273105408 (3.05 GiB), totalspace: 35080790593536 (32671.53 GiB)
Sep 29 16:57:38 mfsmaster[14326]: server ip: 127.0.0.1.129 / port: 9422 has been fully removed from data structures

chunkservice log
Sep 29 16:34:33 mfschunkserver[10803]: connecting ...
Sep 29 16:34:33 mfschunkserver[10803]: connected to Master
Sep 29 16:34:33 mfschunkserver[10803]: MATOCS_MASTER_ACK - wrong meta data id. Can't connect to master
Sep 29 16:34:38 mfschunkserver[10803]: connecting ...
Sep 29 16:34:38 mfschunkserver[10803]: connected to Master
Sep 29 16:34:38 mfschunkserver[10803]: MATOCS_MASTER_ACK - wrong meta data id. Can't connect to master

@xandrus

This comment has been minimized.

Copy link
Member

commented Sep 29, 2017

Hi,
Are you sure that you are connecting to correct master server?
This is protection to avoid connecting wrong chunkserevr to different MooseFS instance.

If you are 100% sure that this chunkserver was connected to this specific master server you can remove this files:
/var/lib/mfs/chunkserverid.mfs
and
/mnt/[hdd mount point]/.metaid file.
I mean .metaid file from all hard disks defined in /etc/mfs/mfshdd.cfg file

Please remember that if chunkserver was connected to different master all chunks will be treated as "unknown" and deleted.

@zhs077

This comment has been minimized.

Copy link
Author

commented Sep 29, 2017

I not found /var/lib/mfs this dir ,
/mnt/mfs/ dir not found .metaid and mfshdd.cfg file

@zhs077

This comment has been minimized.

Copy link
Author

commented Sep 29, 2017

old master server is down, and I use a new master server

@xandrus

This comment has been minimized.

Copy link
Member

commented Sep 29, 2017

Hi,
I mean hard disk defined in /etc/mfs/mfshdd.cfg file.

chunkserverid.mfs file should be in MooseFS chunkserver metadata path (DATA_PATH parameter in mfschunkserer.cfg file)

@zhs077

This comment has been minimized.

Copy link
Author

commented Sep 30, 2017

thank you, I've solved it

@suntabu

This comment has been minimized.

Copy link

commented Nov 8, 2018

Hi,
I wanna deploy two masters with one instance for HA got the same error.

only one master running at the same time, once it's down, another backup master would handle the master work.
Could this be done? @xandrus
What should I do to keep two masters running properly?

@xandrus

This comment has been minimized.

Copy link
Member

commented Nov 8, 2018

Hi,
Basically, if you want to use two or more master servers( MooseFS HA) you have to install all the components in the pro version.
Then you should add two A entries to your DNS server which should resolve mfsmaster name to two different IP addresses. Something like this:

mfsmaster IN A 192.168.1.1
mfsmaster IN A 192.168.1.2

And this is it.

Please remember that PRO version is not for free.

@suntabu

This comment has been minimized.

Copy link

commented Nov 8, 2018

OK, thanks for your info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.