Resource temporarily unavailable problem

[ozzi4648]

One of our users is seeing this on his site:

[Mon Nov 25 05:13:07 2002] [error] [client 194.82.103.38] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:07 2002] [error] [client 194.82.103.152] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:07 2002] [error] [client 194.82.103.152] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.138] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.138] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.36] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.36] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.144] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:06 2002] [error] [client 194.82.103.144] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:05 2002] [error] [client 194.82.103.143] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:05 2002] [error] [client 194.82.103.143] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:05 2002] [error] [client 194.82.103.40] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:05 2002] [error] [client 194.82.103.40] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:04 2002] [error] [client 194.82.103.37] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:04 2002] [error] [client 194.82.103.37] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl
[Mon Nov 25 05:13:04 2002] [error] [client 194.82.103.141] File does not exist: /home/outwest/public_html/500.shtml
[Mon Nov 25 05:13:04 2002] [error] [client 194.82.103.141] (11)Resource temporarily unavailable: couldn't spawn child process: /home/outwest/public_html/cgi-bin/ads/ads.pl

I dont think the server is running out of resources. Its got over 1gig of memory running a P4 2ghz server. One thing puzzles me. An ad rotation script call ads.pl that does nothing but rotate banners seems to be the program that always spawns the resource messages. Also, this is the only user on the box. Everthing in httpd.conf seems just fine. Anyone seen this on their cPanel box? I couldnt find any reference to this here on the forums. Strange! Is cPanel limiting the number of processes that a user can start?

 

[ozzi4648]

*BUMP*

I cant believe nobody has seen this problem on their server. We get over 200 of these a day, still. Closed ticket from Cpanel says nothing and i suspect when i reported it nothing was done, they didnt even log in. They just closed the ticket. Whats up with this?

There are only 60sites on this box and 1 cgi driven site. These resource error started back when the box only had 1 site online.

Anyone have any ideas? Setting max connections to 256 doesnt solve the problem.

 

[Website Rob]

Off-hand, I would say this is more of script problem.

I would make sure all required modules are installed, correct permissions have been set (for dir. and/or files) and that any required files have been installed or created -- some scripts require files that must, first be manually created.

If you were to run:

perl -d /home/outwest/public_html/cgi-bin/ads/ads.pl

you might get some helpful information. Otherwise, contact the script maker or your local Perl guru.

 

[ozzi4648]

[quote:4fb700af7c][i:4fb700af7c]Originally posted by Website Rob[/i:4fb700af7c]

Off-hand, I would say this is more of script problem.

I would make sure all required modules are installed, correct permissions have been set (for dir. and/or files) and that any required files have been installed or created -- some scripts require files that must, first be manually created.

If you were to run:

perl -d /home/outwest/public_html/cgi-bin/ads/ads.pl

you might get some helpful information. Otherwise, contact the script maker or your local Perl guru. [/quote:4fb700af7c]

Thanks, thats what we thought. The load during times the errors are generated are only at 2% if that. The user claims its Apache on our server. I think its his scripts. Poorly written piece of junk!

 

[monotreme]

on a related note

I am getting this error a lot. If the culprit is some user written piece of junk I just say your program your problem, but as often as not seems to be the culprit is cpanel itself. Our server is heavily loaded.

[Tue Nov 30 17:20:12 2004] [error] [client xx.xxx.xx.xx] (11)Resource temporarily unavailable: couldn't spawn child process: /usr/local/cpanel/cgi-sys/Count.cgi

After follows usually another file does not exist error about not having a custom 500.shtml file. from the same ip. It is not a mortal sin for them to not have this, it should just fall thru to the generic error handler.

Is something wrong with my Count.cgi file? that could be precipitating this? Its binary file, yes?



explanations? advice?

 

[chirpy]

One thing you should check is the size of log files in:

/etc/httpd/logs/

and

/etc/httpd/domlogs/

Make sure that not log file in either directory is more than (or near) 2GB. If there is, then this can cause havoc with Apache. You shoudl remove the offender and restart Apache to create a new file.

If that's not the case, then how many Apache children do you have running when you see the problem? This will give you an approximation:

ps axf | grep httpd | wc -l

If it's anywhere near 150 (or whatever MaxClients is set to in your httpd.conf), then that will cause problems.

Another thing can can help depending on the problem, is to turn off the KeepAlive directive and restart Apache.

 

[monotreme]

Thanks for the pointers

found a couple of chunkies in domlog from departed hog users whom I have already persuaded to go elsewhere.

zapped them and I'll check the error logs starting now to see if those errors stop happening.


THANKS A BUNCH!

 

[monotreme]

still getting those errors though...