This is possibly due to
- The database encountered an error and is unable to be rebuilt.
- The database is not rebuilding, but has stopped and needs to be restarted.
- Other system problems.
Check is any process stuck in Zombi state by using the below command
ps aufx | grep cpservice
root 1663 91.0 0.0 0 0 ? Zl
You can try to kill this kind of PID and check if it works?
The ps aufx output is like :
root 22937 0.0 0.0 2884 572 S+ ....... \_grep cpservice
root 21747 0.0 0.0 186292 6652 Ss ...... /usr/bin/perl /usr/local/bin/cpservicectl
root 5942 28.1 1.3 3664932 428992 Dl ....... \_ /usr/local/ess/cpserviced /usr/local/ess
root 26540 0.0 0.0 44688 13256 S ...... \_ /usr/bin/perl /etc/rc.d/rc6.d/K50cpservice stop
Could you describe this? Thanks.
Looks normal, what did the support team said about it??
I my experience with ESM upgrades it's best to just wait and don't rush things. Depending on the size of the database the rebuild might take some time.
Yes, in your case you might have an issue but waiting one hour it really isn't that much :-)
If you need some help with which commands to fix this we can help you.
First support said : "do not kill the services" then i sent them the output about messages,NitroErrorlog he said that yes you could kill the cpserviced and dbserverd.
I've killed them and rebooting has started but 15 minutes no changes have occured. We powered off the the system through the VM console and powered on again. 1 night later finally we could log in successfully.
My experience about that wait 1-2 hours but if anything there are no changes kill the services (cpservice, dbserverd)