[Linux-cluster] RHCS for RHEL3 Resource temporarily unavailable
Filipe Miranda
filipe.miranda at gmail.com
Tue Apr 18 20:33:13 UTC 2006
Hello,
We have a Red Hat Cluster Suite for Red Hat Enteprise Linux 3. After one
month, the master host cluster (node1) service was interrupted.
This is what shows in the file /var/log/messages:
Apr 13 16:05:06 Node1 clumembd[3222]: <warning> sending broadcast
message failed Resource temporarily unavailable
Apr 13 16:05:29 Node1 last message repeated 32 times
Apr 13 16:06:31 Node1 clumembd[3222]: <warning> sending broadcast
message failed Resource temporarily unavailable
This is the cluster config file:
cluster.xml
<?xml version="1.0" ?>
- <#> <cluconfig version="*3.0*">
<clumembd broadcast="*yes*" interval="*750000*" loglevel="*5*" multicast
="*no*" multicast_ipaddress="" thread="*yes*" tko_count="*20*" />
<cluquorumd loglevel="*5*" pinginterval="*4*" tiebreaker_ip="" />
<clurmtabd loglevel="*5*" pollinterval="*4*" />
<clusvcmgrd loglevel="*7*" />
<clulockd loglevel="*7*" />
<cluster config_viewnumber="*1*" key="*814109fd98a521c9e33618045d42b97o*"name
="Cluster_A" />
<sharedstate driver="*libsharedraw.so*" rawprimary="*/dev/raw/raw1*"rawshadow
="*/dev/raw/raw2*" type="*raw*" />
- <#> <members>
<member id="*0*" name="*node1*" watchdog="*no*" />
<member id="*1*" name="node2" watchdog="*no*" />
</members>
- <#> <services>
- <#> <service checkinterval="*30*" failoverdomain="*Local*"
id="*0*"maxfalsestarts
="*0*" maxrestarts="*15*" name="*script01*" userscript="">
- <#> <service_ipaddresses>
<service_ipaddress broadcast="*101.168.192.255*" id="*0*" ipaddress="*
101.168.192.162*" netmask="*255.255.255.0*" />
</service_ipaddresses>
- <#> <device id="*0*" name="*/dev/vol01/lv01*" sharename="">
<mount forceunmount="*yes*" fstype="*ext3*" mountpoint="*/opt/*share"options
="" />
</device>
</service>
</services>
- <#> <failoverdomains>
- <#> <failoverdomain id="*0*" name="*Local*" ordered="*no*" restricted="*
no*">
<failoverdomainnode id="*0*" name="*node1*" />
<failoverdomainnode id="*1*" name="node2" />
</failoverdomain>
</failoverdomains>
</cluconfig>
Any ideas what is going on? what seems to be the problem?
The RHEL3 is on U4, so is the RHCS.
Did we do anything wrong in this configuration? Suggestions?
I would appreciate any help.
Regards,
FTM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20060418/b6390a1d/attachment.htm>
More information about the Linux-cluster
mailing list