• Resolved adriansquared

    (@adriansquared)


    Hi there,

    This error only occurs when database backup is run, files backup and xml backup are working properly. The plugin has been working perfectly until yesterday and the site hadn’t been touched before the problem occurred.

    I set the memory limit to 256M, but based on the error log, it seems like allocating more than 1GB. The version of BackWPup I am using is 3.4.4, I also tried 3.4.1 and it returned the same result. Also, running this task caused my CPU usage to 100%, even after the task is aborted, I called my hosting company and they said the task was still running.

    I am running this site on a shared hosting and I have 5 other sites running on this shared hosting as well, but there is no problem running database backup on another site.

    What could be the issue here?

    Thanks in advance.

    Please find the following error log.

    [INFO] BackWPup 3.4.1; A project of Inpsyde GmbH
    [INFO] WordPress 4.9.1 on
    [INFO] Log Level: Debug
    [INFO] BackWPup job: Testing Backup to Folder; DBDUMP
    [INFO] Runs with user: (0)
    [INFO] BackWPup no automatic job start configured
    [INFO] BackWPup job started manually
    [INFO] PHP ver.: 7.0.27 (64bit); litespeed; Linux
    [INFO] Maximum PHP script execution time is 300 seconds
    [INFO] Script restart time is configured to 20 seconds
    [INFO] MySQL ver.: 10.2.12-MariaDB
    [INFO] Web Server: LiteSpeed
    [INFO] curl ver.: 7.54.0; OpenSSL/1.0.2k
    [INFO] Temp folder is: /home/theparad/public_html/assets/uploads/backwpup-b5e2e6-temp/
    [INFO] Logfile is: /home/theparad/public_html/assets/uploads/backwpup-b5e2e6-logs/backwpup_log_b5e2e6_2018-01-12_10-01-36.html
    [INFO] Backup file is: /home/theparad/public_html/assets/uploads/backwpup-test/backwpup_b5e2e602_2018-01-12_10-01-36.zip
    [12-Jan-2018 10:01:36] 1. Try to backup database …
    [12-Jan-2018 10:01:36] Connected to database theparad_parade on localhost
    [12-Jan-2018 10:01:36] Backup database table “tswp_commentmeta” with “~0” records
    [12-Jan-2018 00:01:36 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1634037384 bytes) in /home/theparad/public_html/assets/plugins/backwpup/inc/class-mysqldump.php on line 506 [12-Jan-2018 10:01:36] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1634037384 bytes)
    [12-Jan-2018 10:01:36] Restart after 1 seconds.
    [12-Jan-2018 10:01:38] 2. Try to backup database …
    [12-Jan-2018 10:01:38] Connected to database theparad_parade on localhost
    [12-Jan-2018 00:01:38 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1279410544 bytes) in /home/theparad/public_html/assets/plugins/backwpup/inc/class-mysqldump.php on line 506 [12-Jan-2018 10:01:38] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1279410544 bytes)
    [12-Jan-2018 10:01:38] Restart after 1 seconds.
    [12-Jan-2018 10:01:41] 3. Try to backup database …
    [12-Jan-2018 10:01:41] Connected to database theparad_parade on localhost
    [12-Jan-2018 00:01:41 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1279410544 bytes) in /home/theparad/public_html/assets/plugins/backwpup/inc/class-mysqldump.php on line 506 [12-Jan-2018 10:01:41] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1279410544 bytes)
    [12-Jan-2018 10:01:41] Restart after 1 seconds.
    [12-Jan-2018 10:01:43] ERROR: Step aborted: too many attempts!
    [12-Jan-2018 10:01:43] 1. Trying to generate a manifest file …
    [12-Jan-2018 10:01:43] Added manifest.json file with 4.35 KB to backup file list.
    [12-Jan-2018 10:01:44] 1. Trying to create backup archive …
    [12-Jan-2018 10:01:44] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [12-Jan-2018 10:01:44] Adding Extra files to Archive
    [12-Jan-2018 10:01:44] Backup archive created.
    [12-Jan-2018 10:01:44] Archive size is 1.76 KB.
    [12-Jan-2018 10:01:44] 2 Files with 4.57 KB in Archive.
    [12-Jan-2018 10:01:45] ERROR: Job has ended with errors in 9 seconds. You must resolve the errors for correct execution.

