|
|
| Author |
Message |
| Mikhail Kovalev |
 Posted: Thu Jan 31, 2008 11:07 pm |
|
|
|
|
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Thu Jan 31, 2008 11:43 pm |
|
|
|
|
And, a funny thing I think it always halts at the same line, which
looks like this:
$string_2 = file_get_contents($string_1);
|
|
| Back to top |
|
| axlq |
| Posted: Thu Jan 31, 2008 11:52 pm |
|
|
|
|
In article <bad6f896-4f0f-4b84-a779-bf1c082bcfd9@e6g2000prf.googlegroups.com>,
Mikhail Kovalev <mikhail_kovalev@mail.ru> wrote:
Quote: And, a funny thing I think it always halts at the same line, which
looks like this:
$string_2 = file_get_contents($string_1);
Try
echo $string1."\n";
That might explain what's happening. You may be trying to access a
locked file, and get a time-out while waiting for release.
-A
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Fri Feb 01, 2008 12:23 am |
|
|
|
|
On 1 Feb, 00:52, a...@spamcop.net (axlq) wrote:
Quote: In article <bad6f896-4f0f-4b84-a779-bf1c082bc...@e6g2000prf.googlegroups.com>,
Mikhail Kovalev <mikhail_kova...@mail.ru> wrote:
And, a funny thing I think it always halts at the same line, which
looks like this:
$string_2 = file_get_contents($string_1);
Try
echo $string1."\n";
That might explain what's happening. You may be trying to access a
locked file, and get a time-out while waiting for release.
-A
$string_1 is an url address, or hundreds of different, but similar
(same host) url address which are opened after each other. I know at
least some of them are working as I am able to watch the script
progress. I guess the reason it halts at this line is because
file_get_contents($string_1) usually takes around 1 second, while all
other following commands are just milliseconds. Statistically it makes
sence.
Basically, my problem is to get the script work longer than 3600
seconds
A friend of mine uses same script on a Mac OS X 10.5 with PHP 5.?.?,
with no problems
|
|
| Back to top |
|
| Jerry Stuckle |
| Posted: Fri Feb 01, 2008 7:28 am |
|
|
|
|
Mikhail Kovalev wrote:
Quote: Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Fri Feb 01, 2008 6:50 pm |
|
|
|
|
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Timeout 300 in httpd.conf?
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Fri Feb 01, 2008 7:32 pm |
|
|
|
|
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
=================> >> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
=================> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Fri Feb 01, 2008 8:15 pm |
|
|
|
|
On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
=================> >>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>> Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
=================> >> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
=================> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
I had no idea!
I had both php4 and php5 installed, and switched from php4 to php5 by
changing the LoadModule line in httpd.conf...
What exactly could I do to make it run as a module?
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Fri Feb 01, 2008 10:21 pm |
|
|
|
|
On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
=================> >>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>> Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
=================> >> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
=================> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
OK, figured it out. I used Denwer Apache + php4 distribution (some
years ago) which installs php as cgi
Somehow the cgi mode was preserved through upgrade... Reinstalled and
testing.
Thanks for pointing out the details!=)
|
|
| Back to top |
|
| Jerry Stuckle |
| Posted: Sat Feb 02, 2008 1:16 am |
|
|
|
|
Mikhail Kovalev wrote:
Quote: On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
|
|
| Back to top |
|
| Jerry Stuckle |
| Posted: Sat Feb 02, 2008 1:55 am |
|
|
|
|
Mikhail Kovalev wrote:
Quote: On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
|
|
| Back to top |
|
| Jerry Stuckle |
| Posted: Sat Feb 02, 2008 4:35 am |
|
|
|
|
Mikhail Kovalev wrote:
Quote: On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
OK, figured it out. I used Denwer Apache + php4 distribution (some
years ago) which installs php as cgi
Somehow the cgi mode was preserved through upgrade... Reinstalled and
testing.
Thanks for pointing out the details!=)
Good - glad to see you found it.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Sat Feb 02, 2008 2:40 pm |
|
|
|
|
On 1 Feb, 23:35, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
=================> >>>>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>>>> Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
=================> >>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>>http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
=================> >> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
OK, figured it out. I used Denwer Apache + php4 distribution (some
years ago) which installs php as cgi
Somehow the cgi mode was preserved through upgrade... Reinstalled and
testing.
Thanks for pointing out the details!=)
Good - glad to see you found it.
--
=================> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
Weirdest thing, this didn't fix the problem, still getting a fatal
error after 3600 seconds
Is it possible that this feature is somehow pre-compiled in the php
distribution package I'm using? If so, I may want to change to
something else
|
|
| Back to top |
|
| Jerry Stuckle |
| Posted: Sat Feb 02, 2008 9:04 pm |
|
|
|
|
Mikhail Kovalev wrote:
Quote: On 1 Feb, 23:35, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
OK, figured it out. I used Denwer Apache + php4 distribution (some
years ago) which installs php as cgi
Somehow the cgi mode was preserved through upgrade... Reinstalled and
testing.
Thanks for pointing out the details!=)
Good - glad to see you found it.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
==================
Weirdest thing, this didn't fix the problem, still getting a fatal
error after 3600 seconds
Is it possible that this feature is somehow pre-compiled in the php
distribution package I'm using? If so, I may want to change to
something else
Not that I know of. There should be no timeout in the PHP package. I
guess there could be in your OS; I've never seen one but then I haven't
had something run for 3600 cpu seconds, either. I didn't see anything
in the bug list on the php site which looked like it is related, either.
I still think there's another setting out there we aren't seeing, but I
don't know where it is.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
|
|
| Back to top |
|
| Mikhail Kovalev |
| Posted: Sun Feb 24, 2008 6:53 am |
|
|
|
|
On Feb 2, 4:04 pm, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Quote: Mikhail Kovalev wrote:
On 1 Feb, 23:35, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:55, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 20:16, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
On 1 Feb, 03:47, Jerry Stuckle <jstuck...@attglobal.net> wrote:
Mikhail Kovalev wrote:
Fatal error: Maximum execution time of 3600 seconds exceeded in z:\home
\localhost\www\somefile.php on line 138
php.ini setting fixes default max execution time at 30 sec,
In the script itself I have set_time_limit(0);
I have also tried set_time_limit(90000); with no luck.
Checked if php was running in safe mode, and it wasn't.
Are there any other reasons that can cause this behavior?
Thanks!
mvh
MK
Does your server have a timeout value specified?
--
=================> >>>>>>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>>>>>> Timeout 300 in httpd.conf?
I wouldn't think that would give a 3600 second timeout. Are you running
PHP as a module or a CGI? What does phpinfo() show you for your timeout
value?
--
=================> >>>>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>>>>http://07db0bc537297586.paste.se/
Timeouts Connection: 300 - Keep-Alive: 15
Is this it
It looks like you're running PHP as a CGI, not a module. Do you have a
timeout set for your CGI's? For instance, if you're using FastCGI it is
an option there, IIRC.
BTW - why are you running PHP as a CGI instead of a module?
--
=================> >>>> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================> >>> OK, figured it out. I used Denwer Apache + php4 distribution (some
years ago) which installs php as cgi
Somehow the cgi mode was preserved through upgrade... Reinstalled and
testing.
Thanks for pointing out the details!=)
Good - glad to see you found it.
--
=================> >> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
Weirdest thing, this didn't fix the problem, still getting a fatal
error after 3600 seconds
Is it possible that this feature is somehow pre-compiled in the php
distribution package I'm using? If so, I may want to change to
something else
Not that I know of. There should be no timeout in the PHP package. I
guess there could be in your OS; I've never seen one but then I haven't
had something run for 3600 cpu seconds, either. I didn't see anything
in the bug list on the php site which looked like it is related, either.
I still think there's another setting out there we aren't seeing, but I
don't know where it is.
--
=================> Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstuck...@attglobal.net
=================
I finally narrowed it down to a bit of code which causes the problem,
by trial and error, and you can imagine it was not easy to do because
each test takes 60 min. Could be a bug...
There were some things I didn't mentioned:
- The problem existed only in Windows for some reason. The script
always worked perfectly in Unix systems.
- I had an earlier version of the script with slightly different
features which didn't had the same problem. So basically, I checked
every minor update I made there, and it turned out the line which
either activates some security trigger or something is include_once()
inside one of the functions, I changed it to include() and moved it to
global level and the problem disappeared. Weird...
|
|
| Back to top |
|
|
|
All times are GMT
The time now is Wed May 16, 2012 10:26 pm
|
|
