scstat: unexpected error , sc 3.2

UNIX Solaris
1

Hello,

Looks like cluster nodes are completely messed up. I had configured mysql resource as failover group using smf.proxy.failover and it looked okay so I 'init 6' one node, other node somehow hung and when both were reset, both have problems .

-bash-3.00# scstat -g

-bash-3.00# svcs -xv

-bash-3.00# ps -ef

dmesg and cluster status are here :
pastebin - Stuff - post number 1505764

Forgot to mention the OS is solaris x86_64 - with latest patches

This is pretty much scene on both the nodes.

Last thing, i don't want to do is reinstall or do everything from scratch, so could someone please help?

Thank you in advance.

---------- Post updated at 09:24 AM ---------- Previous update was at 09:14 AM ----------

if i type scstat instead of scstat -g

-bash-3.00# scstat

---------- Post updated at 09:41 AM ---------- Previous update was at 09:24 AM ----------

svcadm clear cl-svc-enable

2

Hi,
it seems your first reboot after cconfig of your cluster.
did you try to get it up one by one. lets see its behavior.
get up only tommy_sun1.

Good luck

3

Hello Samar,

No - not first reboot after initial cluster install-configuration
Yes- first reboot after the mysql failover resources were configured

I can try only one node as you said, I will post update soon. Sorry for the delay.

Thanks

---------- Post updated at 09:02 AM ---------- Previous update was at 08:52 AM ----------

Only booted tommy_sun1, but still status is same as earlier. Now I am wondering if a patch for sun cluster messed up the things
svc:/system/cluster/cl-svc-enable:default (Enabling the cluster userland services)
State: maintenance since Mon Jul 27 08:47:59 2009
Reason: Completes a dependency cycle.
See: Sun Message ID: SMF-8000-HP
Impact: 25 dependent services are not running:
svc:/system/cluster/ql_upgrade:default
svc:/system/cluster/mountgfs:default
svc:/system/cluster/clusterdata:default
svc:/system/cluster/ql_rgm:default
svc:/system/zones:default
svc:/system/cluster/pnm:default
svc:/system/cluster/rgm-starter:default
svc:/application/management/common-agent-container-1:default
svc:/system/cluster/cl-svc-cluster-milestone:default
svc:/system/cluster/sc_svtag:default
svc:/system/cluster/sckeysync:default
svc:/system/cluster/scsymon-srv:default
svc:/system/cluster/scslmclean:default
svc:/system/cluster/sc_pnm_proxy_server:default
svc:/system/cluster/rpc-fed:default
svc:/system/cluster/sc_zones:default
svc:/system/cluster/scprivipd:default
svc:/system/cluster/cznetd:default
svc:/system/cluster/rpc-pmf:default
svc:/system/cluster/sc_zc_member:default
svc:/system/cluster/scdpm:default
svc:/system/cluster/cl-event:default
svc:/system/cluster/cl-eventlog:default
svc:/system/cluster/cl-ccra:default
svc:/system/cluster/scqdm:default

svc:/network/cswmysql5:default (?)
State: uninitialized since Mon Jul 27 08:47:59 2009
Reason: Restarter svc:/system/cluster/sc_restarter:default has not initialized service state.
See: Sun Message ID: SMF-8000-4D
Impact: 6 dependent services are not running:
svc:/milestone/multi-user:default
svc:/application/management/common-agent-container-1:default
svc:/milestone/multi-user-server:default
svc:/system/basicreg:default
svc:/system/zones:default
svc:/system/iscsitgt:default

4

So you're getting something here ?
Clustering - scstat: unexpected error , sc 3.2

5

not this time :b: