Programs keep running without finishing

teguh123

When I access my most heavily populated website I got this message:

teguh: I saw Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, example@example.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. Apache/1.3.37

The hosting support says that I did bad coding.

Some of my code simply keep running without terminating.

How the hell I was going to debug that sort of thing?

Also is there a way to make my script to just give up and die after 1 minute?

rsmith

Can you post the script generating the error? Make sure to use the built in php tags to preserve syntax and formatting.

teguh123

Here's the thing.... The script is VERY long... However, this is the error_log that I receive:

[30-Dec-2007 17:06:20] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 4344 bytes) in /home/obedient/public_html/tools.php on line 98
[30-Dec-2007 18:48:51] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 38524561 bytes) in /home/obedient/public_html/tools.php on line 104
[30-Dec-2007 18:49:31] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 20624717 bytes) in /home/obedient/public_html/slap1.php on line 449
[30-Dec-2007 20:42:16] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 5496 bytes) in /home/obedient/public_html/tools.php on line 98
[30-Dec-2007 21:18:18] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 35986245 bytes) in /home/obedient/public_html/slap1.php on line 448
[30-Dec-2007 22:12:24] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 21827842 bytes) in /home/obedient/public_html/tools.php on line 104
[30-Dec-2007 22:33:55] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 15480501 bytes) in /home/obedient/public_html/slap1.php on line 449
[31-Dec-2007 00:13:16] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 18295605 bytes) in /home/obedient/public_html/slap1.php on line 449
[31-Dec-2007 01:50:22] PHP Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 22195591 bytes) in /home/obedient/public_html/tools.php on line 104

And the code around that is

slap1.php around 449
reportDebugMessage("Length of Content When Beginning to Scrap " .strlen($content) . "\nLine: ". LINE . "File: " .FILE." Function: ". FUNCTION . "<br/>" );
$content = preg_replace("'<style[^{>]?>.?</style>'si",'',$content);}

$content = preg_replace("'<script[^{>]?>.?</script>'si",'',$content);}
$content = preg_replace("'<link[^{>]?>'si",'',$content);}

$content = preg_replace("'<body[^>]?>'si",'<body>',$content);

		//echo "fetch: " . measuretime1() . "|";

tools.php around 104
$bufferar = explode ("\r\n\r\n", $buffer, 2);
//print_r ($bufferar);

		//print_r ($bufferar);

My best guesses is that my program surf a web and then try to analyze the content. Once in a while it scanned a really large file.

That's all.

I wonder how to fix that?

Weedpacket

teguh123 wrote:
My best guesses is that my program surf a web and then try to analyze the content.

You mean you don't know?!

Suggestion: don't try and read the entire content of a page at once (as would happen if you were using file_get_contents(), say) since that would block until either the read is complete or the whole thing blows up. Use [man]fread[/man] to read it in chunks instead. Work on each chunk before reading the next.

teguh123

Is there a way to tell php to just give up and stop after a certain amount of time?

Horizon88

set_time_limit() comes to mind, but it's really not a time issue, as Weedpacket said. You're reading pages that are larger than the allocated memory for your PHP scripts - either up the limit of allowed memory, or read less at once.

teguh123

I look at phpini and saw this:

max_execution_time 30 30
max_input_time 60 60
memory_limit 40M 40M

How could procs keep running when those safeguard is in place.

Weedpacket

Because, like I said, file_get_contents() blocks until it has read everything. Not until afterwards does PHP have the chance to look at the time that has been spent. (Indeed, there is a note on the page about max_execution_time setting to this effect.)

Which is why I suggested not using file_get_contents() but [man]fread[/man] instead. That solves both the time and the space problem. Further, you can set the timeout on the stream itself so that it doesn't block forever while waiting for a chunk.

teguh123

I don't think I use file_get_contents.

That being said, is there a way to make sure that curl and file_get_contents always terminate after certain amount of time?

I believe I have made sure of that one too.

Weedpacket

teguh123 wrote:
I don't think I use file_get_contents.

If you can't find out for yourself whether you do or not, then maybe whoever wrote it could help.

teguh123 wrote:
That being said, is there a way to make sure that curl and file_get_contents always terminate after certain amount of time?

Wouldn't it make more sense to find out if you use it or not first? (PS. The answer is no; which is (again) why I suggested not using it.)

teguh123

I think I figured out. I use curl. I didn't use file_get_contents Many advices against it.