Apache Problems

[anand]

Originally posted by shaun
anand,

Sorry it was late last night, i wasnt trying to be a dick if thats the way it came off. I'm just stating that by looking at the patch it's doing more than just editing that file, by the looks of it, it doesnt even use that os.h file.


My point was you shouild try my buildapache.sea since the patch that cpanel was using by default is in it.

No offence taken Shaun.

I respect you for a person who atleast has more knowledge and experience. I just was not able to understand the point, thats what i asked.

Anyways what i rote helped me sort the probs on my server, when i saw this post i thought perhaps it could help someone else also ;-)

regards,

Anand

 

[Carl Ramirez]

Latest buildapache has the option to do this without any of these hassles:
do the following:

1.Run buildapache.sea
2.select option 5
3.Select Increase fd_setsize to 16384
4.Disable PHP
5.Exit and the compilation will complete sucessfully.

 

[thomas]

Originally posted by Carl Ramirez
Latest buildapache has the option to do this without any of these hassles:
do the following:

1.Run buildapache.sea
2.select option 5
3.Select Increase fd_setsize to 16384
4.Disable PHP
5.Exit and the compilation will complete sucessfully.

Yes, but it didn't work, it didn't increase the fd_setsize.

 

[thomas]

Originally posted by shaun
Well i dont have any of these FD Size problems but i found and fixed the problem i beleive. If i didnt i fixed one of them . You guys can download the new buildapache.sea from me here

http://www.ndchost.com/cp/buildapache.sea

give it a shot. let me know what happens

Looking good, have been running for 20+ hours now, and had no problems with perl. :D

Thanks again!!

 

[shaun]

np, glad to help, nicks a busy guy.

 

[shaun]

i total forgot about this until nick reminded me but make sure /usr/local/apache/bin/apachectl has ulimit -n 16384 or apache will be as reliable as a windows machine. (seg faults).

Also nick says he fixed the typo in the buildapache... you guys dont have to use mine anymore.

 

[Darkedge]

Question

Is it ok if it looks like this
#!/bin/sh
ulimit -n 16384
#
# Apache control script designed to allow an easy command line interface
# to controlling Apache. Written by Marc Slemko, 1997/08/23
#
# The exit codes returned are:
# 0 - operation completed successfully
# 1 -
# 2 - usage error
# 3 - httpd could not be started
# 4 - httpd could not be stopped
# 5 - httpd could not be started during a restart
# 6 - httpd could not be restarted during a restart
# 7 - httpd could not be restarted during a graceful restart
# 8 - configuration syntax error
#
# When multiple arguments are given, only the error from the _last_
# one is reported. Run "apachectl help" for usage info
#

 

[shaun]

looks fine to me

 

[Darkedge]

FUN FUN FUN

Well I decided to use cpanel's version of build apache today since they released a new one and within 15 minutes crashie crashie. THe filedescriptor problem came back. I am recompiling with shaunx version now again.

 

[Darkedge]

also

also with shauns version I am still getting segfaults even though i used the apachectl file I posted part of above. shoudl it only have the one ulimit -n 16384 entry right. DO i need it somewhere else or jsut any where in the file

 

[cPanelNick]

did you compile in mcrypt ?

 

[Darkedge]

Yeppers

Yes I did it was requested bya user on the system

 

[shaun]

Dont add mcrypt some type of problem with it

 

[Darkedge]

this is bad

Ok if I use shauns script I get seg faults everywhere If i use the cpanel new build apache I get file descriptor problems. I have built shauns script without mcrypt amd still have the seg fault problems.

this is my configure for shauns. I would rather use cpanels build but it brings back the file descriptor issue. If I remove mcrypt for the cpanel bu7ild will that fix the file descriptor issue.
$SETMODULE{''} = 1;
$SETMODULE{'attach'} = 0;
$SETMODULE{'auth_mysql'} = 0;
$SETMODULE{'bwprotect'} = 1;
$SETMODULE{'bytes'} = 0;
$SETMODULE{'dav'} = 0;
$SETMODULE{'expire'} = 0;
$SETMODULE{'fdsetsize'} = 1;
$SETMODULE{'frontpage'} = 1;
$SETMODULE{'limit'} = 1;
$SETMODULE{'perl'} = 0;
$SETMODULE{'php'} = 1;
$SETMODULE{'php-422'} = 0;
$SETMODULE{'php-423'} = 0;
$SETMODULE{'php-bcmath'} = 1;
$SETMODULE{'php-cal'} = 1;
$SETMODULE{'php-curl'} = 0;
$SETMODULE{'php-curl-ssl'} = 0;
$SETMODULE{'php-flash'} = 0;
$SETMODULE{'php-ftp'} = 1;
$SETMODULE{'php-gd'} = 1;
$SETMODULE{'php-gd-ttf'} = 1;
$SETMODULE{'php-imap'} = 1;
$SETMODULE{'php-mbstring'} = 0;
$SETMODULE{'php-mcrypt'} = 0;
$SETMODULE{'php-ming'} = 0;
$SETMODULE{'php-mk'} = 1;
$SETMODULE{'php-mysql'} = 1;
$SETMODULE{'php-pdflib'} = 0;
$SETMODULE{'php-pear'} = 1;
$SETMODULE{'php-pg'} = 0;
$SETMODULE{'php-sablot'} = 1;
$SETMODULE{'php-safe'} = 0;
$SETMODULE{'php-sockets'} = 1;
$SETMODULE{'php-suexec'} = 0;
$SETMODULE{'php-trackvars'} = 1;
$SETMODULE{'php-ttf'} = 0;
$SETMODULE{'php-vs'} = 1;
$SETMODULE{'php-zlib'} = 1;
$SETMODULE{'php3'} = 1;
$SETMODULE{'php3-imap'} = 0;
$SETMODULE{'php3-mysql'} = 1;
$SETMODULE{'php3-trackvars'} = 1;
$SETMODULE{'phpsuexec'} = 0;
$SETMODULE{'rewrite'} = 1;
$SETMODULE{'roaming'} = 0;
$SETMODULE{'ssl'} = 1;
$SETMODULE{'suexec'} = 1;
$SETMODULE{'throttle'} = 0;
1;

 

[shaun]

Are you sure apache/php finished compiling and didnt error out? If it errored out you will still be running the old version.

 

[Darkedge]

I am sure.

So I should now be using cpanels new build apache with mcrypt and make sure that I add that ulimit to apachectl. If i do this i shoul dnot have either the fildescriptor problem or the seg fault problem???

 

[Darkedge]

Hrm

If I try to use the new buildapache it still gives me the filedescriptor problem.

 

[shaun]

can you paste the last 10-20 lines of the build process.

 

[HSAdam]

I did that and it still shows the ulimit as 1024 which is to low... how can I fix this???

 

[shaun]

do this as root

head /usr/local/apache/bin/apachectl

you should see this in there ulimit -n 16384

you might see somthing like this too...

bash-2.05$ head /usr/local/apache/bin/apachectl
#!/bin/sh
ulimit -n 1024
ulimit -n 4096
ulimit -n 8192
ulimit -n 16384

Thats alright as long as the ulimit -n 16384 is the last one.