On Wed, Jul 21, 2004 at 09:54:36AM +0800, chloong wrote: > hi, > i checked the dmesg, the error is : > lock_gulm: fsid=cluster1:gfs1: Exiting gulm_mount with errors -111 > GFS: can't mount proto = lock_gulm, table = cluster1:gfs1, hostdata = > where as in /var/log/messages the error is : > lock_gulm: ERROR Got a -111 trying to login to lock_gulmd. Is it > runni > ng? > lock_gulm: ERROR cm_login failed. -111 > lock_gulm: ERROR Got a -111 trying to start the threads. > lock_gulm: fsid=cluster1:gfs1: Exiting gulm_mount with errors -111 > GFS: can't mount proto = lock_gulm, table = cluster1:gfs1, hostdata = > i got 2 nodes in the gfs cluster. 1 is the lock_gulm server and the > other one is not. > the one that not a lock_gulm server giving me mount error... > Did i need to start the lock_gulm daemon on this server that is not > the lock_gulm server? yes, you need to start lock_gulmd on every node. > When i start the lock_gulmd on this server it gave me this error in > /var/log/messages: > lock_gulmd: You are running in Standard mode. > lock_gulmd: I am (clu2.abc.com) with ip (192.168.11.212) > lock_gulmd: Forked core . > lock_gulmd_core: ERROR [core_io.c:1029] Got error from reply: > (clu1:192. > 168.11.211) 1006:Not Allowed it might be marked expired. do a 'gulm_tool nodelist clu1' that will list what state gulm thinks each node is in. If it is marked expired, and given your ccs config, you'll need to complete the fence manual action. (erm, i forget how that's done, man pages should tell.) -- Michael Conrad Tadpol Tilstra The Grand Illusion: "I am in control!"
Description: PGP signature