Viewing 15 replies - 1 through 15 (of 41 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hi @adriansquared
    Please try to set reduce server load to maximum by going to BackWPUp -> Settings -> Jobs -> Reduce server load, set to maximum.
    After that, try again.
    Is that helps?

    Thread Starter adriansquared

    (@adriansquared)

    Hi @duongcuong96

    I have done so but it didn’t work, it should not use 1GB memory anyway in my opinion.

    Because the problem only occurs when backing up database file, so I checked the database version on this problematic server, it is 10.2.12-MariaDB, on my other websites (same hosting provider) where the plugin runs perfectly, the database version is mysql 5.6.38. That is the only thing different between problematic websites and working ones.

    Is there any known issues between this plugin and different versions of mysql database?

    Thanks.

    • This reply was modified 7 years, 1 month ago by adriansquared. Reason: grammar
    Plugin Support happyAnt

    (@duongcuong96)

    @adriansquared,
    This may be a bug. So I will try to reproduce this and talk to our developers and back to you as soon as I can.
    Thank you for providing your config details ??

    Thread Starter adriansquared

    (@adriansquared)

    Hi @duongcuong96, no worries! Hopefully that I could hear from you soon ??

    I am getting the exact same error with all database backups. I’ve tried the same suggestion as above and the error continues. Is there any update on this error?

    Thread Starter adriansquared

    (@adriansquared)

    Hey @csmaderer, what’s your database version? I haven’t got any updates from the plugin author yet, so probably you need to find another plugin to backup the database for now.

    Sorry How to I check and tell you the DB version? This is the log with the error….

    [INFO] BackWPup 3.4.4; A project of Inpsyde GmbH
    [INFO] WordPress 4.9.2 on https://inspiredstewardship.com/wp/
    [INFO] Log Level: Normal
    [INFO] BackWPup job: Daily Database
    [INFO] Logfile is: backwpup_log_c15fc0_2018-01-28_06-59-39.html
    [INFO] Backup file is: 2018-01-28_06-59-39_W3AV7QF602.tar.bz2
    [28-Jan-2018 06:59:39] 1. Try to backup database …
    [28-Jan-2018 06:59:39] Connected to database ua827298_wp643 on localhost
    [28-Jan-2018 06:59:39] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1701601920 bytes)
    [28-Jan-2018 06:59:40] 2. Try to backup database …
    [28-Jan-2018 06:59:40] Connected to database ua827298_wp643 on localhost
    [28-Jan-2018 06:59:40] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1852140936 bytes)
    [28-Jan-2018 06:59:40] 3. Try to backup database …
    [28-Jan-2018 06:59:40] Connected to database ua827298_wp643 on localhost
    [28-Jan-2018 06:59:40] ERROR: Allowed memory size of 268435456 bytes exhausted (tried to allocate 761624200 bytes)
    [28-Jan-2018 06:59:41] ERROR: Step aborted: too many attempts!
    [28-Jan-2018 06:59:41] 1. Trying to generate a manifest file …
    [28-Jan-2018 06:59:41] Added manifest.json file with 9.35 KB to backup file list.
    [28-Jan-2018 06:59:41] 1. Trying to create backup archive …
    [28-Jan-2018 06:59:41] Compressing files as TarBz2. Please be patient, this may take a moment.
    [28-Jan-2018 06:59:41] Backup archive created.
    [28-Jan-2018 06:59:41] Archive size is 2.68 KB.
    [28-Jan-2018 06:59:41] 2 Files with 9.57 KB in Archive.
    [28-Jan-2018 06:59:41] 1. Try to send backup file to Dropbox …
    [28-Jan-2018 06:59:41] Authenticated with Dropbox of user: Scott Maderer
    [28-Jan-2018 06:59:41] Uploading to Dropbox …
    [28-Jan-2018 06:59:43] Backup transferred to /Inspired-Stewardship/2018-01-28_06-59-39_W3AV7QF602.tar.bz2
    [28-Jan-2018 06:59:43] ERROR: Job has ended with errors in 4 seconds. You must resolve the errors for correct execution.

    Thread Starter adriansquared

    (@adriansquared)

    Hey @csmaderer.

    A kind reminder, please edit your post to delete the website information, like your website URL and some other information, otherwise you are at risk of getting hacked.

    The easiest way to know your database is to check BackWPUp -> Setting -> Information from your WordPress backend.

    Cheers

    Well, unfortunately, I can’t edit it after an hour. However to answer your question.
    I assume you mean the BackWPUp version 3.4.4. Or do you mean the MYSQL version? It’s 10.2.12-MariaDB.

    Scott

    Thread Starter adriansquared

    (@adriansquared)

    @csmaderer Yep, I mean the MySQL version and my MySQL version is the same as yours as you can see from my previous posts. In this case, I think that’s a bug in the plugin for now.

    I recommend you to find an alternative for backing up the database, that’s my temporary solution.

    same issue here
    DB: 10.2.12-MariaDB

    tried to allocate: 1701601920 bytes

    brand new install so nothing in the database yet other than default install data, so no way should need that amount of memory

    • This reply was modified 7 years, 1 month ago by njwp.
    Plugin Support happyAnt

    (@duongcuong96)

    @here,
    This might be a bug, I will try to reproduce this and then report to our developers about this.
    Please be patience. Thanks ??

    Thread Starter adriansquared

    (@adriansquared)

    Hey @duongcuong96,

    Thanks for creating the plugin, but it’s been two and half week since I reported this issue, hopefully it can be solved soon.

    Cheers

    Plugin Support happyAnt

    (@duongcuong96)

    @here,
    Currently, we are releasing new release so this problem will be on our roadmap and can be fixed soon.
    Please be patient!
    Thank you!

    Thread Starter adriansquared

    (@adriansquared)

    Hi @duongcuong96,

    Would you mind giving some information about when the next version of BackWPUp will be released?

    Thank you.

Viewing 15 replies - 1 through 15 (of 41 total)
  • The topic ‘Database backup failed because memory is exhausted’ is closed to new replies.