There are several steps you can take to restore the system to correct operation. Follow these steps in order:Can't contact objectserver
Log into the system as root.
ps -ef | grep objectserver
You should see three lines of information. At the far right of these columns, you should see the following words:
/usr/Cadmin/bin/objectserver
/usr/Cadmin/bin/objectserver
grep objectserver
The last item is the grep command you just entered, and there should be two separate instances of the objectserver.
chkconfig | grep objectserver
You should see the line:
objectserver on
Suppose the response that you see is:
objectserver off
Then you must turn on the objectserver by entering the command:
chkconfig objectserver on
Then cycle the cadmin init script by issuing the commands:
/etc/init.d/cadmin stop
/etc/init.d/cadmin start
ps -ef | grep objectserver
Check the output to see that both objectserver daemons are running. If both required instances of the objectserver are running, the error message should no longer appear. If you see the message again, go on to the next step.
Can't contact objectserver
The objectserver database may be corrupted. You must stop the objectserver daemons, repair the database and then start the objectserver daemons again with the following commands:
/etc/init.d/cadmin stop
/etc/init.d/cadmin clean
/etc/init.d/cadmin start