Forums | Mahara Community
Support
/
Segmantation Fault in the cron.php
12 February 2009, 8:34
Hello,
I seem to have a problem with the cron om my server. It keeps giving an segmentation fault when I run the cron job. I've looked through the file but could not locate the problem anywhere. Is this a known issue?
php -f /var/www/mahara-1.0.9/htdocs/lib/cron.php ..
[DBG] 09 (lib/cron.php:62) ---------- cron running Thu, 12 Feb 2009 13:17:13 +0100 ----------
Segmentation fault
I'm currently running 1.0.9 of Mahara on an ubunto 8.10 server. And I have no clue what could cause this. Any input would be helpful.
Greets,
Yannick
php -v
PHP 5.2.4-2ubuntu5.4 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 25 2008 22:10:31)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
with XCache v1.2.1, Copyright (c) 2005-2007, by mOo
mysql -V
mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2
12 February 2009, 9:36
There's been a long standing bug in debian that I've been working around for ages to do with the order that the files in /etc/php5/conf.d are loaded. It only happens with php5-cli.
I can see that I've renamed pgsql.ini to 0_pgsql.ini in that directory to get around it - I think it's a problem when pgsql is loaded after curl, which is the alphabetical default.
I see you're using mysql, but I guess it's possible that you have the pgsql extension loaded as well?
This could be a long shot... but might be it.
12 February 2009, 10:44
woah, weird. Well it fixed the problem. I renamed the pgsql file like you said. Yeah, I forgot that I installed in on a PostgreSQL DB rather then MySQL.
Thanks a lot, that saved me ages to find myself. Thanks again anyways. Maybe an idea for the admins to put this somewhere on the wiki or install manual.
12 February 2009, 15:41
I think probably there should be a debian bug for it.... I have no idea what package to file it against though... maybe php5-cli
11 March 2009, 12:45
Yeah we had the same issue, found this post and applied the same trick... seems to resolve this specific issue, thanks!
Seems there are a few things in Debian / Ubuntu this is the second quirk in Debian / Ubuntu to have caused me trouble, the other being the way clam is added to the php config... 