#1338 - The Cron Daemon is emitting errors at 1 minute intervals
-
By Lhasadreams
- Added
- 11 views
| Identifier | #1338 |
|---|---|
| Issue type | Major issue (breaks an entire feature) |
| Title | The Cron Daemon is emitting errors at 1 minute intervals |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | Hi,
We have not changed anything and at 20:13 tonight I have started to get Cron Daemon error messages. This is continuing at 1 minute intervals, ie each time cron_bridge.php runs. The error is a PHP error "Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534 @ http://vwgolfmk1.org.uk/data/cron_bridge.php" [07-Aug-2013 19:36:03 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in /home/vwgolfm/public_html/sources/mail.php on line 534 [07-Aug-2013 19:36:03 UTC] PHP Error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534 @ http://vwgolfmk1.org.uk/home/vwgolfm/public_html/data/cron_bridge.php Not sure what has happened, so would appreciate you guys taking a look. The site itself is up and running fine. Cheers Ade |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
<!DOCTYPE html><html lang="EN">
<head>
<title>Critical error</title>
<style type="text/css"><![CDATA[ .screen_title { text-decoration: underline; display: block; min-height: 42px; padding: 3px 0 0 0; }
a[target="_blank"], a[onclick$="window.open"] { padding-right: 0; }
]]></style>
</head>
<body><div class="global_middle"><h1 class="screen_title">Critical error – bailing out</h1>
<div class="red_alert" role="error">This is an error that has been elevated to critical error status because it occurred during the primary error mechanism reporting system itself (possibly due to it occuring within the standard output framework). It may be masking a secondary error that occurred before this, but was never output - if so, it is likely strongly related to this one, thus fixing this will fix the other.</div>
<div style="padding-left: 50px">PHP ERROR [1] Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534 (version: 9.0.5, PHP version: 5.3.20, URL: /home/vwgolfm/public_html/data/cron_bridge.php)<div class="box guid_{_GUID}"><div class="box_inner"><h2>Stack trace…</h2>
File -> '/home/vwgolfm/public_html/sources/failure.php'
Line -> 792
Function -> 'die_html_trace'
Args -> array (
0 => 'PHP ERROR [1] Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534 (version: 9.0.5, PHP version: 5.3.20, URL: /home/vwgolfm/public_html/data/cron_bridge.php)',
)
File -> '/home/vwgolfm/public_html/sources/global2.php'
Line -> 1011
Function -> '_fatal_exit'
Args -> array (
0 => 'PHP ERROR [1] Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534',
)
File -> '/home/vwgolfm/public_html/sources/failure.php'
Line -> 224
Function -> 'fatal_exit'
Args -> array (
0 => 'PHP ERROR [1] Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes) in sources/mail.php on line 534',
)
File -> '/home/vwgolfm/public_html/sources/global2.php'
Line -> 874
Function -> '_Composr_error_handler'
Args -> array (
0 => 'error',
1 => 1,
2 => 'Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes)',
3 => 'sources/mail.php',
4 => 534,
)
File -> '/home/vwgolfm/public_html/sources/global2.php'
Line -> 810
Function -> 'Composr_error_handler'
Args -> array (
0 => 1,
1 => 'Allowed memory size of 67108864 bytes exhausted (tried to allocate 17131744 bytes)',
2 => '/home/vwgolfm/public_html/sources/mail.php',
3 => 534,
)
Function -> 'catch_fatal_errors'
Args -> array (
)
</div></div></div>
Details here are intended only for the website/system-administrator, not for regular website users.
» <strong>If you are a regular website user, please let the website staff deal with this problem.</strong>
<p class="associated_details">Depending on the error, and only if the website installation finished, you may need to <a href="#" onclick="if (!window.confirm('Are you staff on this site?')) return false; this.href='http://vwgolfmk1.org.uk/config_editor.php';">edit the installation options</a> (the <kbd>info.php</kbd> file).
<p class="associated_details">ocProducts maintains full documentation for all procedures and tools. These may be found on the <a href="http://compo.sr">Composr website</a>. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you.
<hr />
<p style="font-size: 0.8em"><a href="http://compo.sr/">Composr</a> is a <abbr title="Content Management System">CMS</abbr> for building websites, developed by ocProducts.
</div></body>
Any idea why that might be ?
I have set it to every 10 minutes.
However I have noticed (an unrelated issue) CRON is slow for you even when immediately refreshing, it should be really fast in such a situation. So I am studying this.