Apache 2.0 Upgrade hosed my server

[slinky]

Nothing easy about EasyApache. Was told to upgrade from 1.3 to 2.0 and now after a rebuild my server won't even start up. My support request was initially denied by cpanel but I think a second attempt with the support number (another number apparently) may have gone through. I'm trying to revert back to 1.3 and hope to high heaven that it works like it used to but I'm getting the following:

oot 24742 0.7 1.7 69580 35772 ? S 14:40 0:00 /usr/local/cpanel/whostmgr/bin/whostmgr ./reshttpd


Jan 29 13:40:49 myhostname kernel: httpd[24753]: segfault at 00007fff76afdff8 rip 00002aaaac257f31 rsp 00007fff76afe000 error 6 httpd has failed, please contact the sysadmin.

If I could upgrade to 2.0, great but I'd be thrilled just getting back to the status quo. Ugh... this is painful, especially with the modules that were installed and worked.

[cPanelDavidG]

Nothing easy about EasyApache. Was told to upgrade from 1.3 to 2.0 and now after a rebuild my server won't even start up. My support request was initially denied by cpanel but I think a second attempt with the support number (another number apparently) may have gone through. I'm trying to revert back to 1.3 and hope to high heaven that it works like it used to but I'm getting the following:

oot 24742 0.7 1.7 69580 35772 ? S 14:40 0:00 /usr/local/cpanel/whostmgr/bin/whostmgr ./reshttpd


Jan 29 13:40:49 myhostname kernel: httpd[24753]: segfault at 00007fff76afdff8 rip 00002aaaac257f31 rsp 00007fff76afe000 error 6 httpd has failed, please contact the sysadmin.

If I could upgrade to 2.0, great but I'd be thrilled just getting back to the status quo. Ugh... this is painful, especially with the modules that were installed and worked.

Is the IP address you provided the primary IP address of the server? We only license the primary IP address of the server.

You can verify the license status of an IP address by visiting: http://verify.cpanel.net

[chirpy]

Just an idea, usually when I've seen httpd v2 or v2.2 segfault-ing it's because of a log file that's at or over 2GB in size in /usr/local/apache/domlogs or /usr/local/apache/logs. If there is one of that size, remove it and try restarting.