Resolved Plesk update fails error 404 mariadb repo

[TrevorM]

Server operating system version

Centos 7

Plesk version and microupdate number

18.0.45 update 2

Dedicated Ionos server with Centos 7
Installed version.
Version 18.0.45 Update #2, last updated on July 26, 2022 04:07 AM

Wanting to update to;

Update to:	Plesk Obsidian 18.0.46

Update in Plesk starts with Plesk Installer Updating.
Then I click on install or update product.
Then I click on Continue.
I again get the Plesk Installer updating message.

Update in Plesk fails with the message;
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Command line Yum update fails with the same message.

Any idea how to fix this please?

regards
Trevor

 

[Dave W]

https://support.plesk.com/hc/en-us/articles/5135895243666-Plesk-and-system-update-fails-http-yum-mariadb-org-10-1-centos7-amd64-repodata-repomd-xml-Errno-14-HTTP-Error-404-Not-Found

 

[TrevorM]

Hi
Many thanks for the reply.

 

[TrevorM]

Hi
Followed the instructions and now get this when trying to restart the database server.
Any idea why this simple process has gone wrong?
systemctl restart mysql
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

 

[Kaspar]

A clue is given in the error message

If you run the # systemctl status mariadb.service command you'll get more detailed information on why starting mysql failed.

 

[TrevorM]

HI
I did but it didn't help me but hopefully someone else will understand it better.
systemctl status mariadb.service
● mariadb.service - MariaDB 10.9.3 database server
Loaded: loaded (/usr/lib/systemd/system/./mariadb.service; disabled; vendor p reset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sat 2022-09-24 15:33:13 BST; 681ms a go
Docs: man:mariadbd(8)
systemd
Process: 9464 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_ WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 9438 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR = || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemc tl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/S UCCESS)
Process: 9436 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START _POSITION (code=exited, status=0/SUCCESS)
Main PID: 9464 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
[trevor@s19362569 ~]$

 

[TrevorM]

journalctl -xe
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Number of transaction pools: 1
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Using Linux native AIO
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: Completed initialization of buffer pool
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
Sep 24 15:39:21 s19362569 named[1885]: client @0x7f1a04114d00 104.35.74.126#7547 (ferc.gov): query (cache) 'ferc.gov/ANY/IN' denied
Sep 24 15:39:21 s19362569 mariadbd[13188]: 2022-09-24 15:39:21 0 [Note] InnoDB: 128 rollback segments are active.
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] InnoDB: log sequence number 11249513860; transaction id 78603240
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] Plugin 'FEEDBACK' is disabled.
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [Note] Server socket created on IP: '127.0.0.1'.
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 22: Invalid argument
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [ERROR] Do you already have another server running on port: 3306 ?
Sep 24 15:39:22 s19362569 mariadbd[13188]: 2022-09-24 15:39:22 0 [ERROR] Aborting
Sep 24 15:39:22 s19362569 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Sep 24 15:39:22 s19362569 systemd[1]: Failed to start MariaDB 10.9.3 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Sep 24 15:39:22 s19362569 systemd[1]: Unit mariadb.service entered failed state.
Sep 24 15:39:22 s19362569 systemd[1]: mariadb.service failed.
Sep 24 15:39:22 s19362569 systemd[1]: Started Plesk Web Socket Service.
-- Subject: Unit plesk-web-socket.service has finished start-up
-- Defined-By: systemd
-- Support: systemd-devel Info Page
--
-- Unit plesk-web-socket.service has finished starting up.
--
-- The start-up result is done.
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: [2022-09-24 15:39:22.647] 13216:632f169a9da50 ERR [panel] DB query failed: SQLSTATE[HY000] [2002] No such file or directory:
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 0: /usr/local/psa/admin/plib/Db/Adapter/Pdo/Mysql.php:79
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: Db_Adapter_Pdo_Mysql->query(string 'SET sql_mode = ''')
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 1: /usr/local/psa/admin/plib/CommonPanel/Application/Abstract.php:103
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: CommonPanel_Application_Abstract::initDbAdapter()
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 2: /usr/local/psa/admin/plib/Session/Helper.php:176
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: Plesk\Session\Helper::initStorage()
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 3: /usr/local/psa/admin/plib/CommonPanel/Application/Abstract.php:52
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: CommonPanel_Application_Abstract->run()
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 4: /usr/local/psa/admin/plib/CommonPanel/Application/Abstract.php:34
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: CommonPanel_Application_Abstract::init()
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 5: /usr/local/psa/admin/plib/pm/Bootstrap.php:16
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: pm_Bootstrap::init()
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 6: /usr/local/psa/admin/plib/sdk.php:11
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: require_once(string '/usr/local/psa/admin/plib/sdk.php')
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: 7: /usr/local/psa/admin/plib/WebSocket/bin/ws-server.php:3
Sep 24 15:39:22 s19362569 sw-engine-pleskrun[13216]: ERROR: Plesk\Exception\Database: DB query failed: SQLSTATE[HY000] [2002] No such file or directory (Mysql.php:79)
Sep 24 15:39:22 s19362569 systemd[1]: plesk-web-socket.service: main process exited, code=exited, status=1/FAILURE
Sep 24 15:39:22 s19362569 systemd[1]: Unit plesk-web-socket.service entered failed state.
Sep 24 15:39:22 s19362569 systemd[1]: plesk-web-socket.service failed.
Sep 24 15:39:22 s19362569 named[1885]: client @0x7f1a04114d00 104.35.74.126#7547 (ferc.gov): query (cache) 'ferc.gov/ANY/IN' denied
Sep 24 15:39:23 s19362569 named[1885]: client @0x7f1a04114d00 104.35.74.126#7547 (ferc.gov): query (cache) 'ferc.gov/ANY/IN' denied
Sep 24 15:39:24 s19362569 named[1885]: client @0x7f1a04114d00 104.35.74.126#7547 (ferc.gov): query (cache) 'ferc.gov/ANY/IN' denied
lines 1414-1473/1473 (END)

 

