SuperCluster: SSCtuner in maintenance state
(Doc ID 2658228.1)
Last updated on JANUARY 27, 2022
Applies to:
Oracle SuperCluster Specific Software - Version 2.x and laterInformation in this document applies to any platform.
Symptoms
o. Unable to start SSCtuner - review of log shows that it timed out
svcs -xv
State: maintenance since Fri Apr 10 07:31:05 2020
Reason: Start method failed repeatedly, last died on Killed (9).
See: http://support.oracle.com/msg/SMF-8000-KS
See: /opt/oracle.supercluster/ssctuner/README
See: /var/svc/log/site-application-sysadmin-ssctuner:default.log
Impact: This service is not running.
o. Log:
site-application-sysadmin-ssctuner:default.log
-----------------------------------------------
[ 2020 Apr 10 07:30:05 Executing start method ("/opt/oracle.supercluster/ssctuner/ssctuner.ksh start"). ]
...
[ 2020 Apr 10 07:31:05 Method or service exit timed out. Killing contract 397. ] ====> here
[ 2020 Apr 10 07:31:05 Method "start" failed due to signal KILL. ]
-----------------------------------------------
[ 2020 Apr 10 07:30:05 Executing start method ("/opt/oracle.supercluster/ssctuner/ssctuner.ksh start"). ]
...
[ 2020 Apr 10 07:31:05 Method or service exit timed out. Killing contract 397. ] ====> here
[ 2020 Apr 10 07:31:05 Method "start" failed due to signal KILL. ]
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |