[GitHub] [cloudstack] DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server
DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server URL: https://github.com/apache/cloudstack/issues/3954#issuecomment-604027611 fixed by #3973 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server
DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server URL: https://github.com/apache/cloudstack/issues/3954#issuecomment-599602320 issue with that last solution is that the target to depend on may be different: it may be mariadb or mysql or mysqld depnding on distribution used. maybe solve is docs after all :( 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server
DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server URL: https://github.com/apache/cloudstack/issues/3954#issuecomment-599593507 @rvalle @rhtyd @andrijapanicsb I've read up on systemd a bit; 1. `If unit1 has the directive After=unit2, then if both units are run, unit2 will be executed fully before unit1 starts.` 1. `If unit1 has Wants=unit2 as a dependency, when unit1 is run, unit2 will be run as well. But whether unit2 starts successfully does not affect unit1 running successfully.` I think we can leverage the two to make sure that if mysql is installed on the same server it will be properly schedule to start before and shutdown after cloudstack. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server
DaanHoogland commented on issue #3954: Cloudstack Management Improper shutdown - causes mgmt to not start after reboot of server URL: https://github.com/apache/cloudstack/issues/3954#issuecomment-599581774 @rvalle How do you want to proceed this? I can imagine a wait in the automation scripts could help as well as a dependency in the systemd configuration. That last one however could lead to a system fault as the dependency does not have to exist locally on the host. Have you given this any thought over the weekend? I am open to any solution if it works with your automation (and doesn't destroy the rest of the world). 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
