Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes until my eyes blurred
Have I read the documentation before posting (which pages?)? Yes also until it dazzled :)
Joomla! version: 2.5.14
PHP version: THAT's the whole problem .... (godaddy)
MySQL version: (unknown)
Host: (optional, but it helps us help you)
Akeeba Backup version: 3.8.2 pro

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.

Description of my issue:

Nicholas,
I am afraid i made a huge mistake by getting a godaddy hosting account ..... I have read a lot about what you have to say about them ,,,, (uucchchhh) The specific problem I am having with them is that my cron-job gets triggered allright but throws me back the message on an outdated version of PHP. As per your instructions I contacted support with the following message :

i have a joomla site installed which uses akeebabackup for backups. the component is able to use cron jobs to get triggered regularly. however it appears that the cron job runs on a server with an outdated PHP 5.2.17 while it needs more up to date and more secure version 5.3.1>

Can you provide me with the path to PHP 5.3.1. CLI binary?

on which i got the following reply:

Thank you for contacting GoDaddy Support.

In regard to the cron server's PHP configuration for the relativerotationgraphs.com hosting account, the cron server is associated with the version of PHP in use for the hosting account. Currently, we have confirmed the hosting account is configured to use PHP 5.3 and, as such, the associated cron would also use PHP 5.3.

At this time, we have successfully tested the hosting account's cron configuration and a cron_test.txt file has been left within the hosting account's root directory for you to review. Separately, we have uploaded a phpinfo.php to the hosting account root directory verify PHP 5.3.24 is in use and have created a custom cron with the Hosting Control Center Cron Manager to have the results of the phpinfo.php file sent once at 5 AM, Arizona Standard Time, on 24 October 2013. The email address applied within the Cron Manager is the corresponding email address from which we received your email.

Please let us know if we may assist you further in the interim.

Regards,

Suzi D.

Professional Hosting Services

From reading your material I take it they are missing point 2 of your error-mail...??

There is also another component on my site that needs cron to run and is causing failures (easy-discuss) the guys there are trying to troubleshoot for 2 days already but to no avail...

Do you see/know of any fixes, workarounds or do i have to accept that the money i spent on go-daddy is simply a waste ad it is better for me to accept it as being flushed down the toilet and move to another hosting company ? I assume you will recommend me to siteground.com ?

regards, Julius


...

strange, on my dashboard it says that davide has responded to this thread but i see no message ?

thanks nick, that was the only thing i needed to hear ....
it's a shame but i have always learned that it is better to face your mistakes and correct them before it is too late .... even if it means flushing a bunch of €€, in my (stock-trading) world we call that "cut your losses"
I will start the switch this w.e. and hopefully I will then have a. faster site and b. running my akeeba backups unattended and c. solved my other cron problems as well ...
have a nice weekend !
Julius

Just as a FYI, before i am going to close this ticket, for everybody else who is running into the same trouble as i did recently.....

I started hosting my site with godaddy on 2nd October and almost right from the bat the security exceptions started flowing in... see attached admin tools graph.I have probably seen every possible attack or intrusion that AT tackles. Adding the worst offenders to the blacklist and denying them access to the site caused the line to go down again. thank you Akeeba ADMINTOOLS. I am fairly sure that without AT the site would have been hacked within a few hours of launching.

Once that was solved i needed to setup some cron jobs with godaddy, that was when the real fun started ...... the thread above speaks for itself with the ultimate answer from Nick Friday, 25 October 2013 15:47 UTC.

Around 16.00 UTC I opened my account with siteground.com just before i had to leave for an appointment. With my plan being to have my login and user details flowing into my mailbox while i was out and start transferring the site over the weekend..... About 20 minutes later I received a phone call which went to my voice mail... when i listened to the message later it was a customer rep from siteground.com introducing himself and offering his help with transferring the site or any other hosting or joomla related hosting issues if i needed it ..... wow ....is this really happening??!!!

The next day, once I had my details I entered all my dns records (my g-apps runs on the same domain). Then I created a new database, copied kickstart and my jpa file over via ftp and within 20 minutes the site was operational via ip-address (dns had not yet updated). No support needed thank you Akeeba BACKUP!

As I have a SSL certificate I needed support to install that for me. The reply to my ticket came 8 minutes after I sent it and within 30 minutes my SSL was operational. @Godaddy : This is how support should be done !!!!

And then the cron jobs... something godaddy was absolutely not able to fix... not only for my akeebabackup but also the cron that easydiscuss needs to send out its mails.... what a joy when you wake up in the morning and find that e-mail in your inbox saying : backup completed , check ! and the backup file safely stored in Amazon S3 storage without any interception from my site .... and all subscribers to discussions have received their updates, no more mails pending in queues etc etc ....

After 25 days with GoDaddy i was gone again and finally able to start focussing on delivering content to my site's subscribers instead of trouble shooting the back end ... and the site is FAAAAAAAAAAAAAAAST !!!!!

Kudos to Nick and his team and thank you for providing some fantastic tools and support to the Joomla community. I would not know what to do without them and just wanted to let you know that I am very happy to pay my annual fee for a DeLuxe subscription!!

Keep up the good work guys!
Happy to buy you a drink whenever you happen to be in Amsterdam :)

Julius