Error Code 3

[MichelleParticipant]

I keep getting an error when trying to just backup the database. When I try to do the full backup to remote storage it uses all of my resources on Godaddy. Is there something that I can do help this situation? This is the latest error log:

0000.000 (0) Opened log file at time: Wed, 07 Mar 2018 21:19:33 +0000 on https://magicalsoulutions.com
0000.007 (0) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.14.4 WP: 4.9.4 PHP: 7.0.22 (cgi-fcgi, Linux a2plvcpnl23312.prod.iad2.secureserver.net 2.6.32-673.26.1.lve1.4.30.el6.x86_64 #1 SMP Wed Jun 21 19:37:37 EDT 2017 x86_64) MySQL: 5.6.36 WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 64.6M | 6M) multisite: N openssl: OpenSSL 1.0.2k-fips 26 Jan 2017 mcrypt: Y LANG: ZipArchive::addFile: N
0000.152 (0) Free space on disk containing Updraft’s temporary directory: 39925.4 MB / Free disk space in account: 39977.3 MB (2.4 % used)
0000.159 (0) Tasks: Backup files: 0 (schedule: monthly) Backup DB: 1 (schedule: weekly)
0000.193 (0) Requesting semaphore lock (d) (apparently not via scheduler)
0000.205 (0) Semaphore (d, wp_options) was stuck, set lock time to 2018-03-07 21:19:33
0000.214 (0) Semaphore (d, wp_options) reset to 1
0000.227 (0) Set semaphore last lock (d) time to 2018-03-07 21:19:33
0000.228 (0) Semaphore lock (d) complete
0000.243 (0) Backup run: resumption=0, nonce=42e96bb196d0, begun at=1520457573 (0s ago), job type=backup
0000.251 (0) Scheduling a resumption (1) after 300 seconds (1520457873) in case this run gets aborted
0000.271 (0) This backup run is not intended for files – skipping
0000.275 (0) Beginning creation of database dump (WordPress DB)
0000.282 (0) Testing: /usr/bin/mysqldump
0000.365 (0) Output: /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;\n/*!40103 SET TIME_ZONE=’+00:00′ */;\n/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;\n/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;\n/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO’ */;\n/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;\nDROP TABLE IF EXISTS wp_options;\n/*!40101 SET @saved_cs_client = @@character_set_client */;\n/*!40101 SET character_set_client = utf8 */;\nCRE (truncated – 1192 bytes total)
0000.368 (0) Working binary mysqldump found: /usr/bin/mysqldump
0000.382 (0) Table wp_options: Total expected rows (approximate): 1745
0308.702 (1) Opened log file at time: Wed, 07 Mar 2018 21:24:42 +0000 on https://magicalsoulutions.com
0308.706 (1) UpdraftPlus WordPress backup plugin (https://updraftplus.com): 1.14.4 WP: 4.9.4 PHP: 7.0.22 (cgi-fcgi, Linux a2plvcpnl23312.prod.iad2.secureserver.net 2.6.32-673.26.1.lve1.4.30.el6.x86_64 #1 SMP Wed Jun 21 19:37:37 EDT 2017 x86_64) MySQL: 5.6.36 WPLANG: en_US Server: Apache safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 56.5M | 2M) multisite: N openssl: OpenSSL 1.0.2k-fips 26 Jan 2017 mcrypt: Y LANG: ZipArchive::addFile: N
0308.988 (1) Free space on disk containing Updraft’s temporary directory: 39895.5 MB / Free disk space in account: 39947.8 MB (2.5 % used)
0309.011 (1) Backup run: resumption=1, nonce=42e96bb196d0, begun at=1520457573 (309s ago), job type=backup
0309.017 (1) Scheduling a resumption (2) after 300 seconds (1520458182) in case this run gets aborted
0309.032 (1) This backup run is not intended for files – skipping
0309.037 (1) Resuming creation of database dump (WordPress DB)
0309.055 (1) Table wp_options: Total expected rows (approximate): 1745
0337.338 (1) Binary mysqldump: error (code: 3)

[Bryle CroduaModerator]

Hi Michelle,

It appears that the backup process is timed out or killed off while backing up the database component.

Please could you ask your hosts/server admin to investigate their PHP error logs. These logs should contain more information on the exact issue that is causing the backup process to halt.

Kind Regards,
Bryle

[MichelleParticipant]

This was the error: [07-Mar-2018 21:25:36 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 897024 bytes) in /home/mkmadm06/public_html/wp-includes/wp-db.php on line 1889.

I upped the memory to 512M on both the PHP hosting and on the wp-config file. I split the archives on the advanced settings to 50 MB. It is still timing out. What else can I do? GoDaddy wasn’t very helpful at all!

[Dee NutbourneModerator]

Hi,

Please could you send us a copy of the latest log file?

The contents will be too long to post here directly, but you can use an online service such as Dropbox or Pastebin, and post the link here.

Best Wishes,
David N

[MichelleParticipant]

This reply has been marked as private.

[Dee NutbourneModerator]

This reply has been marked as private.

[Author]

Posts