[Linux-cluster] Cluster issues

punit_j punit_j at rediffmail.com
Wed Jun 25 18:53:43 UTC 2008


  
 Hi All,

I have installed zimbra mailbox server in 2+1 cluster. I am facing following issues while configuring Redhat cluster suite: -

2 services -
mb1-cluster.ku.edu.kw
mb2-cluster.ku.edu.kw

 I have only IP and mount points which are used using LABEL assigned to them. When i reboot all the 3 nodes mount points dont come up and i am getting following errors in log file. Attached is the cluster.conf for reference and also below are logs mentioned : -

These logs are on 1st node : -

Jun 25 11:13:15 mb1 clurgmgrd[14825]: Resource Group Manager Starting
Jun 25 11:13:15 mb1 clurgmgrd[14825]: Loading Service Data
Jun 25 11:13:17 mb1 clurgmgrd[14825]: Initializing Services
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: /dev/sdh1 is not mounted
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-BACKUP with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-BACKUP returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-STORE with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-STORE returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-DBDATA with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-DBDATA returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-CONF with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-CONF returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-REDOLOG with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-REDOLOG returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-INDEX with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-INDEX returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-LOG with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-LOG returned 2 (invalid argument(s))
Jun 25 11:13:17 mb1 clurgmgrd: [14825]: stop: Could not match LABEL=MB2-TEST-CLUST with a real device
Jun 25 11:13:17 mb1 clurgmgrd[14825]: stop on fs:MB2-CLUSTER returned 2 (invalid argument(s))
Jun 25 11:13:22 mb1 clurgmgrd: [14825]: /dev/sdg1 is not mounted
Jun 25 11:13:27 mb1 clurgmgrd: [14825]: /dev/sdf1 is not mounted
Jun 25 11:13:33 mb1 clurgmgrd: [14825]: /dev/sde1 is not mounted
Jun 25 11:13:38 mb1 clurgmgrd: [14825]: /dev/sdd1 is not mounted
Jun 25 11:13:43 mb1 clurgmgrd: [14825]: /dev/sdc1 is not mounted
Jun 25 11:13:45 mb1 rgmanager: clurgmgrd startup failed
Jun 25 11:13:48 mb1 clurgmgrd: [14825]: /dev/sdb1 is not mounted
Jun 25 11:13:53 mb1 clurgmgrd: [14825]: /dev/sda1 is not mounted
Jun 25 11:13:58 mb1 clurgmgrd[14825]: Services Initialized
Jun 25 11:14:01 mb1 clurgmgrd[14825]: Logged in SG "usrm::manager"
Jun 25 11:14:01 mb1 clurgmgrd[14825]: Magma Event: Membership Change
Jun 25 11:14:01 mb1 clurgmgrd[14825]: State change: Local UP
Jun 25 11:14:01 mb1 clurgmgrd[14825]: State change: mbstandby.ku.edu.kw UP
Jun 25 11:14:03 mb1 clurgmgrd[14825]: Magma Event: Membership Change
Jun 25 11:14:03 mb1 clurgmgrd[14825]: State change: mb2.ku.edu.kw UP

On STANDBY NODE

forgot to add standby server logs: -

