Title: GaryCoon's Replies | WordPress.org --- # GaryCoon [ ](https://wordpress.org/support/users/garycoon/) * [Profile](https://wordpress.org/support/users/garycoon/) * [Topics Started](https://wordpress.org/support/users/garycoon/topics/) * [Replies Created](https://wordpress.org/support/users/garycoon/replies/) * [Reviews Written](https://wordpress.org/support/users/garycoon/reviews/) * [Topics Replied To](https://wordpress.org/support/users/garycoon/replied-to/) * [Engagements](https://wordpress.org/support/users/garycoon/engagements/) * [Favorites](https://wordpress.org/support/users/garycoon/favorites/) Search replies: ## Forum Replies Created Viewing 3 replies - 1 through 3 (of 3 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[BackWPup – WordPress Backup & Restore Plugin] ERROR: Signal "SIGTERM" is sent to script!](https://wordpress.org/support/topic/error-signal-sigterm-is-sent-to-script/) * [GaryCoon](https://wordpress.org/support/users/garycoon/) * (@garycoon) * [10 years, 1 month ago](https://wordpress.org/support/topic/error-signal-sigterm-is-sent-to-script/page/4/#post-6626682) * I can run DB only OK (One click backup OR job), but Files + DB always seems to fail/have errors. I have read thru the comments here and have emailed 2 support requests (unanswered). I don’t know why I would want to upgrade to Pro if I can’t get the basic plugin working reliably. And thanks for the def of SIGTERM, but I had already guessed it. * My results: Job 1 03-30_18-34-51.zip (1.64 GB on SG Server, 1.76 GB downloaded). It had errors: ERROR: Signal “SIGTERM” is sent to script! [30-Mar-2016 18:38: 11] ERROR: Step aborted: too many attempts! [30-Mar-2016 18:38:11] ERROR: Job has ended with errors in 200 seconds. You must resolve the errors for correct execution. The downloaded zip file opens and appeared to be normal, contained 6228 files and folders, but Zip has Fatal error: 693 when trying to unzip any files. * Job 2 had Gateway Timeout: The gateway did not receive a timely response from the upstream server or application. * =Reinstalled BackWPup plugin= * Job 3 had another Gateway Timeout, restarted, ended with ERROR: Job has ended with errors in 962 seconds. You must resolve the errors for correct execution. Zip file created (1.79 GB downloaded) backwpup_356e5d_2016-03-30_19-23-49.zip, 6317 files. Zip file opened and unzipped without error. * Not sure if I can trust the validity of a backup that ended with errors (# files). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [BackWPup [ERROR] Job restarted, because inactivity!](https://wordpress.org/support/topic/backwpup-error-job-restarted-because-inactivity/) * Thread Starter [GaryCoon](https://wordpress.org/support/users/garycoon/) * (@garycoon) * [11 years ago](https://wordpress.org/support/topic/backwpup-error-job-restarted-because-inactivity/#post-6036962) * Oh, sure, when the backup ran overnight it worked perfectly! TMDHosting must have provided a better connection speed. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [BackWPup [ERROR] Job restarted, because inactivity!](https://wordpress.org/support/topic/backwpup-error-job-restarted-because-inactivity/) * Thread Starter [GaryCoon](https://wordpress.org/support/users/garycoon/) * (@garycoon) * [11 years ago](https://wordpress.org/support/topic/backwpup-error-job-restarted-because-inactivity/#post-6036821) * After 3 errors it finally said job was done, but zip file was not complete. Zip file was too small and it had incomplete error when opened… * 2015/04/20 22:05.24: 1. try for make list of files to backup…. 2015/04/20 22: 05.26: 3817 files with 329.84 MB to backup 2015/04/20 22:05.26: 1. try to create backup zip (PclZip) archive… 2015/04/20 22:21.37: [ERROR] Job restarted, because inactivity! 2015/04/20 22:21.37: 2. try to create backup zip (PclZip) archive… 2015/04/20 22:49.26: [ERROR] Job restarted, because inactivity! 2015/04/20 22: 49.27: 3. try to create backup zip (PclZip) archive… 2015/04/20 23:05.51: [ERROR] Job restarted, because inactivity! 2015/04/20 23:05.52: Job done in 3633 sec. * This looks like timing issues all over the place. Viewing 3 replies - 1 through 3 (of 3 total)