Cannot mount: Management node communication failed

[maj...@gmail.com]

Hello,
I'm a newbie in the FhGFS world.
We have a running FhGFS installation. I'm trying to mount the filesystem on one node which has a different setup as the other nodes that already can mount the FhGFS.

I'm getting always
Management node communication failed: meta01

For instance:
# fhgfs-check-servers
Management
==========
Management node communication failed: meta01

# fhgfs-ctl --listnodes --nodetype=meta --details
Management node communication failed: meta01

# fhgfs-ctl --listnodes --nodetype=storage --details
Management node communication failed: meta01

# fhgfs-net
df: â/scratchâ: Remote I/O error
No active FhGFS mounts found.

But the filesystem is reported to be mounted:
# mount |grep fhgfs
fhgfs_nodev on /scratch type fhgfs (rw,cfgFile=/etc/fhgfs/fhgfs-client.conf,_netdev)

I am a bit lost. It would be great if someone can give me a hint...
Best

[ReDuX]

Hi,

Is "meta01" reachable by the Clients?

ping? nslookup?

[maj...@gmail.com]

Hello,
Thanks for the answer.
Sorry for not being more informative. I think I have tried the obvious things. And of course the server is reachable:

# ping meta01
PING meta01 (10.141.240.1) 56(84) bytes of data.
64 bytes from meta01 (10.141.240.1): icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=2 ttl=64 time=0.124 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=3 ttl=64 time=0.127 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=4 ttl=64 time=0.136 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=5 ttl=64 time=0.175 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=6 ttl=64 time=0.135 ms
64 bytes from meta01 (10.141.240.1): icmp_seq=7 ttl=64 time=0.135 ms
^C
--- meta01 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6000ms
rtt min/avg/max/mdev = 0.106/0.134/0.175/0.019 ms

and

# nslookup meta01
Server:         10.141.255.252
Address:        10.141.255.252#53

Name:   meta01
Address: 10.141.240.1

I can also access the server via ssh with public key.

Do I have to somehow tell the server about the client? I have not seen that in the documentation, but obviously I'm missing something here...

Best

[maj...@gmail.com]

The issue is fixed.
The problem was caused by missmatching versions of the packages: the server was running 2012.10.r15 and I had installed 2014.01-2014.01.r12 on the client side. Now, with the 2012 version on the client plus a couple of patches I got it working.
Best.