nxsbi commented on issue #10780: URL: https://github.com/apache/cloudstack/issues/10780#issuecomment-2833619700
ok, I think I found the issue, posting here for everyone's benefit. On looking further, I realized that the file /etc/cloudstack/usage/db.properties and /etc/cloudstack/usage/key were physical files and not pointed to the management db.properties. I deleted the existing files and recreated them as a symlink. After this the usage server started. Not sure if this is a bug, but I did not have this issue in my first management server. ``` sudo rm /etc/cloudstack/usage/db.properties sudo rm /etc/cloudstack/usage/key sudo ln -s /etc/cloudstack/management/db.properties db.properties sudo ln -s /etc/cloudstack/management/key key ``` One thought before Closing the issue -- There does not seem to be a way to confirm via metadata or UI that the second Usage server is up and running. I understand that only one usage server will run the batches, but it would be good to be able to confirm that the second is on standby? -- 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]
