Forums | Mahara Community
Support
/
Upgrading mahara to 1.1.2 - site unavailable
17 April 2009, 8:16
Hello, we attempted to upgrade mahara from 1.0.4 to the 1.1.2 version. When we try to access the upgrade script we get
"Mahara: Site unavailable
And the log shows the following error messages:
[Fri Apr 17 08:10:01 2009] [error] [client xx]
[Fri Apr 17 08:10:01 2009] [error] [client xx] [WAR] 92 (lib/mahara.php:1835) get_real_size called without valid size suffix
[Fri Apr 17 08:10:01 2009] [error] [client xx] Call stack (most recent first):
[Fri Apr 17 08:10:01 2009] [error] [client xx] * get_real_size("536870912") at /www/eportfolios/lib/mahara.php:1794
[Fri Apr 17 08:10:01 2009] [error] [client xx] * raise_memory_limit("32M") at /www/eportfolios/lib/mahara.php:156
[Fri Apr 17 08:10:01 2009] [error] [client xx] * ensure_sanity() at /www/eportfolios/init.php:79
[Fri Apr 17 08:10:01 2009] [error] [client xx] * require("www/eportfolios/init.php") at
/www/eportfolios/lib/cron.php:50
[error] [client xxxx] [WAR] ef (lib/mahara.php:1835) get_real_size called without valid size suffix
[Fri Apr 17 08:38:30 2009] [error] [client xx] Call stack (most recent first):
[Fri Apr 17 08:38:30 2009] [error] [client xx] * get_real_size("536870912") at /www/eportfolios/lib/mahara.php:1794
[Fri Apr 17 08:38:30 2009] [error] [client xx] * raise_memory_limit("32M") at /www/eportfolios/lib/mahara.php:156
[Fri Apr 17 08:38:30 2009] [error] [client xx] * ensure_sanity() at /www/eportfolios/init.php:79
[Fri Apr 17 08:38:30 2009] [error] [client xx] * require("/www/eportfolios/init.php") at
/www/eportfolios/index.php:31
[Fri Apr 17 08:38:30 2009] [error] [client xx]
Not really sure what went wrong..Any advise will be much appreciated!
thanks,
Renu
19 April 2009, 17:12
Hi - interesting, that looks like a bug in Mahara. Your memory_limit PHP setting is set to 536870912 which doesn't have a suffix on the end to say what unit it's in. I presume it's bytes though. Mahara has crashed because it couldn't find the suffix.
Workaround for now: set your memory_limit setting to some value like '512M'.
Solution: we can patch get_real_size to assume bytes by default, in a future version. I have filed a bug for this.