Messages

1

CentOS-WebPanel Bugs / Filemanager is broken again!

« on: April 23, 2021, 05:22:51 PM »

The CWP filemanager GUI is broken again.

https://pasteboard.co/JYGL17N.png

Tried running sh /scripts/update_cwp but no luck. Is this only me or everyone else is having same issue?

2

Addons / Re: Wordpress Create Bug

« on: January 13, 2021, 08:06:56 PM »

Hi,

I could reproduce the issue on CWPpro version: 0.9.8.1032.

If user input same value as Database Name and User Name the installer works perfectly.

If the user input different value as Database and User Name, the installer creates the wp-config.php file with "User Name" value both in DB_NAME and DB_USER fields which causes a database error on the WordPress site because of wrong credentials.

Steps to reproduce the issue -
Login to CWP User -> Navigate to Addons -> WordPress -> Add New WordPress -> Set "wpdb" as database name and "wpuser" as username and finish installation.

I have tried on multiple server and could reproduce this on all of them.
Please let me know if there's something I can do to fix this.

Thanks.

3

PHP Selector / Re: Error php-fpm whmcs 503 Service Unavailable

« on: January 13, 2021, 04:42:31 PM »

I have been experiencing the same issue.

Code: [Select]

process_control_timeout = 10s
Setting the above in php-fpm.conf partially fixed the issue. Now suspending/unsuspending account through WHMCS works fine. But still seeing the following error when trying to accept new order (creating new hosting account) from WHMCS.

Code: [Select]

[Wed Jan 13 21:14:22.441491 2021] [proxy_fcgi:error] [pid 19466:tid 140073714579200] [client xx.xx.xx.xx:52568] AH01067: Failed to read FastCGI header, referer: https://whmcsdomain.com/admin/orders.php?action=view&id=3
[Wed Jan 13 21:14:22.441570 2021] [proxy_fcgi:error] [pid 19466:tid 140073714579200] (104)Connection reset by peer: [client xx.xx.xx.xx:52568] AH01075: Error dispatching request to : , referer: https://whmcsdomain.com/admin/orders.php?action=view&id=3

Can anyone please suggest how to fix this?

4

CentOS-WebPanel Bugs / Re: Error when accessing phpmyadmin from the user side

« on: November 06, 2020, 04:34:26 PM »

Hi,

Is there any update on the phpMyAdmin auto login (client panel) issue?
I have checked and could reproduce the issue on both CWP free and PRO servers. Auto login to phpMyAdmin from CWP root panel works fine. Experiencing this issue only on user panel. I have tried both on http://IP:2083 and https://hostname.tld:2083 but the result is same.

5

Information / Re: Disappointed with CWP 🤬

« on: August 28, 2020, 05:21:26 PM »

How you are so certain it's the panel not the OS or some other configurations? Peoples here aren't wizards. They can't provide you solution if you don't share what you have tried and what you are seeing in the logs. If the required ports aren't open on both servers the API won't function properly. Try running the following on both servers and make sure the API is functional.

sh /scripts/check_api

However, I guess cPanel, Plesk would be better option for you as they are much polished compared to CWP and doesn't require much technical knowledge.

6

PHP / Re: CWP7.Pro Error | Unable to Login Admin Panel

« on: July 15, 2020, 07:14:19 AM »

https://forum.centos-webpanel.com/index.php?topic=9283.msg32481#msg32481

Do you want to say CWP Team themselves post "bad advice" in the forum? I myself experienced the same and following the instructions I posted fixed the issue.

7

PHP / Re: CWP7.Pro Error | Unable to Login Admin Panel

« on: July 12, 2020, 10:35:42 PM »

Try disabling secure/hidden process from CWP admin - > security and try again.

8

CentOS-WebPanel GUI / Re: cron_notificate_user

« on: July 05, 2020, 09:30:05 AM »

CWP itself uses php 7.1 at the backend. Take a look at the path.

Any try updating your cron job defining the php path.

