Fatal error: Maximum execution time of 30 seconds

Anon

Hi all,
I keep getting "Fatal error: Maximum execution time of 30 seconds exceeded " message for any script longer then a few lines. All the postings that I could find on the Internet suggest that I increase the max_execution_time in my php.ini file to more then 30 seconds. But that doesn't really solve the problem, because even 30 seconds is unacceptable!!! (Who would wait for 30 seconds or more to load one page) I was hoping it would be a max of 1-2 seconds for the script to execute when I decided to go for PHP.

I am running PHP4 with ZEND optimizer on a Win98 maching with Apache 1.3.12.

Any ideas? What could possibly be wrong with my setup?

My e-mail is milos-popovic@home.com

Anon

It's evident that you are doing something
wrong, PHP doesn't have anything to do
with this. You should have faced the
same problem in perl, python or asp.
Analize your code, profile it using PHP
functions (see article about timing script
execution in this site) and find the
bottlenck.

Luis.

Anon

Thanks a lot for your answer,

But this delay happens only when I log on from outside of @Home network. For example, if I log on to my site (which is on @Home network) from another @Home customer, the process is extremely fast, and it works great. But, if, for example, I try to connect to my site (which is on @Home network) from, say, PSI net computer, or GlobalServe, or AOL, I almost always get an Maximum Execution Time Exceeded error. ?? Now, does this have anything to do with proxies set up at @Home networks??

By the way I am also using MySQL, but it's mostly stuff from tutorials so I can not imagine anything being so wrong. Can it be something in the setup of my MySQL, or Apache or Php?

Thanks a lot for your help again though,

Milos

Anon

I'm getting this problem too with a PHP / mysql application (well known BBS called vBulletin) running on a Win2K server.

I can never pin it down to a particular action - it always seems to be at an odd point. I know it happens because I see it in my error logs. For the forst time in months, I have seen it on the screen in front of me.

I believe it is a mysql problem since the PHP code used by vBulletin can got to be the best and most widely used around.

I want to investigate the mysql site and run those utilities that check the health of the db since mine is about 20 mB now in size. The problem started when moving from one server to another AND using a later version of mySQL - 3.23.41

In your case, it all sounds so simple and the problem occurs when accessing your site remotely. This sounds very odd - I think it may be a red herring and that mysql is the problem.