Support

Akeeba Backup for Joomla!

#19543 3.10.2 cron --quiet not respected

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
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

Latest post by heidi4web on Thursday, 13 March 2014 15:49 CDT

heidi4web
Description of my issue:

This is one of many sites we work on, and it appears that on the sites that have been updated to Akeeba Backup 3.10.2 (as opposed to 3.10.1) the "--quiet" option on the cron command is no longer being respected and the cron mailer is sending success as well as error emails.

The 3.10.1 sites are still only sending error and warning emails.


A Success email, used to be blocked by using the "--quiet" option:
-------------------------------------------
From: Cron Daemon
Date: Tue, Mar 11, 2014 at 2:00 AM
Subject: Cron /usr/bin/php5-cli /public_html/cli/akeeba-backup.php --profile=5 --quiet

-------------------------------------------


A more typical error message (from a different site):
-------------------------------------------
From: Cron Daemon
Date: Tue, Nov 19, 2013 at 2:05 AM
Subject: Cron /usr/bin/php5-cli /public_html/cli/akeeba-backup.php --profile=5 --quiet

Last Tick : 2013-11-19 01:05:08 GMT-0600 (CST)
Domain : finale
Step : Post-processing
Substep : site-20131119-015002.j12
Memory used : 11.68 Mb
Warnings : POTENTIAL PROBLEMS DETECTED; 3 warnings issued (see below).
AEUtilAmazons3::uploadMultipart(): [InternalError] We encountered an internal error. Please try again.
Failed to process file /public_html/administrator/components/com_akeeba/backup/site-20131119-015002.j12
Post-processing interrupted -- no more files will be transferred

-------------------------------------------

(the error email above is just for comparison).

Did the "--quiet" option change, or do you think this may be something with the host? Since the 3.10.2 sites are the only ones experiencing this, I thought it may be related to the upgrade.

Thank you!

nicholas
Akeeba Staff
Manager
The --quiet option only changes the way the CRON script outputs information. The emails are not sent by the CRON script, they are sent by the CRON daemon running on your site. If you do not wish to receive emails from your CRON you should append
1> /dev/null 2> /dev/null
to your CRON command line.

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!

heidi4web
Hi,

Thanks for the info: looks like I was misunderstanding the meaning of the "--quiet" option.

Still, it is interesting that before the 3.10.2 update we weren't receiving anything but error messages and now we get the blank success messages as well. Not sure if there is a question in that anymore, though. =)

nicholas
Akeeba Staff
Manager
Sorry, I just realised the context of your question and you are right. There was something changed, accidentally. There is a space in the beginning of the cli/akeeba-backup.php file which triggers the email when the backup is successful. We will remove that in the next version of Akeeba Backup.

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!

heidi4web
Not a problem. Thank you for the update! We'll look forward to it and cut back down on the email inbox a bit.

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!