The svcadm enable command does not turn on when forcefully turned on.
[root@sj-cluster1:~]#svcs -xv
svc:/system/sstore:default (Statistics Store Daemon)
State: offline* transitioning to online since 2023-01-05T16:53:40
Reason: Start method is running.
See: http://support.oracle.com/msg/SMF-8000-C4
See: man -M /usr/share/man -s 7 ssid
See: man -M /usr/share/man -s 1 sstore
See: man -M /usr/share/man -s 8 sstored
See: /var/svc/log/system-sstore:default.log
Impact: 3 dependent services are not running:
svc:/system/sysstat:default
svc:/system/install/telemetry-manager:files
svc:/system/install/telemetry-manager:stats
svc:/system/cluster/manager:default (Oracle Solaris Cluster Manager)
State: maintenance since 2023-01-05T16:55:40
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://support.oracle.com/msg/SMF-8000-KS
See: /var/svc/log/system-cluster-manager:default.log
Impact: This service is not running.
svc:/system/cluster/manager-wls:default (SOLARIS CLUSTER MANAGER - WLS)
State: offline* transitioning to online since 2023-01-05T16:56:15
Reason: Start method is running.
See: http://support.oracle.com/msg/SMF-8000-C4
See: /var/svc/log/system-cluster-manager-wls:default.log
Impact: This service is not running.
Your best bet here would be to look at the log files that these service status messages are telling you to look at, and see what you find in them. SMF is aware that these clustering services are not running, but to find out more details about exactly why they're not, you'll need to look at those log files and see what they say.
A cluster comprises two or more nodes in a HA (High availability) configuration. It treats data storage as the essential resource and treats CPUs as a commodity. There are many interdependent processes.
If you imagine a two node cluster (the simplest that you can have) and you start one node from cold, cluster processes will wait until it sees the second node is up. Therefore you will notice that processes seem to be just "waiting around" for something to happen. You can call that 'offline' is you like.
However, this shouldn't be happening:
but is not an uncommon occurance. Cluster services once failed can lock themselves out until cleared.
