dstack-usage no longer working / error saving account to
cloud_usage db
Hi Rohit,
thanks!
Having a recent DB backup at hand and only based on guesses, I did some
further experiments yesterday :)
- Rerun /usr/share/cloudstack-common/scripts/util/migrate-
dynamicroles.py
- Checked cloudstack-usage 4.8
Hi Rohit,
thanks!
Having a recent DB backup at hand and only based on guesses, I did some
further experiments yesterday :)
- Rerun /usr/share/cloudstack-common/scripts/util/migrate-
dynamicroles.py
- Checked cloudstack-usage 4.8.0.1 instead of 4.9
- Updated back to cloudstack-usage 4.9
... and ma
Hi Stephan,
In cloud_usage.account `role_id` can be NULL as there is no user of this field
within the usage server. In cloud.account, the `role_id` should be
automatically populated/migrated when you upgraded. From your shared db query
result, I'm not sure if that's a select query on cloud.acc
role_id in account table shouldn't be null. If the upgrade was
successful, it should have updated it with proper mapping from
account type. (check the db upgrade log for any exceptions)
I suggest you do the update manually following the logic at
https://github.com/apache/cloudstack/blob/4.9/engine
Hi!
We've recently noticed cloudstack-usage is no longer able to write
usage data into mysql. I assume this happened after updateing to
4.8.0.1 or 4.9 - we missed that error in our testsetup...
Here's the usage.log: http://pastebin.com/Zpvnw4xX
Finally it fails with following message:
ERROR [us
