Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.35, 10.3.26
-
None
Description
Possibly related to the recent update: https://mariadb.com/kb/en/mariadb-10235-release-notes/
Sites running PHP 5.6 will see this error:
SQLSTATE[HY000]: General error: 1835 Malformed communication packet
|
Sites running PHP 7.0, 7.1, 7.2 will see this error:
Critical Error Could not connect to the database.
|
Setting the sites to use PHP 7.3, solves the issue. So the recent MariaDB update appears to have introduced a DB connection issue for PHP < 7.3 (or anything using PDO)
Another solution is to downgrade. This is also mentioned here: https://xenforo.com/community/threads/mariadb-10-3-26-1-breaks-php-7-2.187331/
Attachments
Issue Links
- includes
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
MDBF-952 Protocol regression testing for the server
-
- Open
-
-
-
- Closed
-
Activity
Since this has been fixed in 10.2.36, 10.3.27 etc - is there an ETA for those being published to Dockerhub mariadb official image ?
MariaDB official images are not maintained by MariaDB, you need to ask the maintainer of the images.
https://github.com/docker-library/mariadb
For all those watching patiently, there have been packages released https://mariadb.org/mariadb-10-5-8-10-4-17-10-3-27-and-10-2-36-now-available/
jliebert with the mariadb release, the docker library official images picked up the release and pushed their release
Since this has been fixed in 10.2.36, 10.3.27 etc - is there an ETA for those being published to the /10.2/, /10.3/ yum repositories? I see the specific version repo is published: http://yum.mariadb.org/10.3.27/centos7-amd64/rpms/ - however, the generic 10.3 repo does not.