Akeeba Backup for Joomla!

Monday, 12 December 2022 02:13 CST

lucidfox

I set up Scheduled Tasks for backups on my client site, triggered by cron. The incremental backup profile works beautifully, but the full backup fails every time with "exit code 4".

In the back end, it appears it ran twice (see attached screenshots in next comment) and (both?) backups appear as successful despite the failure email. This is not always the case, sometimes they show as failed in the back end too but Alice finds no problems.

You can see the log file of the most recent backup that gave the exit code 4 here: https://www.icloud.com/iclouddrive/053HAlJrtA0gQ9A26hKfG18ow#Akeeba_Backup_Debug_Log

This happens on multiple sites.

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 10MiB, please upload it on your server and post a link to it.

Edited by lucidfox on 2022-12-12 02:22 CST

Monday, 12 December 2022 02:14 CST

lucidfox

HAHAHAHAHA I pressed enter when I meant to tab. I will edit to add actual information.

Monday, 12 December 2022 02:24 CST

lucidfox

Attachments here. Sorry. 🫠

Monday, 12 December 2022 09:35 CST

nicholas

I cannot reproduce this and there is also something odd about this.

Exist status 4 is an internal error in Joomla, not a problem with the task plugin (our code). You can see it's defined in Joomla itself https://github.com/joomla/joomla-cms/blob/f520c98c64efb538e70e918acffb60d07e4d6b1e/administrator/components/com_scheduler/src/Task/Status.php#L64

The only place where this error is thrown is again in Joomla itself: https://github.com/joomla/joomla-cms/blob/ce3d724d633473c4c514f7d20be46c9617165f59/administrator/components/com_scheduler/src/Task/Task.php#L270

At this point our task has successfully executed (part of a) backup and Joomla has resumed control. Joomla then tries to release all the "locked" tasks using an update query. If that query fails for any reason Joomla will NOT log the reason the query failed (making it impossible to debug the problem…) and return false from \Joomla\Component\Scheduler\Administrator\Task\Task::releaseLock which triggers the status 4 failure for the task even though the task had nothing to do with the problem.

This is ultimately a problem in \Joomla\Component\Scheduler\Administrator\Task\Task::releaseLock which should log the query failure reason in line 400, before returning false. Since it logs nothing I can't tell you why Joomla fails to release the lock on the tasks it has locked by itself. It could be a broken table, it could be a table schema in need of an update, it could be something else database related. Without a logged error my guess is as good as anyone else's.

Please ask Benjamin to add logging there so we can troubleshoot this kind of issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support