/usr/local/bin/php /path/to/the/file.php

9

Installation / Re: MySQL errors when logging into CentOS Web Panel first time

« on: June 04, 2020, 11:27:47 PM »

Dis you install CWP on a fresh CentOS server or you already had apache, MySQL etc installed and running?

10

CentOS 7 Problems / Re: mysqld: Can't lock aria control file

« on: May 29, 2020, 05:46:58 PM »

Hi,

Thanks for the suggestion.

Yes, the above steps brings back the mysql server online I mean killing the mysql processes and restarting mysql and mariadb. The issue was continuing after every reboot. However after upgrade I forgot to start mariadb on boot which was causing issues. "systemctl enable mariadb" fixed the issue and everything running smooth now. Thanks again.

11

CentOS 7 Problems / Re: mysqld: Can't lock aria control file

« on: May 29, 2020, 02:19:06 PM »

Hi,

I have already tried increasing the number of max_open_files and it's not the issue I believe. As I'm seeing it's just a warning. Shouldn't make the whole database server down.

12

CentOS 7 Problems / Re: mysqld: Can't lock aria control file

« on: May 29, 2020, 01:35:42 PM »

One thing I forgot to mention, I upgraded MariaDB on multiple servers and experiencing the same with all of them.

13

CentOS 7 Problems / mysqld: Can't lock aria control file

« on: May 29, 2020, 01:29:36 PM »

Hi,

I upgraded MariaDB from 10.1 to 10.3 following the instructions here - https://www.mysterydata.com/update-upgrade-to-mariadb-10-3-on-vestacp-cwp-centos-7/

After upgrading the mysql server is working perfectly without issues but when I'm logged into CWP GUI as root I do see MySQL server is marked as stopped. Even if I try starting/restarting mariadb it doesn't start.

Here's the output from the terminal.

Code: [Select]

[root@server1 ~]# systemctl status mariadb
● mariadb.service - MariaDB 10.3.23 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: inactive (dead)
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
[root@server1 ~]#

After restarting mariadb I do see the following -

Code: [Select]

May 29 12:29:41 server1.domain.com systemd[1]: Starting MariaDB 10.3.23 database server...
May 29 12:29:42 server1.domain.com mysqld[1950]: 2020-05-29 12:29:42 0 [Note] /usr/sbin/mysqld (mysqld 10.3.23-MariaDB) starting as process 1950 ...
May 29 12:29:42 server1.domain.com mysqld[1950]: 2020-05-29 12:29:42 0 [Warning] Could not increase number of max_open_files to more than 16364 (request: 32183)
May 29 12:29:42 server1.domain.com mysqld[1950]: 2020-05-29 12:29:42 0 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds


May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [Note] InnoDB: 10.3.23 started; log sequence number 6504894; transaction id 4175
May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [Note] InnoDB: Buffer pool(s) load completed at 200529 12:07:06
May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [Note] Plugin 'FEEDBACK' is disabled.
May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with...ria-tmp-tables
May 29 12:07:06 server1.domain.com mysqld[1892]: 2020-05-29 12:07:06 0 [ERROR] Aborting
May 29 12:07:08 server1.domain.com systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
May 29 12:07:08 server1.domain.com systemd[1]: Failed to start MariaDB 10.3.23 database server.
May 29 12:07:08 server1.domain.com systemd[1]: Unit mariadb.service entered failed state.
May 29 12:07:08 server1.domain.com systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.


May 29 12:31:00 server1.domain.com mysqld[1950]: 2020-05-29 12:31:00 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
May 29 12:31:01 server1.domain.com mysqld[1950]: 2020-05-29 12:31:01 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
May 29 12:31:01 server1.domain.com mysqld[1950]: 2020-05-29 12:31:01 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
May 29 12:31:02 server1.domain.com mysqld[1950]: 2020-05-29 12:31:02 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
May 29 12:31:02 server1.domain.com mysqld[1950]: 2020-05-29 12:31:02 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
May 29 12:31:03 server1.domain.com mysqld[1950]: 2020-05-29 12:31:03 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
May 29 12:31:03 server1.domain.com mysqld[1950]: 2020-05-29 12:31:03 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
May 29 12:31:04 server1.domain.com mysqld[1950]: 2020-05-29 12:31:04 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11



