Hi Magnus,
I expect the issue is caused by the combination of the AXONIQ_AXONSERVER_STANDALONE environment setting and the fact that you already have an Axon Server controldb in place.
If Axon Server detects a controldb from an older Axon Server SE version, it performs a migration to get the database in the required state, and you do not need the AXONIQ_AXONSERVER_STANDALONE setting. The AXONIQ_AXONSERVER_STANDALONE setting is only needed on a clean installation.
We will investigate how we can prevent this situation leads to a problem, but for now, you can delete the “axonserver-controldb.mv.db” file in the data directory and then restart.
Regards,
Marc
1 Like