Jun 25 11:13:26 mbstandby clurgmgrd[15850]: Resource Group Manager Starting
Jun 25 11:13:26 mbstandby clurgmgrd[15850]: Loading Service Data
Jun 25 11:13:27 mbstandby clurgmgrd[15850]: Initializing Services
Jun 25 11:13:27 mbstandby clurgmgrd: [15850]: /dev/sdl1 is not mounted
Jun 25 11:13:27 mbstandby clurgmgrd: [15850]: /dev/sdp1 is not mounted
Jun 25 11:13:32 mbstandby clurgmgrd: [15850]: /dev/sdk1 is not mounted
Jun 25 11:13:32 mbstandby clurgmgrd: [15850]: /dev/sdn1 is not mounted
Jun 25 11:13:38 mbstandby clurgmgrd: [15850]: /dev/sdj1 is not mounted
Jun 25 11:13:38 mbstandby clurgmgrd: [15850]: /dev/sdo1 is not mounted
Jun 25 11:13:43 mbstandby clurgmgrd: [15850]: /dev/sdi1 is not mounted
Jun 25 11:13:43 mbstandby clurgmgrd: [15850]: /dev/sdm1 is not mounted
Jun 25 11:13:47 mbstandby sshd(pam_unix)[17583]: session opened for user root by (uid=0)
Jun 25 11:13:48 mbstandby clurgmgrd: [15850]: /dev/sdd1 is not mounted
Jun 25 11:13:48 mbstandby clurgmgrd: [15850]: /dev/sdh1 is not mounted
Jun 25 11:13:53 mbstandby clurgmgrd: [15850]: /dev/sdg1 is not mounted
Jun 25 11:13:53 mbstandby clurgmgrd: [15850]: /dev/sdc1 is not mounted
Jun 25 11:13:56 mbstandby rgmanager: clurgmgrd startup failed
Jun 25 11:13:58 mbstandby clurgmgrd: [15850]: /dev/sdf1 is not mounted
Jun 25 11:13:58 mbstandby clurgmgrd: [15850]: /dev/sdb1 is not mounted
Jun 25 11:14:04 mbstandby clurgmgrd: [15850]: /dev/sde1 is not mounted
Jun 25 11:14:04 mbstandby clurgmgrd: [15850]: /dev/sda1 is not mounted
Jun 25 11:14:09 mbstandby clurgmgrd[15850]: Services Initialized
Jun 25 11:14:09 mbstandby clurgmgrd[15850]: Logged in SG "usrm::manager"
Jun 25 11:14:09 mbstandby clurgmgrd[15850]: Magma Event: Membership Change
Jun 25 11:14:09 mbstandby clurgmgrd[15850]: State change: Local UP
Jun 25 11:14:12 mbstandby clurgmgrd[15850]: Magma Event: Membership Change
Jun 25 11:14:12 mbstandby clurgmgrd[15850]: State change: mb1.ku.edu.kw UP
Jun 25 11:14:13 mbstandby clurgmgrd[15850]: Resource groups locked; not evaluating
Jun 25 11:14:14 mbstandby clurgmgrd[15850]: Magma Event: Membership Change
Jun 25 11:14:14 mbstandby clurgmgrd[15850]: State change: mb2.ku.edu.kw UP
Jun 25 11:49:22 mbstandby sshd(pam_unix)[9438]: session opened for user root by (uid=0)

