SIGTERM means that the server send a Termination request to the backup script.
You can try to configure BackWPup > Settings > Tab: Job the maximum execution time.
We also have this Problem since we upgraded to v.3.2.1.
The maximum excecution time was set to 0. This was no Problem.
With the new Version it is. I have set it to 20 Seconds to get it to work.
But with 20 Seconds the FTP Upload is always disrupted and often restarted.
It works, but not so nice as with the old Version.
Maybe there is a way to change this behaviour?
Thanks for this great Plugin!
Brudertac
I have added a filter to disable signal handling in the last version.
add_filter( 'backwpup_job_signals_to_handel', __return_empty_array() );
placed in funtions.php will remove signakl handling. But i don’t think that is the better way.
I am not sure that i understand you correct. Is that what you have changed from the last (old) Version to the actual Version? (Then this is what causes the Problem?)
Or it this a way to handle the Error. Then the question is what was the change in the latest Version. Because it was working fine.
Thanks again!
Brudertac
The answer for the question is that there ar users wher we can’t find the abbortion of scripts. Now there will hopfully displayed.
That line you kan add in a Plugin or functions.php of you the to disable the singal handling.
Hello, I am also getting this error. I’m with siteground. Can anybody please help, I’ve been trying for 3 days to create one backup.
Thanks
On sitegound place check that you use the newest BackWPup version and that under BackWPup > Settings > Tab: Jobs “Enable an empty Output on backup working.” is diabled!
I had the latest version of the plugin and I have “Enable an empty Output on backup working” disabled but I am still getting the error.
@tomcho…
Our Webhost, SiteGround, just upgraded our server to a new platform, including SSD drives. All of our BackWPup errors went away and backup times went from 300+- seconds, to 30+- seconds!
It is my understanding that SiteGround is in the process of upgrading ALL of their servers. So if you’re on SiteGround, this error may go away soon. If you’re not on SiteGround, maybe explore speed/load issues with your Webhost that may be causing this error.
