MatthiasDrexler commented on issue #10068: URL: https://github.com/apache/cloudstack/issues/10068#issuecomment-2529769973
> @MatthiasDrexler Did you find the root cause ? I don't think so. It seems that it is possible to leave the database in an invalid state by rebooting or restarting cloudstack-management during the migration. If I run cloudstack-setup-management directly after cloudstack-setup-databases, I do not have any problems. All in all in retrospective, I had several independent problems during the last two days: - invalid value/config in db.properties (503 as a result with connection error in logs) - mentioned reboot/restart problem (503 as a result with sql error in logs) - impatience during the migration (no response without error in logs) At some time, I lost the track in desperation. But since, I managed to reproduce point 2 with several attempts using different OSes, I think that the migration transactions have some blank spaces. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