Can anyone help me in this issue. Its really urgent. So request you for help. 





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20080625/bc21f700/attachment.htm>
-------------- next part --------------
<?xml version="1.0"?>
<cluster alias="KU-CLUSTER" config_version="26" name="KU-CLUSTER">
	<fence_daemon post_fail_delay="0" post_join_delay="8"/>
	<clusternodes>
		<clusternode name="mb1.ku.edu.kw" votes="1">
			<fence>
				<method name="1">
					<device name="MB1-FENCE"/>
				</method>
			</fence>
		</clusternode>
		<clusternode name="mb2.ku.edu.kw" votes="1">
			<fence>
				<method name="1">
					<device name="MB1-FENCE"/>
				</method>
			</fence>
		</clusternode>
		<clusternode name="mbstandby.ku.edu.kw" votes="1">
			<fence>
				<method name="1">
					<device name="MB1-FENCE"/>
				</method>
			</fence>
		</clusternode>
	</clusternodes>
	<cman/>
	<fencedevices>
		<fencedevice agent="fence_ilo" hostname="10.10.1.102" login="Administrator" name="MB1-FENCE" passwd="YTRFARYM744"/>
	</fencedevices>
	<rm log_facility="local4" log_level="7">
		<failoverdomains>
			<failoverdomain name="mb1-cluster.ku.edu.kw" ordered="1" restricted="1">
				<failoverdomainnode name="mb1.ku.edu.kw" priority="1"/>
				<failoverdomainnode name="mbstandby.ku.edu.kw" priority="2"/>
			</failoverdomain>
			<failoverdomain name="mb2-cluster.ku.edu.kw" ordered="1" restricted="1">
				<failoverdomainnode name="mbstandby.ku.edu.kw" priority="2"/>
				<failoverdomainnode name="mb2.ku.edu.kw" priority="1"/>
			</failoverdomain>
		</failoverdomains>
		<resources>
			<ip address="10.10.1.98" monitor_link="1"/>
			<ip address="10.10.1.80" monitor_link="1"/>
			<fs device="LABEL=MB1-test-CLUST" force_fsck="0" force_unmount="1" fsid="55679" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw" name="MB1-CLUSTER" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-STORE" force_fsck="0" force_unmount="1" fsid="57530" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/store" name="MB1-STORE" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-REDOLOG" force_fsck="0" force_unmount="1" fsid="46961" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/redolog" name="MB1-REDOLOG" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-BACKUP" force_fsck="0" force_unmount="1" fsid="29649" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/backup" name="MB1-BACKUP" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-CONF" force_fsck="0" force_unmount="1" fsid="59576" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/conf" name="MB1-CONF" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-LOG" force_fsck="0" force_unmount="1" fsid="29992" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/log" name="MB1-LOG" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-INDEX" force_fsck="0" force_unmount="1" fsid="57292" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/index" name="MB1-INDEX" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB1-DBDATA" force_fsck="0" force_unmount="1" fsid="18112" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb1-cluster.ku.edu.kw/db/data" name="MB1-DBDATA" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-test-CLUST" force_fsck="0" force_unmount="1" fsid="58810" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw" name="MB2-CLUSTER" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-LOG" force_fsck="0" force_unmount="1" fsid="4088" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/log" name="MB2-LOG" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-INDEX" force_fsck="0" force_unmount="1" fsid="50513" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/index" name="MB2-INDEX" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-REDOLOG" force_fsck="0" force_unmount="1" fsid="35764" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/redolog" name="MB2-REDOLOG" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-CONF" force_fsck="0" force_unmount="1" fsid="39446" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/conf" name="MB2-CONF" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-STORE" force_fsck="0" force_unmount="1" fsid="64039" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/store" name="MB2-STORE" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-DBDATA" force_fsck="0" force_unmount="1" fsid="16675" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/db/data" name="MB2-DBDATA" options="noatime" self_fence="1"/>
			<fs device="LABEL=MB2-BACKUP" force_fsck="0" force_unmount="1" fsid="29746" fstype="ext3" mountpoint="/opt/test-cluster/mountpoints/mb2-cluster.ku.edu.kw/backup" name="MB2-BACKUP" options="noatime" self_fence="1"/>
		</resources>
		<service autostart="0" domain="mb1-cluster.ku.edu.kw" exclusive="1" name="mb1-cluster.ku.edu.kw" recovery="restart">
			<ip ref="10.10.1.98">
				<fs ref="MB1-CLUSTER"/>
				<fs ref="MB1-STORE"/>
				<fs ref="MB1-REDOLOG"/>
				<fs ref="MB1-BACKUP"/>
				<fs ref="MB1-CONF"/>
				<fs ref="MB1-LOG"/>
				<fs ref="MB1-INDEX"/>
				<fs ref="MB1-DBDATA"/>
			</ip>
		</service>
		<service autostart="0" domain="mb2-cluster.ku.edu.kw" exclusive="1" name="mb2-cluster.ku.edu.kw" recovery="restart">
			<ip ref="10.10.1.80">
				<fs ref="MB2-CLUSTER"/>
				<fs ref="MB2-LOG"/>
				<fs ref="MB2-INDEX"/>
				<fs ref="MB2-REDOLOG"/>
				<fs ref="MB2-CONF"/>
				<fs ref="MB2-DBDATA"/>
				<fs ref="MB2-STORE"/>
				<fs ref="MB2-BACKUP"/>
			</ip>
		</service>
	</rm>
</cluster>


More information about the Linux-cluster mailing list