Forums | Mahara Community

Support /
regularly error-messages in the cron-log

anonymous profile picture
Account deleted
Posts: 39

05 August 2011, 8:52


in the log-file of the mahara-cronjob (mahara-version 1.3.6) there are every day the same error-messages at the same time, like this:

[Fri Jul 29 05:50:03 2011] [error] [client] [WAR] ec (lib/mahara.php:2360) DOMDocument::loadHTML() [domdocument.loadhtml]: Tag wbr invalid in Entity, line: 2670
[Fri Jul 29 05:50:03 2011] [error] [client] Call stack (most recent first):
[Fri Jul 29 05:50:03 2011] [error] [client]   * log_message("DOMDocument::loadHTML() [domdocument.loadhtml]: Ta...", 8, true, true, "/var/www/mahara/lib/mahara.php", 2360) at /var/www/mahara/lib/errors.php:444
[Fri Jul 29 05:50:03 2011] [error] [client]   * error(2, "DOMDocument::loadHTML() [<a href='domdocument.load...", "/var/www/mahara/lib/mahara.php", 2360, array(size 3)) at Unknown:0
[Fri Jul 29 05:50:03 2011] [error] [client]   * DOMDocument->loadHTML("<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Trans...") at /var/www/mahara/lib/mahara.php:2360
[Fri Jul 29 05:50:03 2011] [error] [client]   * cron_check_for_updates() at /var/www/mahara/lib/cron.php:152

Has anybody an idea what to do?

Thank you for help,

anonymous profile picture
Account deleted
Posts: 808

07 August 2011, 17:35

It's nothing to worry about.  It's in the cron_check_for_updates function in lib/mahara.php.

Mahara is trying to scrape the launchpad downloads page to see if there's a new version of Mahara available, and the only point of that is to display a message in the admin section to encourage the admin to upgrade.

It looks like the function was made more robust/less noisy in 1.4, so if it bothers you, you could upgrade to 1.4, replace that function with the 1.4 version, or even just delete cron_check_for_updates from your cron table (to make it stop running).

anonymous profile picture
Account deleted
Posts: 39

09 August 2011, 2:54

Hello Richard,

thank you for your answer. You were also right.;-)

I followed your advice and deleted the cron_check_for_updates from the cron table to make it stop running and now: there are no error-messages any more. ;-)

thanxs & greetings,


3 results