[Linux-cluster] CentOS 5.5 RHCS (cluster.conf) apache resource issues

Mark Watts m.watts at eris.qinetiq.com
Wed Jan 26 14:12:54 UTC 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I have a 2-node CentOS 5.5 cluster, with a single service comprising of
an IP address and apache resource.

Starting and stopping rgmanager works fine - the service starts and
stops with no issues.


# service rgmanager start
Jan 26 14:01:56 proxy01 clurgmgrd[5305]: <notice> Resource Group Manager
Starting
Jan 26 14:01:56 proxy01 clurgmgrd[5305]: <info> Loading Service Data
Jan 26 14:02:00 proxy01 clurgmgrd[5305]: <info> Initializing Services
Jan 26 14:02:01 proxy01 clurgmgrd: [5305]: <info> Stopping Service
apache:Public_Proxy_HTTPD
Jan 26 14:02:01 proxy01 clurgmgrd: [5305]: <err> Checking Existence Of
File /var/run/cluster/apache/apache:Public_Proxy_HTTPD.pid
[apache:Public_Proxy_HTTPD] > Failed - File Doesn't Exist
Jan 26 14:02:01 proxy01 clurgmgrd: [5305]: <info> Stopping Service
apache:Public_Proxy_HTTPD > Succeed
Jan 26 14:02:02 proxy01 clurgmgrd[5305]: <info> Services Initialized
Jan 26 14:02:02 proxy01 clurgmgrd[5305]: <info> State change: Local UP
Jan 26 14:02:07 proxy01 clurgmgrd[5305]: <notice> Starting stopped
service service:Public_Proxy
Jan 26 14:02:07 proxy01 clurgmgrd: [5305]: <info> Adding IPv4 address
192.168.0.1/24 to eth0
Jan 26 14:02:11 proxy01 clurgmgrd: [5305]: <info> Starting Service
apache:Public_Proxy_HTTPD
Jan 26 14:02:14 proxy01 clurgmgrd[5305]: <notice> Service
service:Public_Proxy started

# service rgmanager stop
Jan 26 14:02:20 proxy01 rgmanager: [5947]: <notice> Shutting down
Cluster Service Manager...
Jan 26 14:02:20 proxy01 clurgmgrd[5305]: <notice> Shutting down
Jan 26 14:02:20 proxy01 clurgmgrd[5305]: <notice> Shutting down
Jan 26 14:02:20 proxy01 clurgmgrd[5305]: <notice> Stopping service
service:Public_Proxy
Jan 26 14:02:21 proxy01 clurgmgrd: [5305]: <info> Stopping Service
apache:Public_Proxy_HTTPD
Jan 26 14:02:21 proxy01 clurgmgrd: [5305]: <info> Stopping Service
apache:Public_Proxy_HTTPD > Succeed
Jan 26 14:02:22 proxy01 clurgmgrd: [5305]: <info> Removing IPv4 address
192.168.0.1/24 from eth0
Jan 26 14:02:32 proxy01 clurgmgrd[5305]: <notice> Service
service:Public_Proxy is stopped
Jan 26 14:02:32 proxy01 clurgmgrd[5305]: <notice> Shutdown complete, exiting
Jan 26 14:02:32 proxy01 rgmanager: [5947]: <notice> Cluster Service
Manager is stopped.


Starting rgmanager then using clusvcadm to disable/enable/disable the
service fails on the last disable:

