Have I read the related troubleshooter articles above before posting (which pages?)? Automatic Backup Documentation, Native Cron Script, FAQs.
Have I searched the tickets before posting? Yes, tons of them. Seems like I get to be abnormal. Though, I do enjoy reading your tickets.
Have I read the documentation before posting (which pages?)? Yes, 4 times. Automatic Backup Documentation. I also did a google search and couldn't find anything either. :(
Joomla! version: 2.5.14
PHP version: 5.3.27
MySQL version: 5.5.33
Host: Bluehost
Akeeba Backup version: Professional 3.7.10
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it. - You got it!
Description of my issue:
My CRON job for automatic backups emails the client with an email stating:
Status: 500 Internal Server Error
Content-type: text/html
The last command line backup it took was 7/28/13. I ran a backup manually before updating to 2.5.14 on 8/1. Since then, no command line backups.
Yesterday, I contacted the host and did get a cron job set for "every 2 minutes" to run successfully. Set it to once a day to test and got the same error listed in an email above.
Today, I tried another one for every 5 minutes, got it to run. Set it for an hour, didn't run. All that didn't run the client got an email like the above for.
I now have a cron set for every 5 minutes and none are going and my client will probably want to kill me with his email box being inundated with Cron Daemon messages. They are nice people so I don't think they will actually kill me.
Anyways, log for command line backups attached. I'm happy to do anything you say. My mind is boggled as to why an every 2 minute cron job would work and an every 5 minute won't (or one hour, or one day, or one week).
So, I tried reading everything before opening a ticket. Nothing major has changed except the security update on the 1st. And then also the host had a major outage on the 2nd too. But I'm assured that had to do with router firmware and not the server itself and that my path is good.
I'll shut up now since I am rambling. Sorry.
jenn :)