mysql down

[hmaddy]

tried to upgrade mariadb 10.2 to 10.3 with the following command
cd /usr/local/directadmin/custombuild
./build clean
./build update
./build set mysql_backup yes
./build set mariadb 10.3
./build set mysql_inst mariadb
./build mariadb

But after the execution of these commands mariadb is down or cant restart. its throwing some error.

systemctl status mariadb
● mariadb.service - MariaDB database server
Loaded: loaded (/etc/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf, tokudb.conf
Active: failed (Result: exit-code) since Sun 2021-07-11 22:57:54 IST; 4min 45s ago
Process: 2305339 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 2305314 ExecStartPre=/bin/sh -c [ -x /usr/bin/galera_recovery ] || exit 0; VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 2305312 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 2305339 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CGroup: /system.slice/mariadb.service
└─1405 /usr/sbin/mysqld

Jul 11 22:55:42 linda1.xserver.com systemd[1]: Stopping MariaDB database server...
Jul 11 22:55:42 linda1.xserver.com systemd[1]: Starting MariaDB database server...
Jul 11 22:57:12 linda1.xserver.com systemd[1]: mariadb.service start operation timed out. Terminating.
Jul 11 22:57:54 linda1.xserver.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jul 11 22:57:54 linda1.xserver.com systemd[1]: Failed to start MariaDB database server.
Jul 11 22:57:54 linda1.xserver.com systemd[1]: Unit mariadb.service entered failed state.
Jul 11 22:57:54 linda1.xserver.com systemd[1]: mariadb.service failed.

 

[hmaddy]

i fixed above error and now getting another error when yum updates.



Error: Package: i360-clamav-0.99.4-8.12.el7.x86_64 (@cloudlinux-imunify360)
Requires: libyara.so.3()(64bit)
Removing: yara-3.11.0-1.el7.x86_64 (@epel)
libyara.so.3()(64bit)
Updated By: yara-4.1.0-1.el7.x86_64 (epel)
~libyara.so.8()(64bit)
Available: yara-3.5.0-5.el7.x86_64 (cloudlinux-imunify360)
libyara.so.3()(64bit)
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
MariaDB-compat-10.3.30-1.el7.centos.x86_64 has installed conflicts mariadb-libs < ('1', '10.1.0', None): cl-MariaDB-meta-10.2.39-1.el7.cloudlinux.x86_64



And when run flag --skin-broken


* cloudlinux-x86_64-server-7: cl-mirror.ukservers.com
* epel: epel.mirror.nucleus.be
Resolving Dependencies
--> Running transaction check
---> Package yara.x86_64 0:3.11.0-1.el7 will be updated
--> Processing Dependency: libyara.so.3()(64bit) for package: i360-clamav-0.99.4-8.12.el7.x86_64
---> Package yara.x86_64 0:4.1.0-1.el7 will be an update
epel/x86_64/filelists_db | 12 MB 00:00:00

Packages skipped because of dependency problems:
yara-4.1.0-1.el7.x86_64 from epel