Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1
Updates / Re: How to stop update notifications for non existent updates?
« on: January 19, 2025, 06:57:59 PM »
Ok, I deleted the other an added this: 0 0 * * * /etc/cron.daily/yum
Thank you
Thank you
2
Updates / Re: How to stop update notifications for non existent updates?
« on: January 19, 2025, 06:14:28 AM »
0 0 * * * yum -y update
3
Updates / How to stop update notifications for non existent updates?
« on: January 19, 2025, 03:40:21 AM »
I login to the root panel every day twice a day and every time there is an orange notification in the bottom right saying there is 2 updates, it ALWAYS says 2 updates even if by chance UI would have 17 updates for real. Please tell me how to fix this. Is there maybe a CWP Cache somewhere that is stuck?
4
How to / Re: Increase /root Partition in CWP?
« on: December 18, 2024, 07:55:30 AM »
I finally fixed it by moving all log files over to / home until they fill up again and then I'll move them over again but I also moved/backup over to /home/backup and that brought it down to 52%, so I was able to start my SQL backup and get everything going but now I'm not sure if this has to do with my SQL being down during that time but I have an issue now that I don't get...
Warning: Attempt to read property "name" on null in /home/hmudate/public_html/assets/includes/core.php on line 1251
Warning: Attempt to read property "id" on null in /home/hmudate/public_html/assets/includes/core.php on line 1260
Warning: Attempt to read property "fake" on null in /home/hmudate/public_html/assets/includes/core.php on line 1269
Warning: Attempt to read property "lang" on null in /home/hmudate/public_html/assets/includes/core.php on line 1270
Warning: Attempt to read property "gender" on null in /home/hmudate/public_html/assets/includes/core.php on line 1270
Fatal error: Uncaught mysqli_sql_exception: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'order by q_order asc' at line 1 in /home/hmudate/public_html/assets/includes/core.php:2199 Stack trace: #0 /home/hmudate/public_html/assets/includes/core.php(2199): mysqli->query() #1 /home/hmudate/public_html/assets/includes/core.php(1270): profileQuestion() #2 /home/hmudate/public_html/mobile/index.php(13): getUserInfo() #3 {main} thrown in /home/hmudate/public_html/assets/includes/core.php on line 2199
Warning: Attempt to read property "name" on null in /home/hmudate/public_html/assets/includes/core.php on line 1251
Warning: Attempt to read property "id" on null in /home/hmudate/public_html/assets/includes/core.php on line 1260
Warning: Attempt to read property "fake" on null in /home/hmudate/public_html/assets/includes/core.php on line 1269
Warning: Attempt to read property "lang" on null in /home/hmudate/public_html/assets/includes/core.php on line 1270
Warning: Attempt to read property "gender" on null in /home/hmudate/public_html/assets/includes/core.php on line 1270
Fatal error: Uncaught mysqli_sql_exception: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'order by q_order asc' at line 1 in /home/hmudate/public_html/assets/includes/core.php:2199 Stack trace: #0 /home/hmudate/public_html/assets/includes/core.php(2199): mysqli->query() #1 /home/hmudate/public_html/assets/includes/core.php(1270): profileQuestion() #2 /home/hmudate/public_html/mobile/index.php(13): getUserInfo() #3 {main} thrown in /home/hmudate/public_html/assets/includes/core.php on line 2199
5
How to / Re: Increase /root Partition in CWP?
« on: December 15, 2024, 05:44:54 AM »One system I manage uses traditional partitions, therefore fdisk and growpart are needed:
https://thelinuxcode.com/extend-xfs-filesystem-linux-without-lvm/
But other systems I manage use LVM, so this is a good guide:
https://sleeplessbeastie.eu/2020/04/22/how-to-expand-an-existing-xfs-filesystem-on-lvm-logical-volume/
[root@viking ~]# sudo pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 almalinux lvm2 a-- 1.56t 0
[root@viking ~]# sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.6T 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 1.6T 0 part
├─almalinux-root 253:0 0 70G 0 lvm /
├─almalinux-swap 253:1 0 23.6G 0 lvm [SWAP]
└─almalinux-home 253:2 0 1.5T 0 lvm /home
[root@viking ~]# sudo pvcreate /dev/sdb
No device found for /dev/sdb.
[root@viking ~]#
6
How to / Re: Increase /root Partition in CWP?
« on: December 15, 2024, 05:41:11 AM »
[root@viking ~]# ls -lh
total 68K
-rw-------. 1 root root 1007 Aug 6 03:03 anaconda-ks.cfg
-rw-r--r-- 1 root root 735 Nov 18 23:34 cron
drwxr-xr-x 81 root root 4.0K Dec 9 05:12 node_modules
-rw-r--r-- 1 root root 105 Dec 9 05:12 package.json
-rw-r--r-- 1 root root 40K Dec 9 05:12 package-lock.json
-rw-r--r-- 1 root root 3.0K Dec 9 05:12 server.js
-rw-r--r--. 1 root root 1.1K Aug 6 03:15 viking.dratgocom.xyz.csr
-rw-------. 1 root root 1.8K Aug 6 03:15 viking.dratgocom.xyz.key.org
[root@viking ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 24G 0 24G 0% /dev
tmpfs 24G 0 24G 0% /dev/shm
tmpfs 24G 2.3G 22G 10% /run
tmpfs 24G 0 24G 0% /sys/fs/cgroup
/dev/mapper/almalinux-root 70G 70G 20K 100% /
/dev/sda1 1014M 340M 675M 34% /boot
/dev/mapper/almalinux-home 1.5T 49G 1.5T 4% /home
tmpfs 4.7G 0 4.7G 0% /run/user/0
tmpfs 4.7G 0 4.7G 0% /run/user/1002
I am trying to find safe stuff in /root I can delete to make enough room to install gparted. I can get in ssh and vnc both but I am not sure what is safe to delete. I can't install anything or update because I get an error that it's full.
total 68K
-rw-------. 1 root root 1007 Aug 6 03:03 anaconda-ks.cfg
-rw-r--r-- 1 root root 735 Nov 18 23:34 cron
drwxr-xr-x 81 root root 4.0K Dec 9 05:12 node_modules
-rw-r--r-- 1 root root 105 Dec 9 05:12 package.json
-rw-r--r-- 1 root root 40K Dec 9 05:12 package-lock.json
-rw-r--r-- 1 root root 3.0K Dec 9 05:12 server.js
-rw-r--r--. 1 root root 1.1K Aug 6 03:15 viking.dratgocom.xyz.csr
-rw-------. 1 root root 1.8K Aug 6 03:15 viking.dratgocom.xyz.key.org
[root@viking ~]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 24G 0 24G 0% /dev
tmpfs 24G 0 24G 0% /dev/shm
tmpfs 24G 2.3G 22G 10% /run
tmpfs 24G 0 24G 0% /sys/fs/cgroup
/dev/mapper/almalinux-root 70G 70G 20K 100% /
/dev/sda1 1014M 340M 675M 34% /boot
/dev/mapper/almalinux-home 1.5T 49G 1.5T 4% /home
tmpfs 4.7G 0 4.7G 0% /run/user/0
tmpfs 4.7G 0 4.7G 0% /run/user/1002
I am trying to find safe stuff in /root I can delete to make enough room to install gparted. I can get in ssh and vnc both but I am not sure what is safe to delete. I can't install anything or update because I get an error that it's full.
7
How to / Re: Increase /root Partition in CWP?
« on: December 14, 2024, 05:20:47 AM »
[root@viking ~]# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/almalinux-root 70G 70G 20K 100% /
[root@viking ~]# fdisk -l
Disk /dev/sda: 1.6 TiB, 1717986918400 bytes, 3355443200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x064e8d9a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2099199 2097152 1G 83 Linux
/dev/sda2 2099200 3355443199 3353344000 1.6T 8e Linux LVM
Disk /dev/mapper/almalinux-root: 70 GiB, 75161927680 bytes, 146800640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/almalinux-swap: 23.6 GiB, 25375539200 bytes, 49561600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/almalinux-home: 1.5 TiB, 1616371515392 bytes, 3156975616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@viking ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 24564712 0 24564712 0% /dev
tmpfs 24583732 0 24583732 0% /dev/shm
tmpfs 24583732 305664 24278068 2% /run
tmpfs 24583732 0 24583732 0% /sys/fs/cgroup
/dev/mapper/almalinux-root 73364480 73364460 20 100% /
/dev/sda1 1038336 347532 690804 34% /boot
/dev/mapper/almalinux-home 1577717064 50447700 1527269364 4% /home
tmpfs 4916744 0 4916744 0% /run/user/1002
tmpfs 4916744 0 4916744 0% /run/user/0
I don't have partition names and numbers like this tut is talking about.
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/almalinux-root 70G 70G 20K 100% /
[root@viking ~]# fdisk -l
Disk /dev/sda: 1.6 TiB, 1717986918400 bytes, 3355443200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x064e8d9a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2099199 2097152 1G 83 Linux
/dev/sda2 2099200 3355443199 3353344000 1.6T 8e Linux LVM
Disk /dev/mapper/almalinux-root: 70 GiB, 75161927680 bytes, 146800640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/almalinux-swap: 23.6 GiB, 25375539200 bytes, 49561600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/almalinux-home: 1.5 TiB, 1616371515392 bytes, 3156975616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@viking ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 24564712 0 24564712 0% /dev
tmpfs 24583732 0 24583732 0% /dev/shm
tmpfs 24583732 305664 24278068 2% /run
tmpfs 24583732 0 24583732 0% /sys/fs/cgroup
/dev/mapper/almalinux-root 73364480 73364460 20 100% /
/dev/sda1 1038336 347532 690804 34% /boot
/dev/mapper/almalinux-home 1577717064 50447700 1527269364 4% /home
tmpfs 4916744 0 4916744 0% /run/user/1002
tmpfs 4916744 0 4916744 0% /run/user/0
I don't have partition names and numbers like this tut is talking about.
8
How to / Re: Increase /root Partition in CWP?
« on: December 14, 2024, 12:02:15 AM »
I found the following but it doesn't seem to 100% follow with Almalinux 8.10 and it's kind of scary hehe. I did a snapshot just now before I try anything. I wish there was a way to get a gparted gui from cli remotely as it is a vps account on Contabo.
To increase the size of the root partition from the command line (CLI), you typically need to use the fdisk command to modify the partition size, then use resize2fs to resize the filesystem within that partition, ensuring your system is using Logical Volume Management (LVM) if applicable to simplify the process.
Key steps:
Check current partition size:
Use df -h / to see the current size of your root partition.
Access disk partition editor:
Without LVM: Run sudo fdisk /dev/sda (replace "sda" with your disk identifier from fdisk -l).
With LVM: Identify the logical volume associated with your root partition using vgdisplay and lvdisplaycommands.
Modify partition size:
In fdisk:1
Press 'p' to view partitions.
Select the partition you want to resize using the partition number.
Use the 'n' command to create a new partition or extend the existing one.
Press 'w' to write changes and exit.
Resize filesystem:
Run sudo resize2fs /dev/sdX(replace "sdX" with the device name of your root partition).
Important considerations:
Backup data: Always back up your system before making significant partition changes.
LVM usage: If your system uses LVM, use commands like lvextend to expand the logical volume associated with your root partition.
Reboot: Depending on your system configuration, you might need to reboot after resizing the partition.
To increase the size of the root partition from the command line (CLI), you typically need to use the fdisk command to modify the partition size, then use resize2fs to resize the filesystem within that partition, ensuring your system is using Logical Volume Management (LVM) if applicable to simplify the process.
Key steps:
Check current partition size:
Use df -h / to see the current size of your root partition.
Access disk partition editor:
Without LVM: Run sudo fdisk /dev/sda (replace "sda" with your disk identifier from fdisk -l).
With LVM: Identify the logical volume associated with your root partition using vgdisplay and lvdisplaycommands.
Modify partition size:
In fdisk:1
Press 'p' to view partitions.
Select the partition you want to resize using the partition number.
Use the 'n' command to create a new partition or extend the existing one.
Press 'w' to write changes and exit.
Resize filesystem:
Run sudo resize2fs /dev/sdX(replace "sdX" with the device name of your root partition).
Important considerations:
Backup data: Always back up your system before making significant partition changes.
LVM usage: If your system uses LVM, use commands like lvextend to expand the logical volume associated with your root partition.
Reboot: Depending on your system configuration, you might need to reboot after resizing the partition.
9
How to / Increase /root Partition in CWP?
« on: December 13, 2024, 06:03:25 PM »
Is there a way in CWP to edit partitions and resize? I have a 100% full /root and it's causing issues. I rebooted and it's still full. I want to increase it from 7oGB to 200GB? If not in CWP how to do this cli on Almalinux 8.10.
10
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 11:05:22 PM »Check the files in:
/root/.my.cnf
/etc/my.cnf
/etc/my.cnf.d/*
and disable "sql_mode" in every section except [mariadb], [server] then restart mariadb and run mariadb-upgrade (not mysql_upgrade) again.
Awesome you rock. That got my db'sa back and everything said OK so it's all good. I appreciate your help so much. So now if I need to put the strict_tables back where do you recommend I put it?
11
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 10:55:28 PM »Check the files in:
/etc/my.cnf
/etc/my.cnf.d/*
and disable "sql_mode" in every section except [mariadb], [server] then restart mariadb and run mariadb-upgrade (not mysql_upgrade) again.
Yeah I tried to create a db and it says it's created but doesn't show up.
12
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 10:43:39 PM »
I spoke too soon...I run this mode because of a php script that requires it.
[root@viking ~]# mysql_upgrade --force
mysql_upgrade: unknown variable 'sql_mode=NO_ENGINE_SUBSTITUTION'
[root@viking ~]#
[root@viking ~]# mysql_upgrade --force
mysql_upgrade: unknown variable 'sql_mode=NO_ENGINE_SUBSTITUTION'
[root@viking ~]#
13
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 10:40:17 PM »I would just follow Sandeep's full set of steps in the linked forum post. (It will remove MariaDB 10.4 and should take you to 10.11.9).
YESSSSS! Finally...Thank you sooooooo much.
Package Architecture Version Repository Size
============================================================================================================================================================================================
Installing:
MariaDB-server x86_64 10.11.10-1.el8 mariadb 28 M
Upgrading:
MariaDB-client x86_64 10.11.10-1.el8 mariadb 16 M
Installing weak dependencies:
pv x86_64 1.6.6-7.el8 epel 64 k
Transaction Summary
============================================================================================================================================================================================
Install 2 Packages
Upgrade 1 Package
Total download size: 44 M
Downloading Packages:
(1/3): pv-1.6.6-7.el8.x86_64.rpm 747 kB/s | 64 kB 00:00
(2/3): MariaDB-client-10.11.10-1.el8.x86_64.rpm 24 MB/s | 16 MB 00:00
(3/3): MariaDB-server-10.11.10-1.el8.x86_64.rpm 35 MB/s | 28 MB 00:00
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 37 MB/s | 44 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Upgrading : MariaDB-client-10.11.10-1.el8.x86_64 1/4
Installing : pv-1.6.6-7.el8.x86_64 2/4
Running scriptlet: MariaDB-server-10.11.10-1.el8.x86_64 3/4
Installing : MariaDB-server-10.11.10-1.el8.x86_64 3/4
Running scriptlet: MariaDB-server-10.11.10-1.el8.x86_64 3/4
Cleanup : MariaDB-client-10.6.20-1.el8.x86_64 4/4
Running scriptlet: MariaDB-server-10.11.10-1.el8.x86_64 4/4
Running scriptlet: MariaDB-client-10.6.20-1.el8.x86_64 4/4
Verifying : pv-1.6.6-7.el8.x86_64 1/4
Verifying : MariaDB-server-10.11.10-1.el8.x86_64 2/4
Verifying : MariaDB-client-10.11.10-1.el8.x86_64 3/4
Verifying : MariaDB-client-10.6.20-1.el8.x86_64 4/4
Upgraded:
MariaDB-client-10.11.10-1.el8.x86_64
Installed:
MariaDB-server-10.11.10-1.el8.x86_64 pv-1.6.6-7.el8.x86_64
Complete!
[root@viking ~]#
14
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 09:20:06 PM »https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/#comment-25
Probably your missing step is:Code: [Select]systemctl stop mariadb mysql mysqldAnd note that 10.10 is already EOL. You should look to 10.11 LTS -- good through Feb 2028:
systemctl disable mariadb
rpm --nodeps -ev MariaDB-server
https://endoflife.date/mariadb
So, to confirm I should do these commands first then do the commands I used above in the same order? I don't want to have to revive it again from a snapshot hehe
15
MySQL / Re: MARIADB10.4.0 to 10.10.0
« on: December 10, 2024, 05:21:10 AM »
Yum updates in CWP panel even fails:
Last metadata expiration check: 0:06:07 ago on Tue Dec 10 05:14:06 2024.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Upgrading:
MariaDB-devel x86_64 10.6.20-1.el8 mariadb 8.2 M
MariaDB-server x86_64 10.6.20-1.el8 mariadb 26 M
MariaDB-shared x86_64 10.6.20-1.el8 mariadb 128 k
galera-4 x86_64 26.4.20-1.el8 mariadb 1.7 M
Transaction Summary
================================================================================
Upgrade 4 Packages
Total download size: 36 M
Downloading Packages:
(1/4): MariaDB-shared-10.6.20-1.el8.x86_64.rpm 740 kB/s | 128 kB 00:00
(2/4): MariaDB-server-10.6.20-1.el8.x86_64.rpm 47 MB/s | 26 MB 00:00
(3/4): galera-4-26.4.20-1.el8.x86_64.rpm 4.2 MB/s | 1.7 MB 00:00
(4/4): MariaDB-devel-10.6.20-1.el8.x86_64.rpm 13 MB/s | 8.2 MB 00:00
--------------------------------------------------------------------------------
Total 57 MB/s | 36 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/1
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/8
Upgrading : galera-4-26.4.20-1.el8.x86_64 1/8
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/8
Upgrading : MariaDB-shared-10.6.20-1.el8.x86_64 2/8
Running scriptlet: MariaDB-shared-10.6.20-1.el8.x86_64 2/8
Upgrading : MariaDB-devel-10.6.20-1.el8.x86_64 3/8
Running scriptlet: MariaDB-server-10.6.20-1.el8.x86_64 4/8
******************************************************************
A MySQL or MariaDB server package (MariaDB-server-10.4.34-1.el8.x86_64) is installed.
Upgrading directly from MySQL 10.4 to MariaDB 10.6 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
A manual upgrade is required.
- Ensure that you have a complete, working backup of your data and my.cnf
files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages. Usually this command will
list the packages you should remove:
rpm -qa | grep -i '^mysql-'
You may choose to use 'rpm --nodeps -ev ' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by MariaDB Foundation
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program
This is a brief description of the upgrade process. Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
error: %prein(MariaDB-server-10.6.20-1.el8.x86_64) scriptlet failed, exit status 1
Running scriptlet: MariaDB-devel-10.4.34-1.el8.x86_64 5/8
error: MariaDB-server-10.6.20-1.el8.x86_64: install failed
error: MariaDB-server-10.4.34-1.el8.x86_64: erase skipped
Cleanup : MariaDB-devel-10.4.34-1.el8.x86_64 5/8
Running scriptlet: MariaDB-devel-10.4.34-1.el8.x86_64 5/8
Running scriptlet: MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Cleanup : MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Running scriptlet: MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Running scriptlet: galera-4-26.4.18-1.el8.x86_64 7/8
Cleanup : galera-4-26.4.18-1.el8.x86_64 7/8
Running scriptlet: galera-4-26.4.18-1.el8.x86_64 7/8
Verifying : MariaDB-devel-10.6.20-1.el8.x86_64 1/8
Verifying : MariaDB-devel-10.4.34-1.el8.x86_64 2/8
Verifying : MariaDB-server-10.6.20-1.el8.x86_64 3/8
Verifying : MariaDB-server-10.4.34-1.el8.x86_64 4/8
Verifying : MariaDB-shared-10.6.20-1.el8.x86_64 5/8
Verifying : MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Verifying : galera-4-26.4.20-1.el8.x86_64 7/8
Verifying : galera-4-26.4.18-1.el8.x86_64 8/8
Upgraded:
MariaDB-devel-10.6.20-1.el8.x86_64 MariaDB-shared-10.6.20-1.el8.x86_64
galera-4-26.4.20-1.el8.x86_64
Failed:
MariaDB-server-10.4.34-1.el8.x86_64 MariaDB-server-10.6.20-1.el8.x86_64
Last metadata expiration check: 0:06:07 ago on Tue Dec 10 05:14:06 2024.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Upgrading:
MariaDB-devel x86_64 10.6.20-1.el8 mariadb 8.2 M
MariaDB-server x86_64 10.6.20-1.el8 mariadb 26 M
MariaDB-shared x86_64 10.6.20-1.el8 mariadb 128 k
galera-4 x86_64 26.4.20-1.el8 mariadb 1.7 M
Transaction Summary
================================================================================
Upgrade 4 Packages
Total download size: 36 M
Downloading Packages:
(1/4): MariaDB-shared-10.6.20-1.el8.x86_64.rpm 740 kB/s | 128 kB 00:00
(2/4): MariaDB-server-10.6.20-1.el8.x86_64.rpm 47 MB/s | 26 MB 00:00
(3/4): galera-4-26.4.20-1.el8.x86_64.rpm 4.2 MB/s | 1.7 MB 00:00
(4/4): MariaDB-devel-10.6.20-1.el8.x86_64.rpm 13 MB/s | 8.2 MB 00:00
--------------------------------------------------------------------------------
Total 57 MB/s | 36 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/1
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/8
Upgrading : galera-4-26.4.20-1.el8.x86_64 1/8
Running scriptlet: galera-4-26.4.20-1.el8.x86_64 1/8
Upgrading : MariaDB-shared-10.6.20-1.el8.x86_64 2/8
Running scriptlet: MariaDB-shared-10.6.20-1.el8.x86_64 2/8
Upgrading : MariaDB-devel-10.6.20-1.el8.x86_64 3/8
Running scriptlet: MariaDB-server-10.6.20-1.el8.x86_64 4/8
******************************************************************
A MySQL or MariaDB server package (MariaDB-server-10.4.34-1.el8.x86_64) is installed.
Upgrading directly from MySQL 10.4 to MariaDB 10.6 may not
be safe in all cases. A manual dump and restore using mysqldump is
recommended. It is important to review the MariaDB manual's Upgrading
section for version-specific incompatibilities.
A manual upgrade is required.
- Ensure that you have a complete, working backup of your data and my.cnf
files
- Shut down the MySQL server cleanly
- Remove the existing MySQL packages. Usually this command will
list the packages you should remove:
rpm -qa | grep -i '^mysql-'
You may choose to use 'rpm --nodeps -ev ' to remove
the package which contains the mysqlclient shared library. The
library will be reinstalled by the MariaDB-shared package.
- Install the new MariaDB packages supplied by MariaDB Foundation
- Ensure that the MariaDB server is started
- Run the 'mysql_upgrade' program
This is a brief description of the upgrade process. Important details
can be found in the MariaDB manual, in the Upgrading section.
******************************************************************
error: %prein(MariaDB-server-10.6.20-1.el8.x86_64) scriptlet failed, exit status 1
Running scriptlet: MariaDB-devel-10.4.34-1.el8.x86_64 5/8
error: MariaDB-server-10.6.20-1.el8.x86_64: install failed
error: MariaDB-server-10.4.34-1.el8.x86_64: erase skipped
Cleanup : MariaDB-devel-10.4.34-1.el8.x86_64 5/8
Running scriptlet: MariaDB-devel-10.4.34-1.el8.x86_64 5/8
Running scriptlet: MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Cleanup : MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Running scriptlet: MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Running scriptlet: galera-4-26.4.18-1.el8.x86_64 7/8
Cleanup : galera-4-26.4.18-1.el8.x86_64 7/8
Running scriptlet: galera-4-26.4.18-1.el8.x86_64 7/8
Verifying : MariaDB-devel-10.6.20-1.el8.x86_64 1/8
Verifying : MariaDB-devel-10.4.34-1.el8.x86_64 2/8
Verifying : MariaDB-server-10.6.20-1.el8.x86_64 3/8
Verifying : MariaDB-server-10.4.34-1.el8.x86_64 4/8
Verifying : MariaDB-shared-10.6.20-1.el8.x86_64 5/8
Verifying : MariaDB-shared-10.4.34-1.el8.x86_64 6/8
Verifying : galera-4-26.4.20-1.el8.x86_64 7/8
Verifying : galera-4-26.4.18-1.el8.x86_64 8/8
Upgraded:
MariaDB-devel-10.6.20-1.el8.x86_64 MariaDB-shared-10.6.20-1.el8.x86_64
galera-4-26.4.20-1.el8.x86_64
Failed:
MariaDB-server-10.4.34-1.el8.x86_64 MariaDB-server-10.6.20-1.el8.x86_64