I'm also seeing multiple mysqld process is running.

Code: [Select]

[root@server1 ~]# ps aux | grep mysqld
root      1244  0.0  0.0 115540  1708 ?        S    12:04   0:00 /bin/sh /usr/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/server1.domain.com.pid
mysql     1407  0.1  4.6 1309456 87888 ?       Sl   12:04   0:00 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/server1.domain.com.err --pid-file=/var/lib/mysql/server1.domain.com.pid
mysql     1892  0.1  2.7 652428 51596 ?        Ssl  12:05   0:00 /usr/sbin/mysqld
root      1992  0.0  0.0 112780   732 pts/0    S+   12:06   0:00 grep --color=auto mysqld


So I stopped mysql and then could successfully start mariadb but the same issue continues everytime I reboot. I tried deleting aria_log_control manually which didn't fix this. Can anyone please tell me why this is happening and is there something I can do to fix this? Any suggestion would be highly appreciated. Thanks for reading.

14

CentOS-WebPanel GUI / Re: Deleting old backups automatically

« on: May 17, 2020, 05:38:02 PM »

Hi,

Thanks for the script. So CWP newbackup GUI doesn't have option to automatically retentate old backups? As per the screenshot, I do see there's option to choose from Daily Backup Retention, Weekly Backup Retention and Monthly Backup Retention. I have just enabled Weekly Backup Retentaton on Sunday. Will it generate a weekly backup on every Sunday or delete old backups on Sunday?

https://imgur.com/a/7v3rGOZ

Screenshot added as reference. Thanks.

15

CentOS-WebPanel GUI / Deleting old backups automatically

« on: May 17, 2020, 04:37:21 PM »

Hi,

I enabled "newbackup" around a month ago and choose backups to generate everyday. The backups are generating everyday as expected but as I'm seeing the old backups don't get deleted automatically. I just want to keep only one copy of every weekday's backup. Is there something I'm missing on the backup settings? I know I can crate cron to delete backup files older than X days but I would like to know if there's anything I can do from GUI. Any suggestion will be highly appreciated. Thanks.

Code: [Select]

[root@server1 newbackup]# tree
.
`-- full
    |-- daily
    |   |-- Friday
    |   |   |-- 2020-04-17
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-01
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-08
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-15
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   |-- Monday
    |   |   |-- 2020-04-20
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-04
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-11
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   |-- Saturday
    |   |   |-- 2020-04-18
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-02
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-09
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-16
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   |-- Sunday
    |   |   |-- 2020-04-19
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-03
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-10
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   |-- Thursday
    |   |   |-- 2020-04-16
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-04-23
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-04-30
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-07
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-14
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   |-- Tuesday
    |   |   |-- 2020-04-21
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   |-- 2020-05-05
    |   |   |   `-- accounts
    |   |   |       `-- wappyco.tar.gz
    |   |   `-- 2020-05-12
    |   |       `-- accounts
    |   |           `-- wappyco.tar.gz
    |   `-- Wednesday
    |       |-- 2020-04-22
    |       |   `-- accounts
    |       |       `-- wappyco.tar.gz
    |       |-- 2020-04-29
    |       |   `-- accounts
    |       |       `-- wappyco.tar.gz
    |       |-- 2020-05-06
    |       |   `-- accounts
    |       |       `-- wappyco.tar.gz
    |       `-- 2020-05-13
    |           `-- accounts
    |               `-- wappyco.tar.gz
    `-- manual
        `-- accounts
            `-- wappyco.tar.gz

63 directories, 27 files
[root@server1 newbackup]#