Support

Akeeba Backup for Joomla!

#36785 authz core error AH01630 on backup cron job

Posted in ‘Akeeba Backup for Joomla!’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

gjzunic@gmail.com

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!


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: see attached screenshot. Backup runs fine when I run it from the online Joomla component. Fails on the attached directory checks. Note that site is hosted on Hostgator.

tampe125
Akeeba Staff

Hello,

those checks are performed by Akeeba Backup to be sure your backups are not publicly available. So they are expected, if we're not getting an error, Akeeba Backup will complain very hard and prevent you to take a backup (since anyone could download it from the web and steal all your website data).

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

gjzunic@gmail.com

Hello - backups run via cron job are failing. See attached log. These backsups process correctly including sending files to remote cloud destination when run from the website. Is it timing out maybe in batch?

Attachments

Akeeba_Backup_Debug_Log.zip

tampe125
Akeeba Staff

Yes, definitively.

Your backups fail because your host is imposing a maximum CPU usage time limit. Please note that CPU usage is different than wall clock time, hence the small variability of a few seconds you may observe in different backups' log files from the start of the backup until the point it abruptly stops.

You will need to contact your host and let them know they have to make a configuration change in their server to let you run your backups. You may use the following text, replacing XYZ with the time it takes to run a backup from the backend plus about 10%. You can find out the time it takes to run a backup in the backend of your site, Akeeba Backup, Manage Backups. If you have multiple backup profiles use the time from the longest-running profile.

Here is the text to use:

I am using CRON jobs to take a backup of my site. I have observed that my CRON job stops executing at around REPLACE THIS BASED ON WHAT YOU SEE IN THE LOG FILE seconds. This is not enough time to complete a backup of my site. This means that you have set up a CPU usage limit either with ulimit or the /etc/security/limits.conf file on your server.

Please make the current CPU limit for my user into a soft lift and set up my CRON jobs so they have a CPU limit of XYZ. This would allow my backups to run without affecting the sensible time limits you have set up for PHP script running over the web.

If your host refuses to make changes you can still automate your backups, either using a third party over-the-web CRON job service which respects redirections (e.g. WebCRON.org) or a third party service which is compatible with Akeeba Backup such as myJoomla.com, BackupMonkey.io or Watchful.li. The latter kind of services also offer additional features such as security auditing, site monitoring, management of core Joomla and extension updates across multiple sites, even backup testing automation in some cases.

The downside of third party services is that they cost money. You can alternatively have an always on-line computer (even a cheap Raspberry Pi would do!) run backups remotely using CRON jobs, either using the Legacy Frontend Backup URL or the modern Akeeba Backup JSON API. In the latter case you'd need to set up Akeeba Remote CLI on the always on-line computer. The always on-line computer can run any of the three major Operating Systems: Windows, macOS or Linux. 

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

gjzunic@gmail.com

Thank you for this very thorough response. I will investigate these options. I will close this ticket.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.