[Kaspar]

It looks like you've updated MariaDB to version 10.9, which isn't supported (yet) by Plesk.

Anyway, MariaDB doesn't start as version 10.6 or higher do not allow a bind to both ::1 and 127.0.0.1 via the setting bind-address = ::ffff:127.0.0.1. Which is set in the /etc/my.cnf file. Which is indicated by the error Can't start server: Bind on TCP/IP port. Got error: 22: Invalid argument outputted by journalctl -xe.

You can try to solve this particular error with the steps outlined in this support article: https://support.plesk.com/hc/en-us/...-on-TCP-IP-port-Got-error-22-Invalid-argument

However, you'll probably still run into issues as Plesk does not support MariaDB version 10.9. I am not sure if a downgrade is possible. I am reading people are having mixed results. So, maybe consider opening a support ticket with Plesk?

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com

 

[TrevorM]

Hi
Weird, I definitely added the correct text produced by the Mariadb repositories page 10.5
But should I have selected the MariaDB Server tab or the MariaDB repositories tab
Can I remove the lot and start again?

 

[TrevorM]

Tried reinstalling the correct version but now see this.
MariaDB-common conflicts with MariaDB-server-10.5.17-1.el7.centos.x86_64
Error: MariaDB-client conflicts with MariaDB-server-10.5.17-1.el7.centos.x86_64

 

[TrevorM]

So I yum removed all the incorrect versions and installed the correct one.
Better but now have the following;


[root@s19362569 etc]# systemctl status mariadb.service -l
● mariadb.service - MariaDB 10.5.17 database server
Loaded: loaded (/usr/lib/systemd/system/./mariadb.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sat 2022-09-24 16:43:32 BST; 54ms ago
Docs: man:mariadbd(8)
systemd
Process: 441 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 414 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 412 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 441 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [Note] InnoDB: Starting shutdown...
Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [ERROR] Plugin 'InnoDB' init function returned error.
Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [Note] Plugin 'FEEDBACK' is disabled.
Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Sep 24 16:43:32 s19362569 mariadbd[441]: 2022-09-24 16:43:32 0 [ERROR] Aborting
Sep 24 16:43:32 s19362569 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Sep 24 16:43:32 s19362569 systemd[1]: Failed to start MariaDB 10.5.17 database server.
Sep 24 16:43:32 s19362569 systemd[1]: Unit mariadb.service entered failed state.
Sep 24 16:43:32 s19362569 systemd[1]: mariadb.service failed.

 

[TrevorM]

Hi
So this was finally resolved after removing log files from /var/lib/mysql
ib_logfile0, ib_logfile1 and ib_logfile2 etc etc
In my case only the first was present.
Deleting that filed allowed the restart of the database server.
I have no idea how or why that file stops the server from starting.
I updated the databases as per the instructions and everything appear to be working.
I had to hit the refresh button to see the new database server version within Plesk.