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.
Pages: [1] 2
1
Updates / Re: MariaDB error preventing other updates
« on: March 27, 2025, 05:34:44 PM »
I understand that. I wondering about getting the other updates applied before I start upgrading all of my servers.
2
Updates / MariaDB error preventing other updates
« on: March 26, 2025, 10:01:46 PM »
I apologize as I know there are many entries regarding MariaDB updates. I just have a quick question. I am running CWPpro version: 0.9.8.1201 on AlmaLinux 8. CWP yum manager is showing only 1 update which is MariaDB. I know that I have to manually update MariaDB 10.4 to 10.11 manually. However, the error is causing the other updates to not show up. On a test box, I remarked out all lines in the /etc/yum.repos.d/mariadb.repo, I refreshed, then all kinds of other updates showed up and I was able to successfully complete those.
Is it advisable to do this just to get other updates applied before I upgrade MariaDB? Or is there a better best/practice way of getting the needed updates completed?
-------------------------------------------------------------------------------------------------------------------------------------------------
Last metadata expiration check: 0:14:54 ago on Tue Mar 25 12:24:17 2025.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Upgrading:
MariaDB-server x86_64 10.11.11-1.el8 mariadb 28 M
Transaction Summary
================================================================================
Upgrade 1 Package
Total download size: 28 M
Downloading Packages:
MariaDB-server-10.11.11-1.el8.x86_64.rpm 3.8 MB/s | 28 MB 00:07
--------------------------------------------------------------------------------
Total 3.8 MB/s | 28 MB 00:07
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64 1/1
Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64 1/2
******************************************************************
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.11 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.11.11-1.el8.x86_64) scriptlet failed, exit status 1
Verifying : MariaDB-server-10.11.11-1.el8.x86_64 1/2
Verifying : MariaDB-server-10.4.34-1.el8.x86_64 2/2
Failed:
MariaDB-server-10.4.34-1.el8.x86_64 MariaDB-server-10.11.11-1.el8.x86_64
Is it advisable to do this just to get other updates applied before I upgrade MariaDB? Or is there a better best/practice way of getting the needed updates completed?
-------------------------------------------------------------------------------------------------------------------------------------------------
Last metadata expiration check: 0:14:54 ago on Tue Mar 25 12:24:17 2025.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Upgrading:
MariaDB-server x86_64 10.11.11-1.el8 mariadb 28 M
Transaction Summary
================================================================================
Upgrade 1 Package
Total download size: 28 M
Downloading Packages:
MariaDB-server-10.11.11-1.el8.x86_64.rpm 3.8 MB/s | 28 MB 00:07
--------------------------------------------------------------------------------
Total 3.8 MB/s | 28 MB 00:07
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64 1/1
Running scriptlet: MariaDB-server-10.11.11-1.el8.x86_64 1/2
******************************************************************
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.11 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.11.11-1.el8.x86_64) scriptlet failed, exit status 1
Verifying : MariaDB-server-10.11.11-1.el8.x86_64 1/2
Verifying : MariaDB-server-10.4.34-1.el8.x86_64 2/2
Failed:
MariaDB-server-10.4.34-1.el8.x86_64 MariaDB-server-10.11.11-1.el8.x86_64
3
Migration from other control panels / Re: CWP to CWP migration does not connect
« on: January 07, 2025, 04:59:31 PM »
Same error
4
Migration from other control panels / Re: CWP to CWP migration does not connect
« on: January 06, 2025, 10:55:02 PM »
I am having the same issue. CWP Almalinux 8 to CWP Almalinux 8
Connection not reached
I am having the same issue. CWP Almalinux 8 to CWP Almalinux 8
Connection not reached
Account_Transfer.Log
2025-01-06 22:50:33 /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:rbaIoOc/asdf09a8sd90f890as8df9a0sdf8.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
root@IPADDRESS: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
2025-01-06 22:50:33 export SSHPASS=**********;/usr/bin/sshpass -e ssh-copy-id root@IPADDRESS -o StrictHostKeyChecking=no 2>&1
2025-01-06 22:50:33 /usr/bin/ssh -p 22 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet root@IPADDRESS test -d /usr/local/cwp/ && echo 'true' || echo 'false' 2>&1
2025-01-06 22:50:33 false
Connection not reached
I am having the same issue. CWP Almalinux 8 to CWP Almalinux 8
Connection not reached
Account_Transfer.Log
2025-01-06 22:50:33 /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:rbaIoOc/asdf09a8sd90f890as8df9a0sdf8.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
root@IPADDRESS: Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
2025-01-06 22:50:33 export SSHPASS=**********;/usr/bin/sshpass -e ssh-copy-id root@IPADDRESS -o StrictHostKeyChecking=no 2>&1
2025-01-06 22:50:33 /usr/bin/ssh -p 22 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet root@IPADDRESS test -d /usr/local/cwp/ && echo 'true' || echo 'false' 2>&1
2025-01-06 22:50:33 false
5
Backup / New Backup - FTP Error
« on: February 23, 2024, 10:11:41 PM »
I am getting these errors on some of my web servers. Anyone else experience this?
PHP Warning: ftp_put(): php_connect_nonb() failed: Operation now in progress (115) in /usr/local/cwpsrv/htdocs/resources/admin/addons/class_backupmanager.php on line 0
PHP Warning: ftp_put(): Type set to I in /usr/local/cwpsrv/htdocs/resources/admin/addons/class_backupmanager.php on line 0
PHP Warning: ftp_put(): php_connect_nonb() failed: Operation now in progress (115) in /usr/local/cwpsrv/htdocs/resources/admin/addons/class_backupmanager.php on line 0
PHP Warning: ftp_put(): Type set to I in /usr/local/cwpsrv/htdocs/resources/admin/addons/class_backupmanager.php on line 0
6
Backup / FTP Backup
« on: July 20, 2023, 06:32:12 PM »
I have been using an FTP backup with New Backup (Beta) with zero issues until July 8th. The backup logs are not showing any errors and shows Backup Successful. It does generate the tar.gz file and pushes it to my FTP server. However, it is not complete. The backup is missing many files. Has anyone ran into this?
7
E-Mail / Cannot Reply To Messages - RoundCube
« on: September 22, 2022, 01:49:36 PM »
Some of our users are reporting issues in RoundCube when replying to emails. It just sits and spins until it just times out. These users are all on different domains within CWP. Has anyone else experienced this?
Thank you
Just to add from a recent user report. It is happening when attempting to forward messages as well. It sits on spinning then just says "Your messages was not sent" according to the user.
Thank you
Just to add from a recent user report. It is happening when attempting to forward messages as well. It sits on spinning then just says "Your messages was not sent" according to the user.
8
E-Mail / Re: Roundcube cant reply to emails but can send individually
« on: September 22, 2022, 01:41:12 PM »
I am now experiencing this same issue. Was there any fix?
9
E-Mail / Re: Roundcube Inbox Server Error! (Internal Server Error)
« on: October 19, 2021, 12:34:47 PM »
Attemping to run "/scripts/update_cwp" and getting this:
** (pkttyagent:112068): WARNING **: 07:23:47.645: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Just sitting here. However in CWP Admin it is now showing CWP Up to date. I need to run the roundcube update to fix the error.
What do I need to do? interrupt the putty session?
** (pkttyagent:112068): WARNING **: 07:23:47.645: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Just sitting here. However in CWP Admin it is now showing CWP Up to date. I need to run the roundcube update to fix the error.
What do I need to do? interrupt the putty session?
10
E-Mail / Re: Roundcube1.5.x Internal Server Error - FIX
« on: October 19, 2021, 12:30:19 PM »
Attemping to run "/scripts/update_cwp" and getting this:
** (pkttyagent:112068): WARNING **: 07:23:47.645: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Just sitting here. However in CWP Admin it is now showing CWP Up to date. I need to run the roundcube update to fix the error.
What do I need to do? interrupt the putty session?
** (pkttyagent:112068): WARNING **: 07:23:47.645: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Cannot determine user of subject
Just sitting here. However in CWP Admin it is now showing CWP Up to date. I need to run the roundcube update to fix the error.
What do I need to do? interrupt the putty session?
11
E-Mail / Re: Roundcube: Unable to connect to the database!
« on: October 06, 2021, 12:02:54 PM »
I am having the same issue " DATABASE ERROR: CONNECTION FAILED! "
Have no idea how to fix.
Have no idea how to fix.
12
SSL / Let's Encrypt DST Root CA X3 expiry Sept 30th 2021
« on: October 02, 2021, 09:14:51 PM »
Having issues with some of my Websites giving me CA Cert errors since "Let's Encrypt DST Root CA X3 expiry Sept 30th 2021"
A Certificate Authority verified SSL certificate was not detected on "Website URL".
A Certificate Authority verified SSL certificate was not detected on "Website URL".
13
Backup / Re: A couple of issues with New Backup (beta)
« on: September 15, 2021, 01:58:35 PM »
Has something changed to where the New Backup is just creating account.tar.gz in the /newbackup/%weekday%/accounts folder and no longer creating a folder for each account and just backing up flat to those folders?
14
Backup / Re: A couple of issues with New Backup (beta)
« on: September 07, 2021, 03:16:01 PM »
Anyone else experiencing this or have any information on it?
15
Backup / A couple of issues with New Backup (beta)
« on: September 03, 2021, 07:02:57 PM »
A couple of issues with New Backup (beta).
1. I am not seeing any email backups (vmail) in the local backups backups. Where is "vmail" backed up in the New Backup (beta)?
2. The %backup%.tar.gz files are being left on the server after the FTP transfer completes.
Is this by design or is there a bug?
Thanks
1. I am not seeing any email backups (vmail) in the local backups backups. Where is "vmail" backed up in the New Backup (beta)?
2. The %backup%.tar.gz files are being left on the server after the FTP transfer completes.
Is this by design or is there a bug?
Thanks
Pages: [1] 2
