This content has been marked as final. Show 6 replies
CACAO is used for the Solaris Cluster Manager GUI and by the cluster check command. It isn't vital for cluster operation.
I'm not sure what caused this. It's usually something like adding new s/w, like directory servers, or patching. It can be a little tricky to fix and I don't have a procedure to do this. I've run into similar situations before, but have the luxury of being able to re-install or pkgrm/pkgadd the packages.
Thanks for your reply.
Where can I find current versions of those packages for reinstall?
On the latest Solaris 10 media. However, there may be patches that update these!
In my case the problem was the initial memory size.
In the file
I changed the initial memory pool from
and cleared the service.
Thanks D.Rock. That change to cacao.properties worked for me.
(Our trouble occurred after applying Recommended Patch Bundle -- hate when that happens. :)
After two days, after debugging all cacao scripts, I finally managed to find the reason for the service not starting for us. File */etc/cacao/private/install.properties* was empty. it should contain
Hope this can help someone else.
# cat /etc/cacao/private/install.properties cacao.install.id=common-agent-container-1