# service rgmanager start
Jan 26 13:53:26 proxy01 clurgmgrd[3157]: <notice> Resource Group Manager
Starting
Jan 26 13:53:26 proxy01 clurgmgrd[3157]: <info> Loading Service Data
Jan 26 13:53:31 proxy01 clurgmgrd[3157]: <info> Initializing Services
Jan 26 13:53:33 proxy01 clurgmgrd: [3157]: <info> Stopping Service
apache:Public_Proxy_HTTPD
Jan 26 13:53:33 proxy01 clurgmgrd: [3157]: <err> Checking Existence Of
File /var/run/cluster/apache/apache:Public_Proxy_HTTPD.pid
[apache:Public_Proxy_HTTPD] > Failed - File Doesn't Exist
Jan 26 13:53:33 proxy01 clurgmgrd: [3157]: <info> Stopping Service
apache:Public_Proxy_HTTPD > Succeed
Jan 26 13:53:33 proxy01 clurgmgrd[3157]: <info> Services Initialized
Jan 26 13:53:34 proxy01 clurgmgrd[3157]: <info> State change: Local UP
Jan 26 13:53:39 proxy01 clurgmgrd[3157]: <notice> Starting stopped
service service:Public_Proxy
Jan 26 13:53:39 proxy01 clurgmgrd[3157]: <info> State change:
ukmaboedprp02.mgmt UP
Jan 26 13:53:39 proxy01 clurgmgrd: [3157]: <info> Adding IPv4 address
192.168.0.1/24 to eth0
Jan 26 13:53:44 proxy01 clurgmgrd: [3157]: <info> Starting Service
apache:Public_Proxy_HTTPD
Jan 26 13:53:47 proxy01 clurgmgrd[3157]: <notice> Service
service:Public_Proxy started

# clusvcadm -d Public_Proxy
Jan 26 13:58:46 proxy01 clurgmgrd[3157]: <notice> Stopping service
service:Public_Proxy
Jan 26 13:58:46 proxy01 clurgmgrd: [3157]: <info> Stopping Service
apache:Public_Proxy_HTTPD
Jan 26 13:58:46 proxy01 clurgmgrd: [3157]: <info> Stopping Service
apache:Public_Proxy_HTTPD > Succeed
Jan 26 13:58:47 proxy01 clurgmgrd: [3157]: <info> Removing IPv4 address
192.168.0.1/24 from eth0
Jan 26 13:58:57 proxy01 clurgmgrd[3157]: <notice> Service
service:Public_Proxy is disabled

# clusvcadm -e Public_Proxy
Jan 26 13:59:04 proxy01 clurgmgrd[3157]: <notice> Starting disabled
service service:Public_Proxy
Jan 26 13:59:04 proxy01 clurgmgrd: [3157]: <info> Adding IPv4 address
192.168.0.1/24 to eth0
Jan 26 13:59:09 proxy01 clurgmgrd: [3157]: <info> Starting Service
apache:Public_Proxy_HTTPD
Jan 26 13:59:11 proxy01 clurgmgrd[3157]: <notice> Service
service:Public_Proxy started

# clusvcadm -d Public_Proxy
Jan 26 13:59:19 proxy01 clurgmgrd[3157]: <notice> Stopping service
service:Public_Proxy
Jan 26 13:59:20 proxy01 clurgmgrd: [3157]: <info> Stopping Service
apache:Public_Proxy_HTTPD
Jan 26 13:59:21 proxy01 clurgmgrd: [3157]: <err> Stopping Service
apache:Public_Proxy_HTTPD > Failed - Application Is Still Running
Jan 26 13:59:21 proxy01 clurgmgrd: [3157]: <err> Stopping Service
apache:Public_Proxy_HTTPD > Failed
Jan 26 13:59:21 proxy01 clurgmgrd[3157]: <notice> stop on apache
"Public_Proxy_HTTPD" returned 1 (generic error)
Jan 26 13:59:21 proxy01 clurgmgrd: [3157]: <info> Removing IPv4 address
192.168.0.1/24 from eth0
Jan 26 13:59:31 proxy01 clurgmgrd[3157]: <crit> #12: RG
service:Public_Proxy failed to stop; intervention required
Jan 26 13:59:31 proxy01 clurgmgrd[3157]: <notice> Service
service:Public_Proxy is failed


Anyone got any ideas why this is the case, and where I can look to work
out why I get a failure after an enable/disable cycle?

Regards,

Mark.

- -- 
Mark Watts BSc RHCE
Senior Systems Engineer, MSS Secure Managed Hosting
www.QinetiQ.com
QinetiQ - Delivering customer-focused solutions
GPG Key: http://www.linux-corner.info/mwatts.gpg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk1AK+YACgkQBn4EFUVUIO1XXwCg6YdjpVkOicUllNerjfKtGilf
KawAoPtvfF43Jmrli8zyLCvEozYk+syh
=h5ra
-----END PGP SIGNATURE-----




More information about the Linux-cluster mailing list