• Resolved Tom

    (@tomybyte)


    The following error reports are send every day @ 3:00 am since the autoupdate to BackWPup 5.3.0.
    The error report created by BackWPup is sent to an email adress that was used by a former Backend-Admin which is no longer valid (this user is deleted completely one day ago). Nevertheless he received today @ 3:00 am the third error report anyway.

    Therefore it is concerning a German website and the error report is in that language so I translated the lines to English [specific data has been replaced]:

    [INFO] BackWPup 5.3.0; A project by WP Media
    [INFO] WordPress 6.8.2 on [client-domain]
    [INFO] Log level: Normal (translated)
    [INFO] BackWPup task: [database_backup_task_name]
    [INFO] Logfile is: backwpup_log_[name].html
    [INFO] Backup file is: [name]-plugin_[id]_DBDUMP.tar
    [17-Jul-2025 03:00:05] 1st attempt to back up the database …
    [17-Jul-2025 03:00:06] Connected to database [db_name] on [db-server]
    [17-Jul-2025 03:00:10] Added database backup “[db_name].sql” with 340.42 MB to the backup file list
    [17-Jul-2025 03:00:10] Database backup finished!
    [17-Jul-2025 03:00:11] 1st attempt to generate a manifest file …
    [17-Jul-2025 03:00:11] The manifest.json file with 3.63 kB was added to the backup file list.
    [17-Jul-2025 03:00:11] 1st attempt to create backup archive …
    [17-Jul-2025 03:00:11] Compress files as tar. Please be patient for a moment.
    [17-Jul-2025 03:00:12] Backup has been created.
    [17-Jul-2025 03:00:12] Archive size is 340.43 MB.
    [17-Jul-2025 03:00:12] 3 files with 340.43 MB in the archive.
    [17-Jul-2025 03:00:12] 1st attempt to send backup as email …
    [17-Jul-2025 03:00:12] ERROR: The backup file is too large to be sent by e-mail!
    [17-Jul-2025 03:00:12] Deleted an old log file
    [17-Jul-2025 03:00:12] ERROR: Job finished with errors in 7 seconds. To ensure correct execution, you must fix the errors.

    This backup with [database_backup_task_name] was never configured to send the database backup by e-mail, there is not this here used email adress as target configured.
    How can this error reports stopped?

    • This topic was modified 1 year, 3 months ago by Tom.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Saransh

    (@saranshwpm)

    Hi,

    Thank you for the detailed explanation and the translated log.

    From what you described, this might be happening if there is still a legacy job present that was previously configured to send backups by email, even if it is not visible in your current settings.

    Please check under BackWPUp > Advanced Settings > Jobs > Access to Legacy Jobs and see if any old job is still listed there. If you find one, try deleting it and check if that stops the email errors.

    Let us know how it goes or if you need help checking this.

    Thread Starter Tom

    (@tomybyte)

    There is a legacy task, but it has been and is currently inactive! It was hardly ever used, maybe in 2023 when a developed plugin was tested. There have been no error messages since then. Only after BackWPup 5.3.0 Update, it seems this causes some troubles and I assume it has not been sufficiently tested! The task is now deleted. I hope that this will make the error messages disappear.

    Thread Starter Tom

    (@tomybyte)

    After deleting the legacy database backup task the error reports via email are still sent. I discovered that the current task with the same name in the section ‘Next Scheduled Backups’ generates this error message when this task is started manually. I wonder where to change the setting for the target and the target email adress couldn’t find any entry. As storage targets are only given:
    Website Server, Dropbox, FTP, Microsoft Azure, Amazon S3, Sugar Sync and Rackspace Cloud, but not sending as email!
    Version 5.3 of BackWPup is annoying and causing headache!!

    Thread Starter Tom

    (@tomybyte)

    It is even worse, as I have now discovered, all archives of the last backups, including those before the update to 5.3, are damaged and unreadable or the extracted SQL files are incomplete. In this form, BackWPup is simply unusable. I am glad that I have now discovered this.

    @tomybyte When we analyzed the first issues after the 5.x release, it became clear that error checking and parameter validation was not sufficient or not exisiting almost everywhere in the code base. Such problems as described in this thread would never happen if proper checks would be in place. Code quality still needs to improve a lot before the plugin will be usable again in production.

    Plugin Support Saransh

    (@saranshwpm)

    Hi @tomybyte,

    Thank you for following up and sharing these details.

    We’ve tried checking this on our end but couldn’t replicate the issue. Could you please reach out to us directly so we can investigate further with your specific setup?

    We’ll be glad to help sort this out.

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

The topic ‘BackWPup Error Report since auto update to 5.3.0’ is closed to new replies.