Geekzone: technology news, blogs, forums
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.

219 posts

Master Geek

Topic # 24904 6-Aug-2008 10:34
Send private message

Good morning everyone Laughing

I have a problem, a very headache problem, with Apache2 on our server.  Our firm has a webserver that uses Apache2. It has been running excellent for many years until recently. One of our customers update their webpage and Apache2 keeps stopped responding at random hours.  restart doesn't work we have to kill the processor then restart then it will start but maybe 10 hours later it stops.

We have checked for an infinite loop on the customer's code and found nothing, there isn't any include inside include and for what I was told PHP prevent those include inside include to take any action anyway. We talked to our customer's programmer, he thinks it must be Dos Attack. But we have checked with the log and there is nothing as such.

I checked with bugs report on debian website, nothing mention about it. Our senior system admin believes there might be a funny code in our customer's script that cause this problem.

I'd like to help but my knowledge of PHP and Apache2 is very limited. Could someone give me a suggestion or a recommendation of what may cause these freezes and where I should look?

Many thanks in advance.

We'll never be too old to learn, and we learn at least one new thing every day.

Create new topic
BDFL - Memuneh
61503 posts

Uber Geek
+1 received by user: 12218

Lifetime subscriber

  Reply # 154575 6-Aug-2008 10:39
Send private message

Perhaps start by finding if the new code is actually causing the problem? You could restore the previous version of the code and if everything is stable then you know it is the new code.

If it is the new code you might want to do a peer review again. And perhaps load it on a stage server and run some load tests to see if it's something that happens only at certain level or at any level. And start some debug?

All very basic - unit testing, stress testing, regression testing, system testing.

Back to drawing board.

889 posts

Ultimate Geek
+1 received by user: 93


  Reply # 154637 6-Aug-2008 13:59
Send private message

Have you looked in the error logs? That will tell you if there's a problem with the website. /var/log/apache2/error.log or something like that.

219 posts

Master Geek

  Reply # 154917 7-Aug-2008 12:36
Send private message

Yes, have a look in that but can't see anything unusual, can't find anything on customer's code either. Last night we tried down grade PHP5 to PHP4, not easy and not working well.

Our network admin found it at midnight last night, there's a bug call FUTEX, something to do with shared memory on our vserver. So we moved our customer to a different server... so far we haven't got any problem.

Only time will tell :-P

Thanks for all your help.

[moderator, could you lock this thread please? We've found the cause and our admin is fixing the problem. Thank you.]

We'll never be too old to learn, and we learn at least one new thing every day.

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:

Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:

Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:

Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.