[Linux-cluster] Strange behaviour of the services in cluster!!

[Alex aka Magobin]

Hi, I configured as first Service in cluster a DNS....it works fine and
from cluster console I can move service from serverA to ServerB without
problem.
According with documentation I've configured Apache...exactly !
The problem is that with 2 services in cluster I'm not able to switch
they from server to another server anymore...Console say thats this is
an error...but there isn't any error in /var/log/messages..only a
warning #70

NOTICE that if I disabled a service and then restart to other server,
services run correctly...(both services), but if I want to switch on the
fly...doesn't work!...It seems that Dns hung up !

any help is greatly appreciated!

Alex

below...tail -40 /var/log/messages trying to start DNS from serverB to
ServerA while apache is running on serverA:



Mar 10 10:24:57 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named status 
Mar 10 10:25:14 nodo2 clurgmgrd[2569]: <notice> Stopping service dns 
Mar 10 10:25:14 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named stop 
Mar 10 10:25:14 nodo2 named[13926]: shutting down: flushing changes
Mar 10 10:25:14 nodo2 named:  succeeded
Mar 10 10:25:14 nodo2 named[13926]: stopping command channel on
127.0.0.1#953
Mar 10 10:25:14 nodo2 named[13926]: no longer listening on 127.0.0.1#53
Mar 10 10:25:14 nodo2 named[13926]: no longer listening on
10.23.5.253#53
Mar 10 10:25:14 nodo2 named[13926]: no longer listening on
10.23.5.240#53
Mar 10 10:25:14 nodo2 named[13926]: no longer listening on
192.168.254.3#53
Mar 10 10:25:14 nodo2 named[13926]: exiting
Mar 10 10:25:14 nodo2 clurgmgrd: [2569]: <info> Removing IPv4 address
10.23.5.240 from eth0 
Mar 10 10:25:24 nodo2 clurgmgrd: [2569]: <info> unmounting san:/SAN/DNS
(/var/named) 
Mar 10 10:25:24 nodo2 clurgmgrd[2569]: <notice> Service dns is stopped 
Mar 10 10:25:24 nodo2 clurgmgrd[2569]: <warning> #70: Attempting to
restart service dns locally. 
Mar 10 10:25:24 nodo2 clurgmgrd[2569]: <notice> Starting stopped service
dns 
Mar 10 10:25:24 nodo2 clurgmgrd: [2569]: <info> Adding IPv4 address
10.23.5.240 to eth0 
Mar 10 10:25:25 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named start 
Mar 10 10:25:25 nodo2 named: Avvio named succeeded
Mar 10 10:25:25 nodo2 named[14145]: starting BIND 9.2.4 -u named
-t /var/named/chroot
Mar 10 10:25:25 nodo2 named[14145]: using 1 CPU
Mar 10 10:25:25 nodo2 named[14145]: loading configuration from
'/etc/named.conf'
Mar 10 10:25:25 nodo2 named[14145]: listening on IPv4 interface lo,
127.0.0.1#53
Mar 10 10:25:25 nodo2 named[14145]: listening on IPv4 interface eth0,
10.23.5.253#53
Mar 10 10:25:25 nodo2 named[14145]: listening on IPv4 interface eth0,
10.23.5.240#53
Mar 10 10:25:25 nodo2 named[14145]: listening on IPv4 interface eth1,
192.168.254.3#53
Mar 10 10:25:25 nodo2 clurgmgrd[2569]: <notice> Service dns started 
Mar 10 10:25:25 nodo2 named[14145]: command channel listening on
127.0.0.1#953
Mar 10 10:25:25 nodo2 named[14145]: zone 5.23.10.in-addr.arpa/IN: loaded
serial 199609206
Mar 10 10:25:25 nodo2 named[14145]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 199609206
Mar 10 10:25:25 nodo2 named[14145]: zone linux.testing/IN: loaded serial
199609206
Mar 10 10:25:25 nodo2 named[14145]: running
Mar 10 10:25:56 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named status 
Mar 10 10:26:01 nodo2 crond(pam_unix)[14196]: session opened for user
root by (uid=0)
Mar 10 10:26:03 nodo2 crond(pam_unix)[14196]: session closed for user
root
Mar 10 10:26:26 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named status 
Mar 10 10:26:57 nodo2 clurgmgrd: [2569]: <info>
Executing /etc/init.d/named status 
Mar 10 10:27:58 nodo2 last message repeated 2 times
Mar 10 10:28:01 nodo2 crond(pam_unix)[14526]: session opened for user
root by (uid=0)
Mar 10 10:28:03 nodo2 crond(pam_unix)[14526]: session closed for user
root