I am running 7.0.4 and everything was running fine but the following cron job just stopped working acouple of days ago
When i checked the folder I found an error log which stated
[13-Dec-2010 19:34:39] PHP Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 30303032 bytes) in /home/idateuco/public_html/inc/utils.inc.php on line 247
Does anyone have any ideas how to fix this or what caused the issue in the first place?
|
You need to increase your memory_limit to a higher amount. Dolphin's minimum requirements state you need at least 128M set, but most people have theirs set to 256M. BoonEx Certified Host: Zarconia.net - Fully Supported Shared and Dedicated for Dolphin |
Thanks Magnussoft but could you expand on your reply, I actually have no idea what that means |
|
For me - could someone please say where to find this? C-Panel? Admin? Server? Thanks |
For me - could someone please say where to find this? C-Panel? Admin? Server? Thanks
You may be able to change your PHP configuration from your hosting account's control panel, or from a local php.ini file. If not, you'll have to contact your hosting provider.
BoonEx Certified Host: Zarconia.net - Fully Supported Shared and Dedicated for Dolphin |
Still didnt fix the issue as I still get the error message
Unable to connect. Please try again later.
It was working fine and then just stopped
|
Still didnt fix the issue as I still get the error message
Unable to connect. Please try again later.
It was working fine and then just stopped
Where are you receiving this error?
BoonEx Certified Host: Zarconia.net - Fully Supported Shared and Dedicated for Dolphin |
I would like to know as well since I have never heard of a cron job giving an error of 'Unable to connect. Please try again later..' Nothing to see here |
The issue is being highlighted in the cron email that is generated, its nice to know I am unique with an issue that you havent seen
Screen shot attached
|
Ok.. Take a look at my post and try changing your Cron Command to one of these listed:
http://www.boonex.com/trac/dolphin/wiki/TutorialCronJobSetup
Nothing to see here |
For the PHP Fatal error: Allowed memory size of 100663296 bytes exhausted part you can try this:
If your host is apache handler add this to your main .htaccess file (yoursite.com/.htaccess)
php_value memory_limit 128M
If your host is cgi/fast cgi/etc add to php.ini or create a php.ini file with the following:
memory_limit = 128M
upload php.ini to:
yoursite.com/php.ini
Also other areas can be helpful depending on your setup/host. Add the same php.ini file to these other locations:
yoursite.com/administration/php.ini yoursite.com/modules/php.ini
Try those location and see if it helps. You can also add php.ini file to each individual module folder/directory if necessary, flash folder, and more.
Certain setups you need php.ini added to additional folders/directories besides the main dolphin directory.
You can also push the 128M to 256M in the above examples, but most shared hosts don't like you to go to high. Start with 128M in the above locations and see first.
To determine if your host has apache handler or cgi, login to your d7 administration. Go to Tools->Host Tools->Php info
Find near the top "Server API"
If it says apache handler use the .htaccess example.
If it says cgi use php.ini example.
For the unable to connect try again later part, not sure right off hand. Could be related to the above memory issue since this seems to have come about from it. Could be something new or unrelated too. DialMe.com - Your One and Only Source For Boonex Dolphin Tutorials and Resources |
ok have tried various configs on cron job and ended up specifying php location but now have a different error message
Cron /usr/bin/php -c /home/sitedir/public_html/php.ini -q /home/sitedir/public_html/periodic/cron.php From: Cron Daemon Add to Contacts To:
--------------------------------------------------------------------------------
Site error: the file /home/sitedir/public_html/inc/classes/BxDolPageViewAdmin.php requires the ionCube PHP Loader ioncube_loader_lin_5.2.so to be installed by the site administrator.
I just heard back from the host and ioncube is installed and running
Next idea?
|
I have nearly the same problem. Installed Dolphin on a test domain and moved it to the productive site a bit later (on same server). I changed the lines in the header.inc.php and the whole website is working fine, the cronjob mostly. I get every five minutes a message reading "Unable to connect. Please try again later."
I've added an echo to the cron.php, and it was sent to me every minute, so the cronjob is working fine. But seems the cron.php (or the jobs it is calling every 5 mins) is having a problem (or needs adjustment in code also).
Can someone help or point me to the direction where to look at?
|
When you moved your site to the 'production' folder, did you change the Cron Job command also?
Example: (last part of the cron job statement)
/home/sitedir/public_html/test_site/periodic/cron.php
to
/home/sitedir/public_html/real_site/periodic/cron.php
Nothing to see here |
yes I did, thats when I started to receive these "Unable to connect" emails... so seems it was working fine on the test site and since the move (or better change of domain) it fails. I am still getting them every 5 mins. :( |
Someone know what is execute every 5 minutes?
As said, I get the mails every 5 minutes only, but the cronjob is called every minute. So there must be something in the cron.php or any included script that is called every 5 minutes only returning a "Unable to connect" (btw I checked for the string, it is not in a file, so it must be a system process returning it)
NOTE: The same cronjob on the same machine but with the test path where it was installed originally, works without any flaws!
|
Most of the hosting companies don't allow to run cronjobs every minute. Mine doesn't, because it's overloading the server.
Next time don't forget to clear the URL in your browser when you publish a screenshot :-)
|
@annabel
guess you are referring to parra541...
PS: no shared server, a dedicated quad core without problems to run the cron job.
|
I think you have cronjobs running from commands that have not been deleted in the cron file on the server end, not within cpanel. but via shell |