Oracle Solaris Cluster (MOSC)

MOSC Banner

OSC Common Agent Container Key Synchronizer fails to start

edited Mar 13, 2020 3:54PM in Oracle Solaris Cluster (MOSC) 12 commentsAnswered ✓

I've recently updated an OSC 4.4 environment running on Solaris 11.4 LDOMs and following patching and rebooting the CDOMs the cluster comes up showing both nodes as members and the resource group comes online on the second node, but svc:/system/cluster/sckeysync:default stays in needs maintenance state on the primary node and cluster check -v on both hosts fails stating each cannot connect to the other.

I've tried the work around of generating new keys using cacaoadm and then copying them across to the other machine and I've even tried rebooting both nodes again, but the issue remains the same and I cannot switch the resourcegroup from the node it's running on to the other one - this is an NFS service and it keeps hanging/looping trying to start statd. I did get it to come online on the primary node, weirdly by rebooting it, though it took far longer than expected.

Tagged:

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center