Repository navigation
|
During management server 4.23 installation I followed these steps to install the whole thing as I have followed these to install cloudstack-management 4.22 mentioned below: Here is the Java version which is required for cloudstack-management 4.23 mentioned in the docs Following these steps I have encountered this error when I run Give me any kind of suggestions or solutions to resolve this issue. |
Answered by
arpanbht
Nov 2, 2026
Replies: 4 comments 1 reply
|
Hi @arpanbht , The first thing I'd check here is whether the database already contains the A couple of things stood out in your command history. You ran I'd suggest checking a few things before making any database changes. 1. Confirm which database server you're running: mysql --versionAlso run this inside MySQL: SELECT VERSION(), @@version_comment;Are you using Oracle MySQL 8.0 or MariaDB? This distinction is worth checking. I've seen a similar CloudStack error reported previously where switching from MariaDB to MySQL resolved it. 2. Check whether the index already exists: SHOW INDEX FROM cloud.hypervisor_capabilities;You can also check the complete table definition: SHOW CREATE TABLE cloud.hypervisor_capabilities\GLook for 3. A few more details would help:
I'd also check whether the CloudStack APT repository is pointing specifically to the 4.23 repository rather than mixing packages from different releases. I wouldn't drop the existing index or recreate the database just yet. First, let's understand why the upgrade script is trying to create an index that MySQL says is already present. I've also been working with Apache CloudStack deployments and testing management server configurations in cloud environments, so I'm interested in understanding what combination of database and package versions is causing this. If you can share the outputs above, we can narrow it down without risking unnecessary database changes. Regards, |
0 replies
|
cloudstack-setup-databases was run more than once. Drop database completely, restaret the process |
0 replies
|
line 13 and line 24 do that failure (line 24) line 13 you did not define explicit options (some defaults apply) and line 24 was not needed and is what broke DB Then repeat 13 OR 24...... keep us looped |
1 reply
|
Hello @andrijapanicsb , Thanks for clarifying this. The repeated database setup commands stood out in the history, but I wasn't sure whether the second execution was the actual cause. Your explanation makes sense, especially since the initial command already initialized the database and the second one was unnecessary. I'll keep an eye on the discussion to see whether the fresh database setup resolves the issue. Appreciate you taking the time to explain what went wrong. Regards, |
|
Hey @RyanAccuWebCloud , @andrijapanicsb Thank you for helping. This time I followed the official docs same to same and it worked 🙌. Actually I was altering the mysql db and creating a |
0 replies
Answer selected by
arpanbht
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @RyanAccuWebCloud , @andrijapanicsb Thank you for helping.
This time I followed the official docs same to same and it worked 🙌.
Actually I was altering the mysql db and creating a
root userbefore running thecloudstack-setup-databasescommand, but this time I did not run the root user creation command instead I directly run the cloudstack-setup-databases command from the doc i.e.cloudstack-setup-databases cloud:cloud@localhost --deploy-as=root:rootpassword -e file -m ManagementSecretKey123 -k DbSecretKey123 -i 192.168.2.11