EasyApache froze during update...now get errors trying to recompile

[azn_romeo_4u]

I first tried to recompile with easyapache, and then it froze. It froze like at the end, when it said build "complete" It wasn't complete though cuz it was still doing something...not sure what it was...I had the server hard rebooted after that because it completely froze.

Now i'm trying to recompile it and i run into errors...

In file included from /home/cpeasyapache/src/php-5.2.6/ext/mbstring/libmbfl/filters/mbfilter_euc_cn.c:31:
/home/cpeasyapache/src/php-5.2.6/ext/mbstring/oniguruma/config.h:1:24: php_config.h: No such file or directory
make: *** [ext/mbstring/libmbfl/filters/mbfilter_euc_cn.lo] Error 1
!! 'make' failed with exit code '512' !!
!! Restoring original working apache !!
!! Executing '/scripts/initsslhttpd' !!
!! Restarting 'httpd' ... !!
!! Failed to restart Apache. !!
!! Apache restart failed. Unable to load pid from pid file and no httpd process found in process list.
If apache restart reported success but it failed soon after, it may be caused by oddities with mod_ssl.
You should run /scripts/ssl_crt_status as part of your troubleshooting process. Pass it --help for more details.
Also be sure to examine apache's variouse log files.
Apache Restart Output:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
no listening sockets available, shutting down
Unable to open logs
Log:
2008-11-12 23:18:40.254 [NOTICE] [Child: 10166] Start shutting down gracefully ...
2008-11-12 23:18:40.254 [NOTICE] [Child: 10167] Shut down successfully!
2008-11-12 23:18:40.256 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets belong to process 10167 !
2008-11-12 23:18:40.358 [NOTICE] [AutoRestarter] child process with pid=10167 exited with status=0!
2008-11-12 23:18:41.210 [NOTICE] [Child: 10166] Shut down successfully!
2008-11-12 23:18:41.210 [NOTICE] [lsphp5] stop worker processes
2008-11-12 23:18:41.210 [INFO] [lsphp5] kill pid: 10168
2008-11-12 23:18:41.220 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets belong to process 10166 !
2008-11-12 23:18:41.220 [INFO] [AutoRestater] Clean up child process with pid: 10168
2008-11-12 23:18:41.323 [NOTICE] [AutoRestarter] child process with pid=10166 exited with status=0!
2008-11-12 23:18:41.323 [NOTICE] [PID:10162] Server Stopped! !!
!! Executing '/scripts/initfpsuexec' !!
!! Executing '/scripts/initsslhttpd' !!
Compiling report...
Sending report (212 bytes)...
Report processed.
!! Verbose logfile is at '/usr/local/cpanel/logs/easy/apache/build.1226560957' !!

Should i have apache running during easyapache? I can't get apache to start up as well...

 

[cPanelDavidG]

You should let our technical analysts take a look at this. You can do so by submitting a support ticket: http://tickets.cPanel.net/submit

 

[alexheizer]

You should let our technical analysts take a look at this. You can do so by submitting a support ticket: http://tickets.cPanel.net/submit

Hi peeps!

Was there a resolution to this that we could try first without having to bother you with logging into our server? Some lib or perlmod which needs to be updated?

Getting the same message.

TIA

 

[cPanelDavidG]

Hi peeps!

Was there a resolution to this that we could try first without having to bother you with logging into our server? Some lib or perlmod which needs to be updated?

Getting the same message.

TIA

You may wish to closely review the verbose error logs for what is causing the issue, or the issue that is causing EasyApache to fail so you can take corrective action.

 

[alexheizer]

You may wish to closely review the verbose error logs for what is causing the issue, or the issue that is causing EasyApache to fail so you can take corrective action.

Since I said we received the exact same messages in the verbose error logs, I thought that whatever you did to fix this on their server might apply. In other words, I asked because the error log didn't indicate what corrective action to take. Hence, my asking what corrective action was taken on a server which experienced exactly what I experienced.

I suppose that cPanel can report the exact same error at the exact same time for different reasons that you can't explain after looking at someone else's system who had this happen on?

I guess I'll submit a support ticket and let you take your time to look at it, instead of just solving it the same way you solved it for this other user...