preventing system crashes

[Oliver Spiesshofer]

Hi,

I made a mistake in a script that completely froze my linux-based server:

I passed an array instead of a number to a function like:

function plg_ratingimg($rating)
{
global $plug_picrank;
for ($i=0;$i<$rating;$i++)
{
$out.=$plug_picrank;
}
return $out;
}

where $plug_picrank is a simple HTML string.

Where is the weakness in the apache or php setup that something like this
can freeze the server?

thanks

Oliver

[Erwin Moller]

Oliver Spiesshofer wrote:

Hi,

I made a mistake in a script that completely froze my linux-based server:

I passed an array instead of a number to a function like:

function plg_ratingimg($rating)
{
global $plug_picrank;
for ($i=0;$i<$rating;$i++)
{
$out.=$plug_picrank;
}
return $out;
}

where $plug_picrank is a simple HTML string.

Where is the weakness in the apache or php setup that something like this
can freeze the server?

thanks

Oliver

Hi Oliver,

Are you sure it is a systemcrash?
I think only PHP stops responding untill the scripttimeout time has elapsed.

When I had a similar situation (a very long calculation) ONLY scripts on
that site stopped responding.
Apache just neatly continued to serve other sites.

Solution? I don't know. Write better scripts? :P

Regards,
Erwin Moller

[Oliver Spiesshofer]

Erwin Moller
<si******************************************@spam yourself.com> wrote in
news:42***********************@news.xs4all.nl:

Hi Oliver,

Are you sure it is a systemcrash?
I think only PHP stops responding untill the scripttimeout time has
elapsed.

No it doesnt, strange enough.
FTP and SSH to the machine dont work anymore either "Connection refused"...

Oliver

[Jerry Sievers]

Oliver Spiesshofer <ol****@email.com> writes:

I made a mistake in a script that completely froze my linux-based server:
I passed an array instead of a number to a function like:

function plg_ratingimg($rating)
{
global $plug_picrank;
for ($i=0;$i<$rating;$i++)
$out.=$plug_picrank;

Assuming this thing iterated a bazillion times, at least during the
PHP configured max script execution time, it busied the CPU to 100%
and also consumed a huge amount of memory.

Not sure if your PHP might be configured to have large amount of
memory available but a runaway loop like this can certainly cause a
server to THRASH, though probably not crash (as you have suggested).

Suspect the memory use put you over the acceptable paging limit for
this box.

Why don't you log into the machine interactively with telnet, SSH or
similar, run the defective PHP script and see what happens. Does your
Linux panic and halt? Or does the machine just go catatonic for a
while.

Can you see the machine physically and check for excessibe disk
activity which would indicate rapid paging.

If the interactive session does continue to respond, top, vmstat and
various other diagnostic tools can help you learn what's really
happening.

HTH

--
-------------------------------------------------------------------------------
Jerry Sievers 305 854-3001 (home) WWW ECommerce Consultant
305 321-1144 (mobile http://www.JerrySievers.com/

[Erwin Moller]

Oliver Spiesshofer wrote:

Erwin Moller
<si******************************************@spam yourself.com> wrote in
news:42***********************@news.xs4all.nl:

Hi Oliver,

Are you sure it is a systemcrash?
I think only PHP stops responding untill the scripttimeout time has
elapsed.

No it doesnt, strange enough.
FTP and SSH to the machine dont work anymore either "Connection
refused"...

Oliver

Oops... That IS bad, Oliver.

I suggest you try Jerry Sievers suggestions in the other thread.

Login and see what the machine is doing.
'top' is a quick way to see what takes up the CPU time.

As far as I know, this shouldn't be possible...
Did you configure the machine yourself?
If it is at some provider (shared), ask them. :P

Regards,
Erwin Moller