Show Posts

16

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.

17

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.

18

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.

19

MySQL / Re: MARIADB10.4.0 to 10.10.0

« on: December 10, 2024, 11:05:22 PM »

Quote from: cyberspace on December 10, 2024, 10:54:15 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?

20

MySQL / Re: MARIADB10.4.0 to 10.10.0

« on: December 10, 2024, 10:55:28 PM »

Quote from: cyberspace on December 10, 2024, 10:54:15 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.

21

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 ~]#

22

MySQL / Re: MARIADB10.4.0 to 10.10.0

« on: December 10, 2024, 10:40:17 PM »

Quote from: overseer on December 10, 2024, 10:18:21 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 ~]#

23

MySQL / Re: MARIADB10.4.0 to 10.10.0

« on: December 10, 2024, 09:20:06 PM »

Quote from: overseer on December 10, 2024, 02:50:46 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 mysqld systemctl disable mariadb rpm --nodeps -ev MariaDB-serverAnd note that 10.10 is already EOL. You should look to 10.11 LTS -- good through Feb 2028:
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

24

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

25

MySQL / Re: MARIADB10.4.0 to 10.10.0

« on: December 10, 2024, 05:18:14 AM »

Ok so I attempted this again when I found a new tutorial at https://blog.alphagnu.com/update-upgrade-to-mariadb-10-4-on-vestacp-cwp-centos-7/.

Below is the resuklts of it, why did it go right back to 10.4?

[root@viking etc]# cp /etc/my.cnf /etc/my.cnf.bak
[root@viking etc]# nano /etc/my.cnf
[root@viking etc]# mv /etc/yum.repos.d/mariadb.repo /etc/yum.repos.d/mariadb.repo.bak
[root@viking etc]# nano /etc/yum.repos.d/mariadb.repo
[root@viking etc]# yum clean all
81 files removed
[root@viking etc]# yum install MariaDB-server MariaDB-client net-snmp perl-DBD-MySQL -y
CentOS Web Panel repo for Linux 8 - x86_64 302 kB/s | 305 kB 00:01
AlmaLinux 8 - BaseOS 18 MB/s | 9.6 MB 00:00
AlmaLinux 8 - AppStream 27 MB/s | 15 MB 00:00
AlmaLinux 8 - Extras 37 kB/s | 13 kB 00:00
AlmaLinux 8 - PowerTools 9.1 MB/s | 4.0 MB 00:00
AlmaLinux 8 - PowerTools Source 207 kB/s | 138 kB 00:00
AlmaLinux 8 - PowerTools debuginfo 1.2 MB/s | 688 kB 00:00
Extra Packages for Enterprise Linux 8 - x86_64 30 MB/s | 14 MB 00:00
MariaDB 1.9 MB/s | 604 kB 00:00
nginx repo 1.1 MB/s | 71 kB 00:00
Package MariaDB-server-10.4.34-1.el8.x86_64 is already installed.
Package MariaDB-client-10.4.34-1.el8.x86_64 is already installed.
Package perl-DBD-MySQL-4.046-3.module_el8.6.0+2827+49d66dc3.x86_64 is already installed.
Dependencies resolved.
============================================================================================================================================================================================
Package Architecture Version Repository Size
============================================================================================================================================================================================
Installing:
net-snmp x86_64 1:5.8-30.el8 appstream 355 k
Upgrading:
MariaDB-client x86_64 10.6.20-1.el8 mariadb 15 M
MariaDB-common x86_64 10.6.20-1.el8 mariadb 88 k
MariaDB-server x86_64 10.6.20-1.el8 mariadb 26 M

Transaction Summary
============================================================================================================================================================================================
Install 1 Package
Upgrade 3 Packages

Total download size: 41 M
Downloading Packages:
(1/4): net-snmp-5.8-30.el8.x86_64.rpm 2.3 MB/s | 355 kB 00:00
(2/4): MariaDB-common-10.6.20-1.el8.x86_64.rpm 456 kB/s | 88 kB 00:00
(3/4): MariaDB-client-10.6.20-1.el8.x86_64.rpm 27 MB/s | 15 MB 00:00
(4/4): MariaDB-server-10.6.20-1.el8.x86_64.rpm 41 MB/s | 26 MB 00:00
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 36 MB/s | 41 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: MariaDB-common-10.6.20-1.el8.x86_64 1/1
Upgrading : MariaDB-common-10.6.20-1.el8.x86_64 1/7
Upgrading : MariaDB-client-10.6.20-1.el8.x86_64 2/7
Running scriptlet: MariaDB-server-10.6.20-1.el8.x86_64 3/7

******************************************************************
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 <package-name>' 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

Error in PREIN scriptlet in rpm package MariaDB-server
Installing : net-snmp-1:5.8-30.el8.x86_64 4/7
error: MariaDB-server-10.6.20-1.el8.x86_64: install failed

Running scriptlet: net-snmp-1:5.8-30.el8.x86_64 4/7
Running scriptlet: MariaDB-client-10.4.34-1.el8.x86_64 5/7
error: MariaDB-server-10.4.34-1.el8.x86_64: erase skipped

