BackWPup Error: Signal “SIGHUP” is sent to script!

  • Resolved maorb

    (@maorb)


    5 months, 2 weeks ago

    Hi,

    Thanks for your great BackWPup plugin, I’m using the free version of it to backup to Dropbox and it’s working well. In the last scheduled backup, this error appeared on the log file:

    [01-Jun-2024 03:33:17] Backup archive created.
[01-Jun-2024 03:33:17] Archive size is 1.99 GB.
[01-Jun-2024 03:33:17] 43550 Files with 2.32 GB in Archive.
[01-Jun-2024 03:33:18] 1. Try to send backup file to Dropbox …
[01-Jun-2024 03:33:20] Authenticated with Dropbox of user: The New Fund for Cinema and Television
[01-Jun-2024 03:33:20] Uploading to Dropbox …
[01-Jun-2024 03:33:20] Beginning new file upload session
[01-Jun-2024 04:04:16] ERROR: Signal "SIGHUP" (Hangup detected on controlling terminal or death of controlling process) is sent to script!
[01-Jun-2024 04:04:21] ERROR: Signal "SIGHUP" (Hangup detected on controlling terminal or death of controlling process) is sent to script!
[01-Jun-2024 04:04:22] 2. Try to send backup file to Dropbox …
[01-Jun-2024 04:04:23] Authenticated with Dropbox of user: The New Fund for Cinema and Television
[01-Jun-2024 04:04:23] Uploading to Dropbox …
[01-Jun-2024 04:19:06] Finishing upload session with a total of 2 GB uploaded
[01-Jun-2024 04:19:07] Backup transferred to /websitebackup-DO-NOT-DELETE/2024-06-01_03-05-07_RIE34YLW01.tar.gz
[01-Jun-2024 04:19:09] One file deleted from Dropbox
[01-Jun-2024 04:19:09] ERROR: Job has ended with errors in 4442 seconds. You must resolve the errors for correct execution.

    I use the tar.gz compresssion, and the maximum script execution time is set to 60seconds in the plugin’s setting.
    As I saw in another ticket here with this error, you suggested that it might appear due to limitation of the hosting provider, but all previous backups were ok and nothing was changed with my hosting.
    Also, the file size of previous backups were the same, about 2GB compressed, and it went ok with no errors, and also there is not a quota issue on the server nor in Dropbox. So I believe there is no reason to split the backup job into two.
    Everything was ok with the backup proces until last one that this error came up.

    I saw a setting of “Reduce server load” which was always disabled, should I try to set it to other option?

    As you may see in the log above, all files have been added to the backup archive file, and the Signal “SIGHUP” was sent after trying to upload it. May it be an error with Dropbox?

    Any other ideas about what could I do to debug it further and fix this issue?

    Thanks ahead,
    Maor

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter maorb

    (@maorb)

    Hi,

    I add here that I’ve checked now on Dropbox itself and found that the full backup file (2GB) is actually there and I was able to manually download it and extract it, so it was uploaded ok although these SIGHUP error signals. So, is there something that needed to be addressed and done with this issue?

    Thanks

    Plugin Support happyAnt

    (@duongcuong96)

    @maorb,

    ERROR: Signal “SIGHUP” is returned from your server. You can try to lower the max execution time to like 20 seconds instead of 60 seconds to let the job restart and resume after each 20s.

    This can help avoid the long-running job that causes the server to try and stop the backup process.

    I hope my answer could help!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.