Here goes ... could use some pointers guys.

[quote:76f63ba669][i:76f63ba669]Originally posted by rpmws[/i:76f63ba669]

OH yea .. 400 happy sites/clients[/quote:76f63ba669]

My advice, don't upgrade. THere is not much difference between 1.3.20 and 1.3.22, and you said it yourself:

400 happy sites/client. If they are happy, keep them that way. I doubt if anyone is upset that you are not running 1.3.22!

 

cd /tmp/
wget http://layer1.cpanel.net/buildapache.sea
chmod +x buildapache.sea
./buildapache.sea

when the options menu comes up just select exit, save conf yes. (If you have recompiled apache before with custom configs then you may want to go threw some of the stuff in here). After that it will start the upgrade.

once your back at the prompt

/usr/local/apache/bin/apachectl stop
/usr/local/apache/bin/apachectl startssl

I'm not possitive about mod_gzip, you may have to re-install this after the apache install, i would just test it out first and if it doesnt work then reinstall it ( I have yet to install mod_gzip or use it)

hope that helps.

If you have any problems with apache not restarting right and your getting pressured IM me, my AOL S/N is octekshaun

 

I did the buildapache.sea upgrade today and Apache was broke with error: [notice] child pid 3070 exit signal Segmentation fault (11)

It ended up to be mod_perl, if you take out Mod Perl, restart Apache and then Apache works.

# AddModule mod_perl.c

So, I then saw where if you install the apacheasp.sea, it has fixed the problem with others.

I did that but it's still not loading ..

But when I look at the loaded perl modules, I see that mod perl is running ..

Any ideas?




[quote:0d461e54e6][i:0d461e54e6]Originally posted by shaun[/i:0d461e54e6]

cd /tmp/
wget http://layer1.cpanel.net/buildapache.sea
chmod +x buildapache.sea
./buildapache.sea

when the options menu comes up just select exit, save conf yes. (If you have recompiled apache before with custom configs then you may want to go threw some of the stuff in here). After that it will start the upgrade.

once your back at the prompt

/usr/local/apache/bin/apachectl stop
/usr/local/apache/bin/apachectl startssl

I'm not possitive about mod_gzip, you may have to re-install this after the apache install, i would just test it out first and if it doesnt work then reinstall it ( I have yet to install mod_gzip or use it)

hope that helps.

If you have any problems with apache not restarting right and your getting pressured IM me, my AOL S/N is octekshaun

[/quote:0d461e54e6]

 

I think I did a restart instead of stop and restart after installing the apacheasp.sea file, at any rate, it seems to be working now after installing this file.. But the buildapache.sea did make the blood pressure rise for a bit.

 

i have upgraded 7 machines so far today my self, and so far they have all came back working file. I used the above to do it also. but then again the 7 machines didnt have any extra plugins installed (1 had jsp).

 

I went with the defaults, except I turned Php safe mode off for software reasons. I also checked perl module.

Then watched it do it's thing.. Make sure you are not on root partition, needs plenty of room.


Then

/usr/local/apache/bin/apachectl stop
/usr/local/apache/bin/apachectl startssl

If your site does not come up, look at Apache error log ..

I had the error : [notice] child pid 3070 exit signal Segmentation fault (11)

tail -200 /usr/local/apache/logs/error_log

If you have same thing, you might then try and uncomment the modperl in your httpd.conf and try a stop and restart again ..

If site comes up, then you might be OK now ..

I then installed apacheasp.sea, enabled mod perl in httpd.conf and stopped and restarted apache again, all works great now.

 

Well, I thought all was working fine but I'm seeing perl sript errors all over the place, 500 premature end of script. Looks like something in perl is broke too.

Dammit .. Any ideas?

 

Can this be because suEXEC mechanism is enabled Now?

If so, whats the fix?

Is this suEXEC worth the hastle or should I just recompile again without it?

What a mess ..

 

ya sorry /tmp is not a good place if it's not big enougf.

Here at ochosting we all ways give / atleast 2gig's in space for dedicated servers and on our shareds around 7gig's for /



NOTICE ** venturesonline CUSTOMERS, DO NOT RUN THE BUILDAPACHE.SEA!!!!! DO NOT!!!! it will cause apache to not start.

 

do it some where with enought space.

mkdir /usr/local/tmp

and you can put it their if your /usr partition has enough space.


If suExec is causing your scripts to not work then log into the WHM and turn suExec off.

Or.... You can run the fix script for suExec. This should fix all permissions with suexec. /scripts/fixsuexeccgiscripts

you can run /scripts/fixeverything if you like also.

 

What is:

/usr/local/apache/bin/apachectl stop
/usr/local/apache/bin/apachectl startssl

Would it work to simply click the apache restart button in WHM, or should I run the above commands explicitly?

thanks!

 

Yes, thats where I did ours..

By the way, I ended up recompiling without suEXEC again, installing apacheasp.sea again and shutting off suEXEC and all works fine again ..

Whew..

That suEXEC looks like a project in itself I don't need right now.



[quote:cb2bb82b6c][i:cb2bb82b6c]Originally posted by rpmws[/i:cb2bb82b6c]

so all we need is a empty hole to stick the install long enough to do the installation ? right //I have about 30 GB left in a /backup drive ..would that do?[/quote:cb2bb82b6c]

 

ventures...

for all ventures online servers...

http://www.venturesonline.com/forums/showthread.php?s=&threadid=2946