[Linux-cluster] Service won't relocate after yum updates
Randy Brown
randy.brown at noaa.gov
Thu Dec 6 15:44:24 UTC 2007
Correction: "but the nfs service will failover" should read "but the
nfs service will not failover" Sorry.
Randy
Randy Brown wrote:
> I just ran `yum update` on one of the nodes in my two node cluster and
> now the nfs service won't relocate to the updated node. Here are the
> versions of relevant packages on each node:
>
> Node 1 (updated node)
> [root at nfs1-cluster ~]# rpm -qa |grep -e cman -e lvm -e gfs -e
> rgmanager -e kernel
> kmod-gfs-0.1.16-6.2.6.18_8.1.15.el5
> lvm2-2.02.26-3.el5
> kmod-gfs-0.1.19-7.el5_1.1
> gfs-utils-0.1.12-1.el5
> system-config-lvm-1.0.22-1.0.el5
> cman-2.0.73-1.el5_1.1
> lvm2-cluster-2.02.26-1.el5
> rgmanager-2.0.31-1.el5.centos
> gfs2-utils-0.1.38-1.el5
> kernel-2.6.18-53.1.4.el5
> kernel-2.6.18-8.1.15.el5
> kernel-headers-2.6.18-53.1.4.el5
>
> Node 2
> [root at nfs2-cluster ~]# rpm -qa |grep -e cman -e lvm -e gfs -e
> rgmanager -e kernel
> gfs2-utils-0.1.25-1.el5
> kmod-gfs-0.1.16-5.2.6.18_8.1.14.el5
> kmod-gfs-0.1.16-6.2.6.18_8.1.15.el5
> system-config-lvm-1.0.22-1.0.el5
> cman-2.0.64-1.0.1.el5
> rgmanager-2.0.24-1.el5.centos
> gfs-utils-0.1.11-3.el5
> lvm2-2.02.16-3.el5
> lvm2-cluster-2.02.16-3.el5
> kernel-2.6.18-8.1.14.el5
> kernel-2.6.18-8.1.15.el5
> kernel-headers-2.6.18-8.1.15.el5
>
> The cluster will start on the new machine but the nfs service will
> failover to it as it did prior to the upgrade. The messages I see in
> /var/log/messages are:
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> Member 2
> shutting down
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> Starting
> stopped service service:nfs
> Dec 6 10:14:08 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> start on
> nfsclient "fs-shared-client" returned 2 (invalid argument(s))
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <warning> #68: Failed to
> start service:nfs; return value: 1
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> Stopping
> service service:nfs
> Dec 6 10:14:08 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "rfcdata-client" returned 2 (invalid argument(s))
> Dec 6 10:14:08 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:08 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "fs-shared-client" returned 2 (invalid argument(s))
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <notice> Service
> service:nfs is recovering
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <warning> #71:
> Relocating failed service service:nfs
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <notice> Stopping
> service service:nfs
> Dec 6 10:14:09 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "rfcdata-client" returned 2 (invalid argument(s))
> Dec 6 10:14:09 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "fs-shared-client" returned 2 (invalid argument(s))
> Dec 6 10:14:09 nfs1-cluster clurgmgrd[4455]: <notice> Service
> service:nfs is stopped
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> Starting
> stopped service service:nfs
> Dec 6 10:14:47 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> start on
> nfsclient "fs-shared-client" returned 2 (invalid argument(s))
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <warning> #68: Failed to
> start service:nfs; return value: 1
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> Stopping
> service service:nfs
> Dec 6 10:14:47 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "rfcdata-client" returned 2 (invalid argument(s))
> Dec 6 10:14:47 nfs1-cluster clurgmgrd: [4455]: <err> No export path
> specified.
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> stop on
> nfsclient "fs-shared-client" returned 2 (invalid argument(s))
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <notice> Service
> service:nfs is recovering
> Dec 6 10:14:47 nfs1-cluster clurgmgrd[4455]: <warning> #71:
> Relocating failed service service:nfs
> Dec 6 10:14:49 nfs1-cluster clurgmgrd[4455]: <notice> Service
> service:nfs is now running on member 2
>
> The export path in the nfsclient resource box, when using
> system-config-cluster, is marked optional and it has not been a
> problem leaving that blank in the past. Has something regarding this
> changed?
>
> Thanks in advance for any assistance,
>
> Randy
>
> Cluster.conf:
> [root at nfs1-cluster cluster]# cat cluster.conf
> <?xml version="1.0"?>
> <cluster alias="ohd_cluster" config_version="120" name="ohd_cluster">
> <fence_daemon post_fail_delay="0" post_join_delay="60"/>
> <clusternodes>
> <clusternode name="nfs1-cluster.nws.noaa.gov"
> nodeid="1" votes="1">
> <fence>
> <method name="1">
> <device name="nfspower"
> port="8" switch="1"/>
> </method>
> </fence>
> </clusternode>
> <clusternode name="nfs2-cluster.nws.noaa.gov"
> nodeid="2" votes="1">
> <fence>
> <method name="1">
> <device name="nfspower"
> port="7" switch="1"/>
> </method>
> </fence>
> </clusternode>
> </clusternodes>
> <cman expected_votes="1" two_node="1"/>
> <rm>
> <failoverdomains>
> <failoverdomain name="nfs-failover" ordered="0"
> restricted="1">
> <failoverdomainnode
> name="nfs1-cluster.nws.noaa.gov" priority="1"/>
> <failoverdomainnode
> name="nfs2-cluster.nws.noaa.gov" priority="1"/>
> </failoverdomain>
> </failoverdomains>
> <resources>
> <ip address="140.90.91.244" monitor_link="1"/>
> <clusterfs
> device="/dev/VolGroupFS/LogVol-shared" force_unmount="0" fsid="30647"
> fstype="gfs" mountpoint="/fs/shared" name="fs-shared" options="acl"/>
> <nfsexport name="fs-shared-exp"/>
> <nfsclient name="fs-shared-client"
> options="no_root_squash,rw" path="" target="140.90.91.0/24"/>
> <clusterfs
> device="/dev/VolGroupTemp/LogVol-rfcdata" force_unmount="0"
> fsid="54233" fstype="gfs" mountpoint="/rfcdata" name="rfcdata"
> options="acl"/>
> <nfsexport name="rfcdata-exp"/>
> <nfsclient name="rfcdata-client"
> options="no_root_squash,rw" path="" target="140.90.91.0/24"/>
> </resources>
> <service autostart="1" domain="nfs-failover" name="nfs">
> <clusterfs ref="fs-shared">
> <nfsexport ref="fs-shared-exp">
> <nfsclient
> ref="fs-shared-client"/>
> </nfsexport>
> </clusterfs>
> <ip ref="140.90.91.244"/>
> <clusterfs ref="rfcdata">
> <nfsexport ref="rfcdata-exp">
> <nfsclient ref="rfcdata-client"/>
> </nfsexport>
> <ip ref="140.90.91.244"/>
> </clusterfs>
> </service>
> </rm>
> <fencedevices>
> <fencedevice agent="fence_apc" ipaddr="192.168.42.30"
> login="rbrown" name="nfspower" passwd="Tele4m32"/>
> </fencedevices>
> </cluster>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
-------------- next part --------------
A non-text attachment was scrubbed...
Name: randy_brown.vcf
Type: text/x-vcard
Size: 313 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20071206/d93de6d2/attachment.vcf>
More information about the Linux-cluster
mailing list