Hi team,

I have checked with my hosting team and they confirmed that the database for the environment is Maria DB 10.4.18 . This MariaDB version is the latest and a drop-in replacement/equivalent for MySQL 5.7
But in the Drupal upgrade status page i see see the following error

When using MySQL/Percona, minimum version is 5.7.8 Once updated to at least 5.6, you can also install the MySQL 5.6 driver for Drupal 9 for now.

Thanks
Divya

CommentFileSizeAuthor
#4 status-report.png135.52 KBdivya.lakshman
#2 upgrade-status.png230.29 KBdivya.lakshman
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

divya.lakshman created an issue. See original summary.

divya.lakshman’s picture

divya.lakshman CreditAttribution: divya.lakshman commented
FileSize
upgrade-status.png230.29 KB
Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia commented

What does the regular site status page show?

divya.lakshman’s picture

divya.lakshman CreditAttribution: divya.lakshman commented
FileSize
status-report.png135.52 KB
divya.lakshman’s picture

divya.lakshman CreditAttribution: divya.lakshman commented

Hi any update on this.

mglaman’s picture

mglaman
Primary language English
Location WI, USA
CreditAttribution: mglaman at Bluehorn Digital for Palantir.net commented
Status: Active » Postponed (maintainer needs more info)

With my testing it seems to work fine. However, it requires that the version is returned correctly. EDIT: I was on D9, not D8. Maybe a regression of #3213533: Fix incorrect MariaDB version reports when used in Drupal 8? See if your database is returning the correct version. And that you have latest 3.x Upgrade Status

The code in upgrade_status is based on the code from here (D8 compatible, since code is in D9): https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Database%...

      // MariaDB may prefix its version string with '5.5.5-', which should be
      // ignored.
      // @see https://github.com/MariaDB/server/blob/f6633bf058802ad7da8196d01fd19d75c53f7274/include/mysql_com.h#L42.
      $regex = '/^(?:5\\.5\\.5-)?(\\d+\\.\\d+\\.\\d+.*-mariadb.*)/i';
      preg_match($regex, $version, $matches);

Basically, if the version returned is failing that regular expression, it will not be detected as MariabDB.

Maybe your hosting team is obfuscating the database version.

mglaman’s picture

mglaman
Primary language English
Location WI, USA
CreditAttribution: mglaman at Bluehorn Digital for Palantir.net commented
Related issues: +#3213533: Fix incorrect MariaDB version reports when used in Drupal 8

Related issue #3213533: Fix incorrect MariaDB version reports when used in Drupal 8

divya.lakshman’s picture

divya.lakshman CreditAttribution: divya.lakshman commented
Status: Postponed (maintainer needs more info) » Fixed
mglaman’s picture

mglaman
Primary language English
Location WI, USA
CreditAttribution: mglaman at Bluehorn Digital for Palantir.net commented

@divya.lakshman glad to know it was fixed! Are you able to share any insight as to why it was mis-reported? So we can help anyone else who has this same issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Nayan Arora’s picture

Nayan Arora CreditAttribution: Nayan Arora commented

Can you tell how it fixed. I am getting same error

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy at Acquia commented

If you are sure that your MySQL version is correct, then I am not sure this need fixing, as long as Drupal itself will understand your correct MySQL version when upgrading, you should be fine. Upgrade Status is reporting this issue as something to look at, but it does not limit its capabilities based on MySQL version and does not block you from doing the upgrade. (It is a reporting and developer tool). I think it would be great to fix MySQL version reporting if it is still a problem but you can also ignore it for now if you are sure it is misreported.

Nayan Arora’s picture

Nayan Arora CreditAttribution: Nayan Arora commented

I still facing this problem on updating my database. I just migrated to drupal 9 from 8. When I tried to run update.php. Its giving me this error. Error: https://prnt.sc/iUiMMnbGxx0P
I am using pantheon and updated my database in pantheon.yml file and chat with pantheon support too. They told me database updated on that specific environment. I don't know now why it's not reflecting in my drupal site.