Support

As the title says, on this one site the CRON job never starts, and the output of the job is this stack trace :

********** ERROR! **********

Failed to start the session because headers have already been sent by "" at line 0.

Technical information:

Code: 0
File: /home/mysite/public_html/libraries/joomla/session/handler/native.php
Line: 256

Stack Trace:

#0 /home/mysite/public_html/libraries/joomla/session/handler/native.php(50): JSessionHandlerNative->doSessionStart()
#1 /home/mysite/public_html/libraries/joomla/session/handler/joomla.php(82): JSessionHandlerNative->start()
#2 /home/mysite/public_html/libraries/joomla/session/session.php(648): JSessionHandlerJoomla->start()
#3 /home/mysite/public_html/libraries/joomla/session/session.php(608): JSession->_start()
#4 /home/mysite/public_html/administrator/components/com_akeeba/Master/Cli/Base.php(321): JSession->start()
#5 /home/mysite/public_html/administrator/components/com_akeeba/Master/Cli/Base.php(351): AkeebaCliBase->__construct()
#6 /home/mysite/public_html/cli/akeeba-backup.php(428): AkeebaCliBase::getInstance('AkeebaBackupCLI')
#7 {main}

The last time the command-line backup worked was on April 22, prior to the J! 3.7 upgrade.

Obviously, since the job never started I have no log.

And yes, I fat-fingered the Akeeba version, its 5.3.4

This is one of the issues in Joomla! 3.7.0, it was identified late last week. For now, the only solution is to disable the plugin System - Page Cache.

Well ... hate to say this, this wasn't the issue in this case. The plugin was never enabled, and I have system caching disabled under the configuration settings :(

My apologies, I had the wrong bug. For this one, please install the latest Developer's Release, available here: https://www.akeebabackup.com/download/developer-releases/akeebapro.html.

Please let us know if this fixes the problem. We have one positive report so far, but we are still looking for confirmation that this fixes the issue.

When you have a Developer's Release installed, Joomla! will always want to install the older, stable version. You will need to ignore the update notices until you see a version higher than 5.3.4.

Dale,

that seems to have fixed this issue. I installed, then reset the CRON to run, and the backup was performed with no errors. The ticket can be closed.

Thanks,

Neil

Thanks for the feedback Neil. I expect this fix to be in the next stable release of Akeeba Backup.