Red Hat Cluster suite 5 question

[Steven E. Protter]

Shalom,

To reset ilo to factory defaults.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=845909

SEP

[Alex Ng Chong Yau]

Hi all,

Is this normal when i configure hp-ilo on the same segment with the public ip. When press the power button on node 1, the node when down and few seconds later the node power up by itself and the service only failover to node 2.

[Ivan Ferreira · Accepted solution]

I think it is, as when you power down node 1, node 2 will try to fence it. By default, fence_ilo reboots the server, according to man fence_ilo, there is an option to power down the server instead of restarting.

And yes, it will failover to node 2, and unless you configure a failover group with priotiy, will stay there.

[Alex Ng Chong Yau]

Hi Ivan,

I have man the fence_ilo. It the descrition it say's that fence_ilo -0 is to set the option, But where should i set it, just open a teminal and set it or do i need to hard code it somewhere? e.g cluster config file / fence_ilo script.

[Alex Ng Chong Yau]

After changing the action from reboot to off in fence_ilo script, now when press the power button the service able to failover. If the power cable have been plug out then the service wont failover. is this the limitation for fence_ilo.?

[Ivan Ferreira]

Yes, as the remaining node cannot confirm that the other was fenced. You can then configure other fence device, as brocade if you use sanswitch.

[Alex Ng Chong Yau]

Facing another problem here. Base on the /var/log/messages log show that after 30 mins the cluster service restart the application by itself an return error code 1. how do i debug this error message.



error log

Mar 28 07:25:15 BA-GW1 clurgmgrd: [4751]: script:MDCS_QUERY_SERVICE: status of /etc/init.d/queryService failed (returne
d 1)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: status on script "MDCS_QUERY_SERVICE" returned 1 (generic error)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Stopping service service:MDCS_QUERY_SERVICE
Mar 28 07:25:15 BA-GW1 clurgmgrd: [4751]: script:MDCS_GATEWAY_SERVICE: status of /etc/init.d/mdcs failed (returned 1)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: status on script "MDCS_GATEWAY_SERVICE" returned 1 (generic error)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Stopping service service:MDCS_GATEWAY_SERVICE
Mar 28 07:25:15 BA-GW1 clurgmgrd: [4751]: script:MDCS_DBLOADER_SERVICE: status of /etc/init.d/dbloader failed (returned
1)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: status on script "MDCS_DBLOADER_SERVICE" returned 1 (generic error)
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Service service:MDCS_QUERY_SERVICE is recovering
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Stopping service service:MDCS_DBLOADER_SERVICE
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Service service:MDCS_GATEWAY_SERVICE is recovering
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Recovering failed service service:MDCS_QUERY_SERVICE
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Service service:MDCS_DBLOADER_SERVICE is recovering
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Recovering failed service service:MDCS_GATEWAY_SERVICE
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Service service:MDCS_QUERY_SERVICE started
Mar 28 07:25:15 BA-GW1 clurgmgrd[4751]: Recovering failed service service:MDCS_DBLOADER_SERVICE
Mar 28 07:25:16 BA-GW1 clurgmgrd[4751]: Service service:MDCS_GATEWAY_SERVICE started
Mar 28 07:25:16 BA-GW1 clurgmgrd[4751]: Service service:MDCS_DBLOADER_SERVICE started



Attach also is a sample script of a script is use to start the application.

[Ivan Ferreira]

script:MDCS_QUERY_SERVICE: status of /etc/init.d/queryService failed (returne
d 1)


You must identify why the status part of the script is not returning 0. Run the script manually outside red hat cluster suite and ensure that you always get exit code 0.

[Alex Ng Chong Yau]

Sorry posted the old script. Here attach is the new script that is use with cluster.

[Alex Ng Chong Yau]

My script actually locate in /etc/init.d. When it run with cluster the service restarted by itself after 30mins or less. Have try to run the script without using the cluster, it seems everything is normal and it does not stop or restart and there is no error. Took out the script from /etc/init.d, place it in another directory and run with cluster the service restarted by itself after 22mins.