• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Issue error updating to Plesk 18.0.43

Cristtiah

Basic Pleskian
getting an error updating my Plesk Linux below. Does anyone knows how to fix this? Thanks I appreciate it

Failed to install {'release': '1centos.7.220316.1402', 'version': '7.4.28', 'arch': 'x86_64', 'name': 'plesk-php74'}:
Error while downloading packages metainfo: failure: repodata/repomd.xml from mariadb: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.1/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found. Trying again.
http://yum.mariadb.org/10.1/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
 
service mysql status

Redirecting to /bin/systemctl status mysql.service

mariadb.service - MariaDB 10.6.7 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 Tue 2022-04-19 06:08:05 EDT; 4s ago

Docs: man:mariadbd(8)

systemd

Process: 32239 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

Process: 32207 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: 32204 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)

Main PID: 32239 (code=exited, status=1/FAILURE)

Status: "MariaDB server is down"



Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [Note] Plugin 'FEEDBACK' is disabled.

Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [Note] Server socket created on IP: '127.0.0.1'.

Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 22: Invalid argument

Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [ERROR] Do you already have another server running on port: 3306 ?

Apr 19 06:08:05 cp.aggelous.net mariadbd[32239]: 2022-04-19 6:08:05 0 [ERROR] Aborting

Apr 19 06:08:05 cp.aggelous.net systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE

Apr 19 06:08:05 cp.aggelous.net systemd[1]: Failed to start MariaDB 10.6.7 database server.

Apr 19 06:08:05 cp.aggelous.net systemd[1]: Unit mariadb.service entered failed state.

Apr 19 06:08:05 cp.aggelous.net systemd[1]: mariadb.service failed.
 
Hello,

MariaDB since 10.6 doesn't allows to bind both ::1 and 127.0.0.1 by setting bind-address = ::ffff:127.0.0.1 in my.cnf. If your upgrade from previous version, you should replace bind-address to 127.0.0.1, otherwise MariaDB won't start (or plesk sbin mysqlmng --bind-address local do it for you)
 
Back
Top