Cleanup : MariaDB-client-10.4.34-1.el8.x86_64 5/7
Running scriptlet: MariaDB-client-10.4.34-1.el8.x86_64 5/7
Running scriptlet: MariaDB-common-10.4.34-1.el8.x86_64 6/7
Cleanup : MariaDB-common-10.4.34-1.el8.x86_64 6/7
Running scriptlet: MariaDB-common-10.4.34-1.el8.x86_64 6/7
Verifying : net-snmp-1:5.8-30.el8.x86_64 1/7
Verifying : MariaDB-client-10.6.20-1.el8.x86_64 2/7
Verifying : MariaDB-client-10.4.34-1.el8.x86_64 3/7
Verifying : MariaDB-common-10.6.20-1.el8.x86_64 4/7
Verifying : MariaDB-common-10.4.34-1.el8.x86_64 5/7
Verifying : MariaDB-server-10.6.20-1.el8.x86_64 6/7
Verifying : MariaDB-server-10.4.34-1.el8.x86_64 7/7

Upgraded:
MariaDB-client-10.6.20-1.el8.x86_64 MariaDB-common-10.6.20-1.el8.x86_64
Installed:
net-snmp-1:5.8-30.el8.x86_64
Failed:
MariaDB-server-10.4.34-1.el8.x86_64 MariaDB-server-10.6.20-1.el8.x86_64

Error: Transaction failed
[root@viking etc]# rm -rf /etc/my.cnf
[root@viking etc]# cp /etc/my.cnf.bak /etc/my.cnf
[root@viking etc]# systemctl enable mariadb
[root@viking etc]# service mysql start
Redirecting to /bin/systemctl start mysql.service
[root@viking etc]# mysql_upgrade
This installation of MariaDB is already upgraded to 10.4.34-MariaDB.
There is no need to run mysql_upgrade again for 10.4.34-MariaDB.
You can use --force if you still want to run mysql_upgrade
[root@viking etc]# mysql
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 5198
Server version: 10.4.34-MariaDB MariaDB Server

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]>

26

CentOS-WebPanel GUI / Re: Known Issue???

« on: October 08, 2024, 11:07:21 PM »

For future fyi this fixed my user panels:

sh /scripts/cwpsrv_rebuild_user_conf

More Info @: https://wiki.centos-webpanel.com/404-on-user-login

27

CentOS-WebPanel GUI / Re: Known Issue???

« on: October 07, 2024, 08:09:40 AM »

Quote from: overseer on October 07, 2024, 05:45:17 AM

https://blog.alphagnu.com/fix-cwp-500-internal-server-error-expired-white-blank-screen/

[root@viking ~]# chattr -i -R /usr/local/cwpsrv/var/services/
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//user_api/v1/app/libs/hooks.php
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//user_api/v1/app/libs/functions.php
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/login/cwp_theme
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/softaculous/softimages
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/softaculous/themes
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/dragocom
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/nulled
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/nullwh
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/vipanel
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/fvault
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//users/users
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/program/resources
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/program/js
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/skins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/.htaccess
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/plugins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/public_html/robots.txt
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/vendor/bin/crypt-gpg-pinentry
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube/vendor/bin/rcubeinitdb.sh
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/robots.txt
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/plugins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/.htaccess
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/skins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/program/js
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcube_06-08-2024.bak/public_html/program/resources
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/public_html/program/resources
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/public_html/program/js
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/public_html/.htaccess
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/public_html/skins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/public_html/plugins
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/vendor/bin/rcubeinitdb.sh
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//roundcubemail-1.4.11/vendor/bin/crypt-gpg-pinentry
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//pma_06-08-2024.bak/vendor/bin/highlight-query
chattr: Operation not supported while reading flags on /usr/local/cwpsrv/var/services//pma_06-08-2024.bak/vendor/bin/lint-query

I went ahead and ran the rest of the commands and the sh update and it didn't help.

28

CentOS-WebPanel GUI / Re: Known Issue???

« on: October 07, 2024, 08:03:49 AM »

Quote from: Starburst on October 06, 2024, 06:08:24 AM

Try

User Account -> Fix Permissions -> (Select User) nobody

Check All 3 boxes, and then Fix Selected Issues.

If it's a permission issue, this 'might' take care of it.

Tried it same black screen with the same message.

29

CentOS-WebPanel GUI / Re: Known Issue???

« on: October 06, 2024, 02:41:03 AM »

Quote from: Starburst on October 05, 2024, 07:07:48 AM

Might be that bug popping up.

Try Suspending the client, make sure the suspend page come up, and then unsuspend.

That didn'twork unfortunately

30

CentOS-WebPanel GUI / Re: Known Issue???

« on: October 05, 2024, 06:10:49 AM »

Quote from: Starburst on October 04, 2024, 08:15:07 AM

Yesterday the control panel updated, and today there was an update to the cwp-suphp if you have the CWP repo active.

Did you try to reboot?

Yeah I tried a reboot. The cwp user page comes up I enter my l/p in the fields and submit and it goes to 500 error

This page isn’t working
viking.dragocom.xyz is currently unable to handle this request.

HTTP ERROR 500

Control Web Panel

Messages - DragoCom

How to / Re: Increase /root Partition in CWP?

How to / Re: Increase /root Partition in CWP?

How to / Increase /root Partition in CWP?

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

MySQL / Re: MARIADB10.4.0 to 10.10.0

CentOS-WebPanel GUI / Re: Known Issue???

CentOS-WebPanel GUI / Re: Known Issue???

CentOS-WebPanel GUI / Re: Known Issue???

CentOS-WebPanel GUI / Re: Known Issue???

CentOS-WebPanel GUI / Re: Known Issue???