Error email even after succesful backup?

  • sarumbear

    (@sarumbear)


    10 years, 5 months ago

    Hi

    I receive a lot of error emails even though reading the log I see that on almost all cases there had been an error during operation but eventually the backup is done as expected. An example is below:

    Wouldn’t it be better email only on cases where the backup failed?

    Thank for listening and a happy 2016!

    —–
    [INFO] BackWPup version 3.1.4; A project of Inpsyde GmbH
    [INFO] WordPress version 4.2.5
    [INFO] Blog url: http://performance-pro.co.uk/
    [INFO] BackWPup job: Daily back-up; DBDUMP+FILE+WPPLUGIN
    [INFO] BackWPup cron: 0 3 * * *; Next: Sat, 2 Jan 2016 @ 03:00
    [INFO] BackWPup job started from wp-cron
    [INFO] PHP ver.: 5.3.29 (64bit); cgi-fcgi; Linux
    [INFO] Maximum PHP script execution time is 600 seconds
    [INFO] Script restart time is configured to 600 seconds
    [INFO] MySQL ver.: 5.5.46-cll
    [INFO] Web Server: Apache
    [INFO] curl ver.: 7.38.0; OpenSSL/1.0.1e
    [INFO] Temp folder is: /home/performa/public_html/wp-content/uploads/backwpup-6d307b-temp/
    [INFO] Logfile is: /home/performa/public_html/wp-content/uploads/backwpup-6d307b-logs/backwpup_log_6d307b_2016-01-01_03-00-05.html
    [INFO] Backup type is: archive
    [INFO] Backup file is: /home/performa/public_html/wp-content/uploads/backwpup-6d307b-temp/backwpup_6d307b_2016-01-01_03-00-05.zip
    [01-Jan-2016 03:00:05] 1. Try to backup database …
    [01-Jan-2016 03:00:06] Connected to database performa_pprat33 on localhost
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_andit_images” with “15” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_cntctfrm_field” with “13” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_commentmeta” with “0” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_comments” with “0” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_et_social_stats” with “125” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_links” with “0” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_options” with “277” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_postmeta” with “1182” records
    [01-Jan-2016 03:00:07] Backup database table “w7pr0_posts” with “1144” records
    [01-Jan-2016 03:00:11] Backup database table “w7pr0_term_relationships” with “62” records
    [01-Jan-2016 03:00:11] Backup database table “w7pr0_term_taxonomy” with “12” records
    [01-Jan-2016 03:00:11] Backup database table “w7pr0_terms” with “12” records
    [01-Jan-2016 03:00:11] Backup database table “w7pr0_usermeta” with “89” records
    [01-Jan-2016 03:00:11] Backup database table “w7pr0_users” with “3” records
    [01-Jan-2016 03:00:11] Added database dump “performa_pprat33.sql” with 6.08 MB to backup file list
    [01-Jan-2016 03:00:11] Database backup done!
    [01-Jan-2016 03:00:11] Restart will be executed now.
    [01-Jan-2016 03:00:13] 1. Trying to make a list of folders to back up …
    [01-Jan-2016 03:00:15] 237 folders to backup.
    [01-Jan-2016 03:00:15] 1. Trying to generate a file with installed plugin names …
    [01-Jan-2016 03:00:15] Added plugin list file “Performance-pro.pluginlist.2016-01-01.txt” with 1.91 kB to backup file list.
    [01-Jan-2016 03:00:15] 1. Trying to generate a manifest file …
    [01-Jan-2016 03:00:15] Added manifest.json file with 5.25 kB to backup file list.
    [01-Jan-2016 03:00:15] 1. Trying to create backup archive …
    [01-Jan-2016 03:00:15] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [01-Jan-2016 03:14:07] Restart after 835 seconds.
    [01-Jan-2016 03:26:43] Backup archive created.
    [01-Jan-2016 03:26:43] Archive size is 395.84 MB.
    [01-Jan-2016 03:26:43] 2684 Files with 430.93 MB in Archive.
    [01-Jan-2016 03:26:43] Restart will be executed now.
    [01-Jan-2016 03:26:46] 1. Try to send backup file to Dropbox …
    [01-Jan-2016 03:26:49] Authenticated with Dropbox of user Riz ([email protected])
    [01-Jan-2016 03:26:49] 192.62 GB available on your Dropbox
    [01-Jan-2016 03:26:49] Uploading to Dropbox …
    [01-Jan-2016 03:30:05] ERROR: Dropbox API: (6) Couldn’t resolve host ‘api-content.dropbox.com’
    [01-Jan-2016 03:30:05] Restart will be executed now.
    [01-Jan-2016 03:44:25] 2. Try to send backup file to Dropbox …
    [01-Jan-2016 03:44:26] Authenticated with Dropbox of user Riz ([email protected])
    [01-Jan-2016 03:44:26] 192.62 GB available on your Dropbox
    [01-Jan-2016 03:44:26] Uploading to Dropbox …
    [01-Jan-2016 03:54:30] Restart after 606 seconds.
    [01-Jan-2016 04:09:48] Restart after 624 seconds.
    [01-Jan-2016 04:20:58] Restart after 669 seconds.
    [01-Jan-2016 04:26:36] Backup transferred to https://api-content.dropbox.com/1/files/sandbox/Performance-pro/backwpup_6d307b_2016-01-01_03-00-05.zip
    [01-Jan-2016 04:26:39] One file deleted from Dropbox
    [01-Jan-2016 04:26:39] One old log deleted
    [01-Jan-2016 04:26:39] ERROR: Job has ended with errors in 5194 seconds. You must resolve the errors for correct execution.

    https://ww.wp.xz.cn/plugins/backwpup/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    10 years, 5 months ago

    The error is the ERROR: Dropbox API: (6) message!

    Thread Starter sarumbear

    (@sarumbear)

    10 years, 5 months ago

    I assume you have not read what I suggested.

    Wouldn’t it be better email only on cases where the backup failed?

    If the plugin has recovered from the error why sent an email? Or at least make it an option to send an email ONLY when the backup has failed.

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    10 years, 5 months ago

    Yes, it detects only error messages in the log and than sending E-Mails.
    It not checks that the error was resolved.

    Thread Starter sarumbear

    (@sarumbear)

    10 years, 5 months ago

    It seems we are not communicating well. I do understand what your system does. I’m making a suggestion to make it better.

    Will you agree that the only purpose of the email is to inform an admin that there is a problem with the site backups? Then when your code manages to make a succesfull backup why would you want to inform an admin? There had been errors during the process but your code has retried and at the end succeeded to create the backup. You don’t want to send an email then do you. Otherwise you would simply be emailing a debug log. What admin likes to receive debug logs when the system is working perfectly fine?

    We receive enough emails already. It will be cool if authors like you help us to reduce the email deluge.

    Thanks for lstening.

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    10 years, 5 months ago

    I’m understand you, we will keep this for later.

    Thread Starter sarumbear

    (@sarumbear)

    10 years, 5 months ago

    Thank you

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Error email even after succesful backup?’ is closed to new replies.