check you PM
You’ve already messed it up enough by being impatient. Don’t make the same mistake over and over again.
The problem is resolved.
-
The container was restarting every 6 minutes because PMS wasn’t responding to Health Check.
-
Resolution was to
– move the DBs (in their entirety) to a native linux installation
(remove the container as the root of the problem)
– Without starting PMS – Clean up the DB so PMS itself operated better (dbrepair optimized)
– Upgrade that machine to 1.40.2 and let PMS perform the normal schema updates.
(about 5 minutes)
– Move the fully upgraded databases back to the container.
– Start the container
EDIT: TL;DR: The container constantly restarting itself prevented the upgrade from completing. Ticket submitted to Engineering but may not be actionable due to the nature of container Health Checks.
Thank you Chuck! Appreciate your outstanding help.
How’s it doing after running overnight?
Still working great. No downtime or issues. Search is running snappier as well & media is loading quicker.
Thanks again!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.