Your message dated Thu, 22 Aug 2013 13:19:07 +0200
with message-id
<CALjhHG_Of4jvBGQzTWWUbo7Luy+B=etxtt2v7vcuohhtbng...@mail.gmail.com>
and subject line Re: [php-maint] Bug#720127: php5: Maximum execution time
exceeded immediately...
has caused the Debian Bug report #720127,
regarding php5: Maximum execution time exceeded immediately...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
720127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720127
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php5
Version: 5.5.1+dfsg-2
Severity: normal
Dear Maintainer,
php5 seems to throw a maximum execution time exceeded immediately.
I see this on owncloud and ampache.
I've set the default timeout to 3600 (1 hour), but the error that time
limit is exceeded comes almost immediately.
Here's an example backtrace with timestamps. By my reading that's
about a tenth of a second before the excepton is thrown.
If I up the timelimit to 10 hours, the process succeeds.
( ! ) Fatal error: Maximum execution time of 3600 seconds exceeded in
/usr/share/php/php-gettext/streams.php on line 113
Call Stack
# Time Memory Function Location
1 0.0004 229952 {main}( ) ../login.php:0
2 0.0565 1471984 require(
'/usr/share/ampache/www/templates/show_login_form.inc.php' ) ../login.php:176
3 0.0570 1472488 T_( ) ../show_login_form.inc.php:66
4 0.0570 1472520 __( ) ../gettext.inc:406
5 0.0570 1472568 _gettext( ) ../gettext.inc:285
6 0.0580 1483624 gettext_reader->translate( ) ../gettext.inc:278
7 0.0580 1484208 gettext_reader->load_tables( ) ../gettext.php:254
8 0.1082 1986656 FileReader->read( ) ../gettext.php:161
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10.0-rc4+ (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages php5 depends on:
ii libapache2-mod-php5 5.5.1+dfsg-2
ii php5-common 5.5.1+dfsg-2
php5 recommends no packages.
php5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.5.1+dfsg-2
On Tue, Aug 20, 2013 at 11:41 PM, Peter Chubb <[email protected]>wrote:
>
>
> On 20/08/2013, at 10:04 PM, Ondřej Surý <[email protected]> wrote:
>
> I saw you are using:
>
> Kernel: Linux 3.10.0-rc4+ (SMP w/2 CPU cores)
>
> Could you try with prepackaged kernel (or even just some non-rc)?
>
>
> yup. the problem goes away in that case. I straced php and saw the
> SIGPROF came too early ... so the problem is in the upstream kernel,
>
> Thanks for your help and attention. Looks like not a php bug.
>
>
> O.
>
>
> On Tue, Aug 20, 2013 at 12:41 PM, <[email protected]> wrote:
>
>> >>>>> "Peter" == Peter Chubb <[email protected]> writes:
>>
>> >>>>> "Ondřej" == Ondřej Surý <[email protected]> writes:
>> Ondřej> could you try that with some simple script?
>>
>> Actually here's an even simpler script:
>>
>>
>> <?php
>> @set_time_limit(3600);
>> @ini_set('max_execution_time', 3600);
>> while (1) {
>> echo date(DATE_RFC822) ;
>> echo "\n";
>> }
>> ?>
>>
>>
>> I find this behaves correctly on some machines. but not the one
>> running my webserver :-(
>>
>
>
>
> --
> Ondřej Surý <[email protected]>
>
>
--
Ondřej Surý <[email protected]>
--- End Message ---
