Bug #51302 [Opn->Bgs]: wierd error with latest snapshot
Edit report at http://bugs.php.net/bug.php?id=51302&edit=1
ID: 51302
Updated by: jani@php.net
Reported by: jachym dot tousek at gmail dot com
Summary: wierd error with latest snapshot
-Status: Open
+Status: Bogus
Type: Bug
Package: Compile Failure
Operating System: Debian etch
PHP Version: 5.3SVN-2010-03-15 (snap)
New Comment:
No idea nor it's bug in PHP either.
Previous Comments:
------------------------------------------------------------------------
[2010-03-17 17:02:30] jachym dot tousek at gmail dot com
Yes, I also think this is some issue with the system but how can i
repair it? It is VPS.
I've compiled PHP 5.3.1 on second server (same OS) some time ago - no
issues.
------------------------------------------------------------------------
[2010-03-17 11:44:56] jani@php.net
Yes, can you try on different server? Sounds more like your system has
some issues..
------------------------------------------------------------------------
[2010-03-16 15:38:55] jachym dot tousek at gmail dot com
Thats the problem. I have some issue with PHP 5.3.2 (different) which
causes that I can compile it but only if i don't use --with-mysql. PHP
5.3.1 compiled, but I couldn't run tests and if I run for example "php
-v", I get the response but the command does NOT exit until i kill it
myself. With that, every request on the server runs new apache2 process,
but all those "apache2" processes don't exit even when the page is
completely loaded. So I have to every few hours run some commands to
kill those processes (or the memory will run out).
This means I have some problem with every version but every time it's
different...
Any Ideas?
------------------------------------------------------------------------
[2010-03-16 10:05:27] jani@php.net
What is the last 5.3 version you CAN build? 5.3.2? 5.3.1?
------------------------------------------------------------------------
[2010-03-15 17:13:48] jachym dot tousek at gmail dot com
Yeah I know, it actually happened few times that memory was not enough.
But when that happened, I the error report was different so that's not
it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=51302
--
Edit this bug report at http://bugs.php.net/bug.php?id=51302&edit=1
Thread (8 messages)