Word to the wise: Do ***NOT**** upgrade to Apache 2.2 with "EasyApache"

[erick_paper]

Read the hundreds of problems here. The stupid "EasyApache" program left my entire Apache installation hanging. My PHP code from the site began to appear as CODE!!!! How embarrasing and insecure is that. Why could this upgrade program not be coded so that if the "build" failed, then nothing was changed and everythign was left as-is? Stupid, stupid program.

Whatever the reason for failing, this program should NOT leave the users hanging with all these security problems and nowhere to go! Suggesting that we leave a ticket for cpanel, which will be answered a day or so later AT THE EARLIEST, is idiotic. The error in building, for those defensive types who will rush to this thread and try to defend:

---- CONTENTS OF THE BUILD FAIL ----

----------------------------------------------------------------------
Libraries have been installed in:
/home/cpeasyapache/src/eaccelerator-0.9.5.2/modules
If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
Build complete.
Don't forget to run 'make test'.
Installing shared extensions: /usr/local/lib/php/extensions/no-debug-non-zts-20060613/
find . -name \*.gcno -o -name \*.gcda | xargs rm -f
find . -name \*.lo -o -name \*.o | xargs rm -f
find . -name \*.la -o -name \*.a | xargs rm -f
find . -name \*.so | xargs rm -f
find . -name .libs -a -type d|xargs rm -rf
rm -f libphp.la modules/* libs/*
EAccelerator extension activated
-- End step 'Install EAccelerator' --
-- End opt 'EAccelerator for PHP' --
-- Begin 'IonCube Loader for PHP' is off--
-- End 'IonCube Loader for PHP' is off --
!! Resetting Apache configuration to default. !!
Updating Apache configuration
Updating Apache configuration
Distilled successfully
!! Failed to generate a syntactically correct Apache configuration (/usr/local/apache/conf/httpd.conf.1200656403):
Syntax error on line 29 of /usr/local/apache/conf/httpd.conf.1200656403:
module rewrite_module is built-in and can't be loaded
!!
!! Archiving successful build so it can be restored via --restore-archive once the httpd.conf are resolved !!
!! Done Archiving successful build !!
!! Restoring original working apache !!
!! Executing '/scripts/initfpsuexec' !!
!! Executing '/scripts/initsslhttpd' !!
Compiling report...
Sending report (496 bytes)...
!! If you want to create a support ticket with cPanel regarding this please reference 'BuildAP Report Id': '554164' !!
Report processed.
!! Feel free to submit a support ticket at https://tickets.cpanel.net/submit/index.cgi?reqtype=tickets !!
!! Verbose logfile is at '/usr/local/cpanel/logs/easy/apache/build.1200655478' !!

 

[isranet]

Did you try to rebuild it manually by SSH immediatelly after the fail?

 

[cPanelNick]

Please open a ticket at https://tickets.cpanel.net/submit/index.cgi?reqtype=tickets .. the longest wait time for the complimentary queue is currently about 70-80 minutes. However if you have priority support or this is a direct license the wait time is about 10 minutes at the time of this posting. Also if you submit the ticket directly from the easyapache build failure window in whm, it will be upgraded to the standard queue which currently has about a 15-25 minute wait time

 

[OMP]

I got 2.2 running and rebuilt it just the other day using the EasyApache 3. It did hang the first time and die, but 2nd time it went through np. Did have to manully fix something in the httpd.config afterwards though. forget what it was.

It is buggy, but it works.

 

[rs-freddo]

I built apache 2.2 with easyapache a couple of weeks ago and it ran smooth as silk. I ticked a bunch of modules and no problems. I was impressed.

 

[rligg]

Ditto. No problems, with like every module under the sun.

 

[steveheinsch]

Flawless install on Centos4.4 the first time...

 

[nat]

Please open a ticket at https://tickets.cpanel.net/submit/index.cgi?reqtype=tickets .. the longest wait time for the complimentary queue is currently about 70-80 minutes. However if you have priority support or this is a direct license the wait time is about 10 minutes at the time of this posting. Also if you submit the ticket directly from the easyapache build failure window in whm, it will be upgraded to the standard queue which currently has about a 15-25 minute wait time

Upgraded from apache 1 to 2. Apache failed right after building. Segmentation fault error. Already did http://www.cpanel.net/support/docs/ea/ea3/ea3_open_ssl_bug.html and tired to rebuild. Still errors.

I do not see an option for $300/year priority support at https://www.cpanel.net/store/index.cgi

I used ssh. I tried building apache with WHM and did not get a build failure window. However, apache has failed.

Apache has been down over 12 hours.

Ticket has been opened since 8 hours ago.

I guess there are 40 people in front of me for this problem caused by /scripts/easyapache. How do I get standard support?

 

[cPanelDavidG]

Upgraded from apache 1 to 2. Apache failed right after building. Segmentation fault error. Already did http://www.cpanel.net/support/docs/ea/ea3/ea3_open_ssl_bug.html and tired to rebuild. Still errors.

I do not see an option for $300/year priority support at https://www.cpanel.net/store/index.cgi

I used ssh. I tried building apache with WHM and did not get a build failure window. However, apache has failed.

Apache has been down over 12 hours.

Ticket has been opened since 8 hours ago.

I guess there are 40 people in front of me for this problem caused by /scripts/easyapache. How do I get standard support?

To receive complementary support, go to http://tickets.cpanel.net/submit/ and scroll down and follow the instructions for submitting a ticket without logging in.

I will remind our webmasters that the inability for non-customers to pay for priority support is still an issue.