DCO 7.4.5 cluster upgrade to 7.5 required manual node restarts

[DCIM_Support]

Hi guys,

I have performed DCO 7.4.5 -> 7.5.0 upgrade today.

All seemed to have gone OK during the upgrade procedure and the last entry to upgrade log was:

....however nothing changed after that and after 30 min STATUS page was still showing red errors and services did not start.

I have then restarted both VM nodes manually (poweroff and start from vSphere) after which all came back to normal and I can log into DCO 7.5.0 client without any issues.

I did notice however that the STATUS page is now indicating that the slave node database is offline...

so I have rebooted the slave node now and it came back clean:

I will monitor tomorrow and update this post accordingly...happy to hear back from anyone if similar issues were experienced elsewhere and also happy to provide server logs tomorrow.

(CID:97485274)

[DCIM_Support]

Hi Lukasz,

Thank you for sharing your findings. It sounds and seems like it should be ok.

Depending on the nature of the solution (not necessarily size) +30 min upgrade time on the first node is not uncommon (we have seen 60 min). There is a number of upgrade steps that are performed one the first node and therefore the upgrade time can be longer than normal on the first node (second node should be the same as normal). It is very hard to put a number to "normal" in this case since it is depending on the solution that is being upgraded.

To be sure that nothing is wrong please share your log files. The red indicators in Webmin during the upgrade is not expected and therefore we would have a quick look. Please share log files gather from Webmin.

/Søren

(CID:97485495)

[DCIM_Support]

Hi Soren,

I may have not been precise enough in my description.
"Database Status  Offline " message on slave node appeared next day after the initial upgrade was done.

I have just checked and it is reporting the same status again:

I think we might need to investigate the logs as you indicated.
It is a Pre-PROD environment and it appears to be working perfectly fine from the DCO Client perspective so I will share the logs on Monday.

(CID:97485503)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.