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]
1
PHP Selector / Re: PHP-FPM Rebuild -PHP upgrade or downgrade always failed rebuild on Rocky Linux 8
« on: April 06, 2024, 05:15:35 PM »
yes this is fresh install.Can you give me more information about RockLinux Issue on CWP?
do you have any references or links that I can check?
do you have any references or links that I can check?
2
PHP Selector / PHP-FPM Rebuild -PHP upgrade or downgrade always failed rebuild on Rocky Linux 8
« on: April 03, 2024, 05:49:18 PM »
Hi Guys,
I always encountered PHP-FPM rebuild failed even if its upgrade to the next php release for specific version or downgrade or just any rebuild or install of php install.
checking whether to enable PCRE JIT functionality... yes
checking whether to enable the SQLite3 extension... yes
checking bundled sqlite3 library... yes
checking for ZLIB support... yes
checking if the location of ZLIB install directory is defined... /usr
checking for zlib version >= 1.2.0.4... 1.2.11
checking for gzgets in -lz... no
configure: error: ZLIB extension requires gzgets in zlib
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Last metadata expiration check: 0:01:11 ago on Wed Apr 3 10:46:58 2024.
Package libsodium-1.0.18-2.el8.x86_64 is already installed.
Package libsodium-devel-1.0.18-2.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 55 28505 55 15691 0 0 34259 0 --:--:-- --:--:-- --:--:-- 34259 100 28505 100 28505 0 0 62237 0 --:--:-- --:--:-- --:--:-- 62102
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 9: /opt/alt/php-fpm73/usr/bin/phpize: No such file or directory
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 10: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 14: /opt/alt/php-fpm73/usr/bin/php-config: No such file or directory
ERROR: Missing extension file /sodium.so
Build Completed
###################
Error:Can't add notification!
I always encountered PHP-FPM rebuild failed even if its upgrade to the next php release for specific version or downgrade or just any rebuild or install of php install.
checking whether to enable PCRE JIT functionality... yes
checking whether to enable the SQLite3 extension... yes
checking bundled sqlite3 library... yes
checking for ZLIB support... yes
checking if the location of ZLIB install directory is defined... /usr
checking for zlib version >= 1.2.0.4... 1.2.11
checking for gzgets in -lz... no
configure: error: ZLIB extension requires gzgets in zlib
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Skipping as php build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Last metadata expiration check: 0:01:11 ago on Wed Apr 3 10:46:58 2024.
Package libsodium-1.0.18-2.el8.x86_64 is already installed.
Package libsodium-devel-1.0.18-2.el8.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
chdir: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 55 28505 55 15691 0 0 34259 0 --:--:-- --:--:-- --:--:-- 34259 100 28505 100 28505 0 0 62237 0 --:--:-- --:--:-- --:--:-- 62102
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 9: /opt/alt/php-fpm73/usr/bin/phpize: No such file or directory
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 10: ./configure: No such file or directory
make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target 'install'. Stop.
/usr/local/cwpsrv/htdocs/resources/conf/el8/php-fpm_selector/external_modules/7.3/sodium.sh: line 14: /opt/alt/php-fpm73/usr/bin/php-config: No such file or directory
ERROR: Missing extension file /sodium.so
Build Completed
###################
Error:Can't add notification!
3
MySQL / Re: Mariadb 10.2 suddenly stopped working in Centos 7 error code=exited 203/EXEC
« on: December 13, 2023, 06:44:50 AM »
I compared it and looks like this is the major difference since your given link content is from 10.4 and mine is 10.2
ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION
But I tried to used that and still encountered the same error.
ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION
But I tried to used that and still encountered the same error.
4
MySQL / Re: Mariadb 10.2 suddenly stopped working in Centos 7 error code=exited 203/EXEC
« on: December 13, 2023, 06:04:18 AM »
heres 50 lines journalctl
[root@mydb ~]# journalctl -x -u mariadb -n 50
-- Logs begin at Tue 2023-12-12 18:21:58 PST, end at Tue 2023-12-12 21:58:33 PST. --
Dec 12 18:22:10 mydb systemd[1]: Starting MariaDB 10.2.44 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has begun starting up.
Dec 12 18:22:10 mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 12 18:22:10 mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Dec 12 18:22:10 mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 12 18:22:10 mydb systemd[1]: mariadb.service failed.
and yes, 3306 is not in used unless as I mentioned that I can run the mysql using this command /usr/sbin/mysqld
[root@mydb ~]# journalctl -x -u mariadb -n 50
-- Logs begin at Tue 2023-12-12 18:21:58 PST, end at Tue 2023-12-12 21:58:33 PST. --
Dec 12 18:22:10 mydb systemd[1]: Starting MariaDB 10.2.44 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has begun starting up.
Dec 12 18:22:10 mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 12 18:22:10 mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Dec 12 18:22:10 mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 12 18:22:10 mydb systemd[1]: mariadb.service failed.
and yes, 3306 is not in used unless as I mentioned that I can run the mysql using this command /usr/sbin/mysqld
5
MySQL / Re: Mariadb 10.2 suddenly stopped working in Centos 7 error code=exited 203/EXEC
« on: December 13, 2023, 04:57:40 AM »
Hi thanks for the reply, the file mysql and mysqld files are existing.Also here is the logs.
[root@mydb ~]# journalctl -xe mariadb
Failed to add match 'mariadb': Invalid argument
Failed to add filters: Invalid argument
[root@mydb ~]# journalctl -u mariadb
-- Logs begin at Tue 2023-12-12 18:21:58 PST, end at Tue 2023-12-12 20:53:53 PST. --
Dec 12 18:22:10 mydb.mydb systemd[1]: Starting MariaDB 10.2.44 database server...
Dec 12 18:22:10 mydb.mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 12 18:22:10 mydb.mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
Dec 12 18:22:10 mydb.mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 12 18:22:10 mydb.mydb systemd[1]: mariadb.service failed.
[root@mydb ~]#
also ,if I run only the /usr/sbin/mysqld command, the mariadb instance will start the database and the CWP7 dashboard is accessible.
But unfortunately it is not working properly maybe due the systemd mariadb service is required to make the CWP fully working?
we are really confused right now on this issue because this issue just occured and we dont have any changes on the system.
[root@mydb ~]# journalctl -xe mariadb
Failed to add match 'mariadb': Invalid argument
Failed to add filters: Invalid argument
[root@mydb ~]# journalctl -u mariadb
-- Logs begin at Tue 2023-12-12 18:21:58 PST, end at Tue 2023-12-12 20:53:53 PST. --
Dec 12 18:22:10 mydb.mydb systemd[1]: Starting MariaDB 10.2.44 database server...
Dec 12 18:22:10 mydb.mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 12 18:22:10 mydb.mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
Dec 12 18:22:10 mydb.mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 12 18:22:10 mydb.mydb systemd[1]: mariadb.service failed.
[root@mydb ~]#
also ,if I run only the /usr/sbin/mysqld command, the mariadb instance will start the database and the CWP7 dashboard is accessible.
But unfortunately it is not working properly maybe due the systemd mariadb service is required to make the CWP fully working?
we are really confused right now on this issue because this issue just occured and we dont have any changes on the system.
6
MySQL / Mariadb 10.2 suddenly stopped working in Centos 7 error code=exited 203/EXEC
« on: December 13, 2023, 04:13:45 AM »
Hi to all,
Unfortunately my production server suddenly encountered this error in Mariadb 10.2.Due to this issue
my server is down for 3 days.Theres no specific error on logs that contains information about this issue.
[root@mydb ~]# systemctl status mysqld
● mariadb.service - MariaDB 10.2.44 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sun 2023-12-10 03:19:00 PST; 2s ago
Docs: man:mysqld(
https://mariadb.com/kb/en/library/systemd/
Process: 163260 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=203/EXEC)
Process: 163231 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 163228 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 163260 (code=exited, status=203/EXEC)
Dec 10 03:19:00 mydb systemd[1]: Starting MariaDB 10.2.44 database server...
Dec 10 03:19:00 mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 10 03:19:00 mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
Dec 10 03:19:00 mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 10 03:19:00 mydb systemd[1]: mariadb.service failed.
Unfortunately my production server suddenly encountered this error in Mariadb 10.2.Due to this issue
my server is down for 3 days.Theres no specific error on logs that contains information about this issue.
[root@mydb ~]# systemctl status mysqld
● mariadb.service - MariaDB 10.2.44 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Sun 2023-12-10 03:19:00 PST; 2s ago
Docs: man:mysqld(
https://mariadb.com/kb/en/library/systemd/
Process: 163260 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=203/EXEC)
Process: 163231 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 163228 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 163260 (code=exited, status=203/EXEC)
Dec 10 03:19:00 mydb systemd[1]: Starting MariaDB 10.2.44 database server...
Dec 10 03:19:00 mydb systemd[1]: mariadb.service: main process exited, code=exited, status=203/EXEC
Dec 10 03:19:00 mydb systemd[1]: Failed to start MariaDB 10.2.44 database server.
Dec 10 03:19:00 mydb systemd[1]: Unit mariadb.service entered failed state.
Dec 10 03:19:00 mydb systemd[1]: mariadb.service failed.
7
CentOS-WebPanel Bugs / goaccess statistic report for monthly has no data
« on: January 22, 2023, 05:57:54 PM »
Do you have a solution to fix the issues in goaccess statistic report for monthly has no data?
This was encountered for all the domains.
This was encountered for all the domains.
8
Information / Needs CWP Pro License for 10 IP address
« on: September 03, 2022, 03:42:46 PM »
Hi to all,
Is there someone here that can allow our 10 IP addresses server to run CWP Pro again? This is temporary (maybe 3 days) for us to turn back to CWP Pro.
Let me know and share your contact number then my boss will contact you for payment and negotiation.
Is there someone here that can allow our 10 IP addresses server to run CWP Pro again? This is temporary (maybe 3 days) for us to turn back to CWP Pro.
Let me know and share your contact number then my boss will contact you for payment and negotiation.
9
CentOS-WebPanel Bugs / Re: htaccess file protect can access file when file permission is 444
« on: February 19, 2022, 07:38:11 AM »
Yes I have nginx in front.
10
CentOS-WebPanel Bugs / htaccess file protect can access file when file permission is 444
« on: February 18, 2022, 05:51:35 PM »
I have a site file that I need to protect by htaccess and htpasswd
https://site/test/test.txt
when the file permission is 444 meaning , read access from web client , the file content will be open and the htaccess login prompt will not show, but when I change the file permission to 440 "no read access for web client , the htaccess login prompt will show and will accept the valid user, but then the file will be "Forbidden
You don't have permission to access this resource".
let me know if you have a fix on this.
https://site/test/test.txt
when the file permission is 444 meaning , read access from web client , the file content will be open and the htaccess login prompt will not show, but when I change the file permission to 440 "no read access for web client , the htaccess login prompt will show and will accept the valid user, but then the file will be "Forbidden
You don't have permission to access this resource".
let me know if you have a fix on this.
11
PHP / PHP extension "Zend Optimizer|Zend Guard Loader" is not loaded.
« on: April 18, 2021, 12:56:57 PM »
Hi to all
I encountered this error during CMS Server tester
Error:
CMS Server Tester
Your server was tested to meet all CMS requirements. Following errors were encountered an need to be fixed to run the software:
PHP extension "Zend Optimizer|Zend Guard Loader" is not loaded.
Please verify your server configuration. Make sure that extension "Zend Optimizer|Zend Guard Loader" is enabled. [ Check for a possible solution here. ]
thank you for anyone who can answer to solved this
I encountered this error during CMS Server tester
Error:
CMS Server Tester
Your server was tested to meet all CMS requirements. Following errors were encountered an need to be fixed to run the software:
PHP extension "Zend Optimizer|Zend Guard Loader" is not loaded.
Please verify your server configuration. Make sure that extension "Zend Optimizer|Zend Guard Loader" is enabled. [ Check for a possible solution here. ]
thank you for anyone who can answer to solved this
12
Apache / How to setup and run cgi perl scripts on cwp Apache
« on: January 30, 2021, 07:40:53 AM »
Good day to all
We are working on executing cgi script on cwp apache website, and we already followed the procedure on below link but we ares still encountering "Internal Server Error".
#Reference link -> but still didn't work
https://wiki.centos-webpanel.com/how-to-run-cgi-scripts-with-apache
note:
My test perl script can run on cli without issue.
thanks :-).
We are working on executing cgi script on cwp apache website, and we already followed the procedure on below link but we ares still encountering "Internal Server Error".
#Reference link -> but still didn't work
https://wiki.centos-webpanel.com/how-to-run-cgi-scripts-with-apache
note:
My test perl script can run on cli without issue.
thanks :-).
13
Updates / error: %pre(dovecot-1:2.2.36-6.el7_8.1.x86_64) scriptlet failed
« on: October 01, 2020, 08:13:49 AM »
Encountered this error when updating dovecot package
BELOW ARE THE ERRORS:
"dovecot.x86_64
error: %pre(dovecot-1:2.2.36-6.el7_8.1.x86_64) scriptlet failed, exit status 5
Verifying : 1:dovecot-2.2.36-6.el7_8.1.x86_64 1/2
Verifying : 1:dovecot-2.2.36-6.el7.x86_64 2/2
Failed:
dovecot.x86_64 1:2.2.36-6.el7 dovecot.x86_64 1:2.2.36-6.el7_8.1
Complete!"
BELOW ARE THE ERRORS:
"dovecot.x86_64
error: %pre(dovecot-1:2.2.36-6.el7_8.1.x86_64) scriptlet failed, exit status 5
Verifying : 1:dovecot-2.2.36-6.el7_8.1.x86_64 1/2
Verifying : 1:dovecot-2.2.36-6.el7.x86_64 2/2
Failed:
dovecot.x86_64 1:2.2.36-6.el7 dovecot.x86_64 1:2.2.36-6.el7_8.1
Complete!"
Pages: [1]
