Oracle Solaris Cluster (MOSC)

MOSC Banner

prevent GDS from sending SIGKILL

edited Jan 16, 2013 4:56PM in Oracle Solaris Cluster (MOSC) 5 commentsAnswered
Hi Cluster Experts, 

Is it possible to prevent GDS from sending a SIGKILL when the stop method of a resource fails ?

The corresponding application should not get a SIGKILL when a SIGTERM does not succeed and the expected behaviour is that the resource comes in status STOP_FAILED.

I get the following message on the console:
Jan  9 18:05:19 x-hv214 SC[,SUNW.gds:6,xxx-rg,yyy-res,gds_svc_stop]: [ID 606362 daemon.error] The stop command </opt/SUNCscbcm/bin/control_bcm -R yyy-res -G xxx-rg -M bcm stop> failed to stop the application. Will now use SIGKILL to stop the application.

Thanks !

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center