Solaris Cluster 4.1 node reboot, second node panic with a metaclust error "Could not re-initialise rpc.mdcommd for set"
Last updated on MARCH 27, 2017
Applies to:Solaris Cluster - Version 4.1 to 4.1 [Release 4.1]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Solaris Cluster node panics when the other node is rebooted. The cluster uses SVM Multi-owner metaset.
The error below can be seen in /var/adm/messages:
Multi-owner metaset named data was just created.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms