IF the special configurations for that package ?
Hi Daniel,
Not really. It backs up the files (just the upload directory & the theme), and saves the plugins in a list.
Wierdly from bug testing, it appears that should the upload date folder not have any files in it, it works okay.
I log into the site via FTP, and those files (which show in the back end of WordPress fine and HTTP fine), aren’t appearing.
….I’m beginning to think it’s a hosting issue.
I will get back to you 🙂
I’m getting message as well since the last update. Before I got SIGALRM.
Backups are sent to Dropbox though. They also seem to be fine.
Hi, i’ve got the same problem..
How can i do to do my backup?
Thanks
Hi,
We also receive this problem lately. Updating plugin to latest version but it did not fix the issue. Tried extending to script time-out to 60 seconds but that also didn’t help
WordPress version 4.3.1
[12-Oct-2015 11:03:29] 1. Trying to generate a manifest file …
[12-Oct-2015 11:03:29] Added manifest.json file with 5.50 kB to backup file list.
[12-Oct-2015 11:03:29] 1. Trying to create backup archive …
[12-Oct-2015 11:03:29] Compressing files as TarGz. Please be patient, this may take a moment.
[12-Oct-2015 11:13:17] WARNING: Cannot modify header information – headers already sent by (output started at /home/infi1020/public_html/wp-includes/functions.php:3339)
[12-Oct-2015 11:19:24] 2. Trying to create backup archive …
[12-Oct-2015 11:24:48] ERROR: Signal “SIGTERM” is sent to script!
[12-Oct-2015 11:24:57] 3. Trying to create backup archive …
Kind Regards,
Gabriel
Hello!
We’re getting the same error, but it seems to work (at least for now) if we change the Maximum script execution time to 20.
Yeah i’ve read that in a couple places but the timeout was already set to 20 for me. I increased it to 60 seconds and it still fails.
Hmmm… then another solution is required, or a fix in a future update.
Also seeing this error on a job that backs up to Amazon S3. Don’t think it is related to timeout as it happens on a DB only update that takes 2 seconds.
Having this same issue.
[INFO] BackWPup 3.2.1; A project of Inpsyde GmbH
[INFO] BackWPup job: SMSA file & XML backup
[INFO] Logfile is: backwpup_log_4222f0_2015-10-28_03-41-12.html
[INFO] Backup file is: SMSA_backwpup_full_backup_4222f0_2015-10-28_03-41-12.tar
[28-Oct-2015 03:41:12] 1. Trying to make a list of folders to back up …
[28-Oct-2015 03:41:13] Added "wp-config.php" to backup file list
[28-Oct-2015 03:41:13] 758 folders to backup.
[28-Oct-2015 03:41:13] 1. Trying to create a WordPress export to XML file …
[28-Oct-2015 03:41:48] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:41:51] 2. Trying to create a WordPress export to XML file …
[28-Oct-2015 03:42:32] Check WP Export file …
[28-Oct-2015 03:42:32] WP Export file is a valid WXR file.
[28-Oct-2015 03:42:32] Compressing file …
[28-Oct-2015 03:42:33] Compressing done.
[28-Oct-2015 03:42:33] Added XML export "SMSA.wordpress.2015-10-28.xml.gz" with 1.15 MB to backup file list.
[28-Oct-2015 03:42:36] 1. Trying to generate a manifest file …
[28-Oct-2015 03:42:36] Added manifest.json file with 7.21 kB to backup file list.
[28-Oct-2015 03:42:36] 1. Trying to create backup archive …
[28-Oct-2015 03:42:36] Compressing files as Tar. Please be patient, this may take a moment.
[28-Oct-2015 03:43:23] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:43:24] 2. Trying to create backup archive …
[28-Oct-2015 03:44:11] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:44:12] 3. Trying to create backup archive …
[28-Oct-2015 03:44:59] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:45:01] 4. Trying to create backup archive …
[28-Oct-2015 03:45:47] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:45:52] 5. Trying to create backup archive …
[28-Oct-2015 03:46:35] ERROR: Signal "SIGTERM" is sent to script!
[28-Oct-2015 03:46:37] ERROR: Step aborted: too many attempts!
[28-Oct-2015 03:46:37] 1. Try to send backup file to Dropbox …
[28-Oct-2015 03:46:38] Authenticated with Dropbox of user: xxxxxxxx
[28-Oct-2015 03:46:38] Uploading to Dropbox …
[28-Oct-2015 03:46:39] One old log deleted
[28-Oct-2015 03:46:39] ERROR: Job has ended with errors in 327 seconds. You must resolve the errors for correct execution.
Timeout is already set to maximum.
What is the solution, please?
I have been using this plugin for months. Now, I get error messages every single day on three backup jobs on websites that don’t even change.
It is either a warning “WARNING: Job restarts due to inactivity for more than 5 minutes.” or an error message “ERROR: Signal “SIGTERM” is sent to script!”. It seems DropBox doesn’t like having BackWPup uploading files to it every day. 😉 Since I am not the only one, I hope you will be able to fix it. Keep up the good job!!
1st time this appeared for me, today
[...]
[01-Nov-2015 03:33:35] 1. Versuche, das Backup zur Dropbox zu senden …
[01-Nov-2015 03:33:36] Authentifiziert mit der Dropbox von:
[01-Nov-2015 03:33:36] Hochladen zur Dropbox hat begonnen …
[01-Nov-2015 03:34:41] FEHLER: Signal "SIGTERM" wurde an das Script geschickt!
[...]
2.Versuch hat dann geklappt.
1st try failed with SIGTERM, 2nd was ok.
I am also getting this error with version 3.2.1, but it seems it only happens when I compress the archive with Zip. When set it to Tar, the error goes away.
(WP 4.3.1)
started using this plugin recently, getting the same error as you guts. Any word from the plugin dev about this?
+1
I have been receiving this very message since 25/9/15, almost every day.
I have unsuccessfully tried some solutions found in other posts.
This used to be a great plugin and I would not like to delete it.
However, this seems to be a very probable option unless a miracle happens in the next weeks.
