GitHub user rongage closed a discussion: New install - 4.19.1 on Centos Stream
9, database upgrade fails.
# ISSUE TYPE
* Bug Report
# COMPONENT NAME
~~~
Core startup
~~~
# CLOUDSTACK VERSION
~~~
4.19.1
~~~
# CONFIGURATION
Separate database server:
mysql> sel
GitHub user DaanHoogland closed the discussion with a comment: New install -
4.19.1 on Centos Stream 9, database upgrade fails.
closed this for lack of interaction, please reopen or open a new item if
applicable
GitHub link:
https://github.com/apache/cloudstack/discussions/9913
GitHub user weizhouapache added a comment to the discussion: New install -
4.19.1 on Centos Stream 9, database upgrade fails.
@rongage
I have tested with latest MariaDB-server 11.6.2, it works
```
curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash
dnf install MariaDB
GitHub user weizhouapache added a comment to the discussion: New install -
4.19.1 on Centos Stream 9, database upgrade fails.
I tested mariadb-server 10.6.18-0ubuntu0.22.04.1, it worked well.
10.6.18 is a more recent release (released in May 2024) than 10.5.22 (released
in August 2023)
can
GitHub user DaanHoogland added a comment to the discussion: New install -
4.19.1 on Centos Stream 9, database upgrade fails.
@rongage , centos stream is not explicitely supported by ACS. I do not know how
far forked it is from the likes of Oracle Linux 9, Alma Linux 9 and Rocky Linux
9
you have been one of the unfortunate ones with the recent database upgrade
> problem I have stumbled across a possible solution...at least in my case.
>
> Looking a little closer at the logs it seems there was some sort of java
> disconnect triggering the DB upgrade issue so I dec
Yep, see this Issue:
https://github.com/apache/cloudstack/issues/3826
-Original Message-
From: Robert Ward
Sent: Wednesday, January 22, 2020 9:42 PM
To: [email protected]
Subject: Update for those having database upgrade issues recently
Hello,
If you have been one of the
Hello,
If you have been one of the unfortunate ones with the recent database upgrade
problem I have stumbled across a possible solution...at least in my case.
Looking a little closer at the logs it seems there was some sort of java
disconnect triggering the DB upgrade issue so I decided to
cker
> > 2013-09-24 02:23:48,145 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> > (Timer-1:null) Grabbing lock to check for database upgrade.
> > 2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
> > Checking to see if the database is at a version befo
l) Running SystemIntegrityChecker databaseUpgradeChecker
> 2013-09-24 02:23:48,145 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
> Checking to see if the database is at a
check for database upgrade.
2013-09-24 02:23:48,147 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null)
Checking to see if the database is at a version before it was the version
table is created
2013-09-24 02:23:48,154 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(Timer-1:null) DB version = 4.1.1 Code
11 matches
Mail list logo
