EasyApache still running - prevents cPanel update - safe to kill multiple processes in sleep state?

pkiff

Member
Jul 31, 2007
11
0
51
I'm getting a daily error message from upcp (cPanel update) when cron calls for it to run. The error says:
"E EasyApache is currently running. Please wait for EasyApache to complete before running cPanel Update (upcp)."

I recently ran EasyApache multiple times while reconfiguring my PHP build, including the addition of PDO and mbstring support. During that sequence of runs, I several times ran into problems with EasyApache "freezing", usually at the step of generating phar, similar to the problem described in Upgrades Stuck on Phar:
https://forums.cpanel.net/f442/upgrades-stuck-phar-342051.html

However, after patiently repeating the process over the course of a day, I would eventually get to a successful build. So my build history shows three or four failed builds, but the most recent build was successful and Apache and PHP certainly seem to be working as expected, running live sites as expected.

I'm running EasyApache 3.22.14 on a XEN VPS slice with CentOS 6.

I think I must have somehow started multiple overlapping EasyApache builds through the cPanel GUI. And some of the stalled processes are still sitting there stalled, preventing upcp from running. I want to understand if it is okay for me to kill all these.

When I run
# ps aux | grep easyapache
I pull up 7 processes (one of which is grep itself):
Code:
root      4050  0.0  0.0  99032   376 ?        S    Oct08   0:00 /home/cpeasyapache/src/php-5.4.20/sapi/cli/php -n -d extension_dir=/home/cpeasyapache/src/php-5.4.20/modules -d open_basedir= -d output_buffering=0 -d memory_limit=-1 -d phar.readonly=0 -d safe_mode=0 ext/phar/phar.php pack -f ext/phar/phar.phar -a pharcommand -c auto -x \.svn -p 0 -s /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/phar.php -h sha1 -b /usr/local/bin/php /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/
root      9564  0.0  0.0 100212   384 ?        S    Oct09   0:00 /home/cpeasyapache/src/php-5.4.20/sapi/cli/php -n -d extension_dir=/home/cpeasyapache/src/php-5.4.20/modules -d open_basedir= -d output_buffering=0 -d memory_limit=-1 -d phar.readonly=0 -d safe_mode=0 ext/phar/phar.php pack -f ext/phar/phar.phar -a pharcommand -c auto -x \.svn -p 0 -s /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/phar.php -h sha1 -b /usr/local/bin/php /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/
root     12276  0.0  0.1 138400   760 ?        S    Oct08   0:15 [bg installer] /usr/local/cpanel/whostmgr/docroot/cgi/easyapache.pl
root     13997  0.0  2.4 137292 12276 ?        S    Oct09   0:16 [bg installer] /usr/local/cpanel/whostmgr/docroot/cgi/easyapache.pl
root     22186  0.0  0.1 103236   852 pts/0    S+   08:57   0:00 grep easyapache
root     26400  0.0  1.3 138040  6728 ?        S    Oct09   0:14 [bg installer] /usr/local/cpanel/whostmgr/docroot/cgi/easyapache.pl
root     30060  0.0  0.8 100212  4244 ?        S    Oct09   0:00 /home/cpeasyapache/src/php-5.4.20/sapi/cli/php -n -d extension_dir=/home/cpeasyapache/src/php-5.4.20/modules -d open_basedir= -d output_buffering=0 -d memory_limit=-1 -d phar.readonly=0 -d safe_mode=0 ext/phar/phar.php pack -f ext/phar/phar.phar -a pharcommand -c auto -x \.svn -p 0 -s /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/phar.php -h sha1 -b /usr/local/bin/php /home/cpeasyapache/src/php-5.4.20/ext/phar/phar/
I understand from various warnings I saw when launching EasyApache that I shouldn't kill an EasyApache process.

Is that right? What should I do to get rid of these sleeping processes. Can I kill them all? Should I reboot the server? Why don't they clean up themselves?
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,911
2,233
363
cPanel Access Level
DataCenter Provider
Twitter
Re: EasyApache still running - prevents cPanel update - safe to kill multiple processes in sleep sta

Hello :)

Yes, in this case you should kill those processes if they are hanging. You should also run another EasyApache build after killing those processes to ensure it completes successfully.

Thank you.