Submitted by sgrayban on Thu, 08/27/2009 - 06:03
I get cron reports and lately I have been seeing the following:
sh: line 1: 31310 Segmentation fault /usr/bin/php5-cgi -v 2>&1 < /dev/null
If I run this manually in console I get the same ting but not all the time:
/etc/webmin/virtual-server/collectinfo.pl |grep php5-cgi
sh: line 1: 28639 Segmentation fault /usr/bin/php5-cgi -v 2>&1 < /dev/null
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Thu, 08/27/2009 - 11:45 Comment #1
Interesting, it looks like the segfault is coming from php, rather than from collectinfo.pl directly .. which makes it hard for us to debug.
Which PHP version and from which repository are you running?
Submitted by sgrayban on Thu, 08/27/2009 - 13:49 Comment #2
It's the default php version for lenny...
root@newsletter:~# php -v
PHP 5.2.6-1+lenny3 with Suhosin-Patch 0.9.6.2 (cli) (built: Apr 26 2009 20:09:03)
Copyright (c) 1997-2008 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
Submitted by JamieCameron on Thu, 08/27/2009 - 14:50 Comment #3
I think you are going to have to raise this issue with Debian then, as the crash is inside the PHP code .. unless there is something Virtualmin is doing to trigger it, which seems unlikely as it just runs "php5-cgi -v" to get the version number.
Submitted by sgrayban on Thu, 08/27/2009 - 14:55 Comment #4
It's only happening on one server that's what has me confused.
I have no idea what VM does which is why I started here to find out...
"/usr/bin/php5-cgi -v" doesnt seg fault but "/usr/bin/php5-cgi -v 2>&1 < /dev/null" does now and then.
Maybe I should update to the dotdeb packages which I use on the other servers which seems to not have this issue.
Submitted by JamieCameron on Thu, 08/27/2009 - 14:56 Comment #5
Yeah, if there is a new PHP version available I would recommend using that..
Submitted by sgrayban on Thu, 08/27/2009 - 17:18 Comment #6
upgrading to 5.2.9 solved the seg faults
Submitted by JamieCameron on Thu, 08/27/2009 - 17:53 Comment #7
Cool!
Submitted by Issues on Thu, 09/10/2009 - 19:18 Comment #8
Automatically closed -- issue fixed for 2 weeks with no activity.