Random 503 errors on PHP - cPanel 60, EasyApache 4, PHP 7.0
Hi,
So couple of days we decided to move to a Linux-based VPS with cPanel, once we got all domains set up and licenses up, we immediately started seeing 503 errors pages randomly, somewhere it would open a route/page, and then next it wouldn't and so on.
We have EA4 with PHP 7.0 + PHP-FMP enabled for that domain in WHM. These are the packages:
Apache 2.4
[LIST]
config
config-runtime
mod_asis
mod_bwlimited
mod_cgi
mod_deflate
mod_env
mod_expires
mod_headers
mod_mpm_prefork
mod_proxy
mod_proxy_fcgi
mod_proxy_http
mod_security2
mod_ssl
mod_suexec
mod_suphp
mod_unique_id
mod_version
tools
PHP 7.0
[LIST]
build
libc-client
pear
php-cli
php-common
php-curl
php-devel
php-fpm
php-ftp
php-iconv
php-imap
php-litespeed
php-mbstring
php-mcrypt
php-mysqlnd
php-odbc
php-pdo
php-pgsql
php-posix
php-xml
php-xmlrpc
php-zip
runtime
We can't fall back to 5.x PHP because our app has lot of stuff using that only became available with PHP 7+ - is it possible that cPanel-based instance is just that unstable with PHP 7.0?
-
Its unlikely to be a problem with PHP 7, check your Apache configuration for limits and increase if needed. Monitor httpd from 'top' from the CLI. 0 -
Its unlikely to be a problem with PHP 7, check your Apache configuration for limits and increase if needed. Monitor httpd from 'top' from the CLI.
It is FPM error, when I turn it of it stops, and I see some other active threads here with the same issue. this is the line from error log: [Sun Dec 18 12:55:55.224548 2016] [proxy_fcgi:error] [pid 18212] [client xx.xxx.xxx.xxx:61618] AH01079: failed to make connection to backend: httpd-UDS [Sun Dec 18 12:55:57.496377 2016] [proxy:error] [pid 18211] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /opt/cpanel/ea-php70/root/usr/var/run/php-fpm/5f2f67918e7a9c66a4f4c6d181e276b03acd0dd7.sock (*) failed And it is happening irregularly as in - one page works and all of a sudden it starts throwing 503 than after 20 mins you go back to that page and it throws the error again.0
Please sign in to leave a comment.
Comments
2 comments