OpenID
Log In | Register
Skip to main content
Recent Posts
21
WHM Backup Solutions Script Support / Re: The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
I enabled logging on my FTP server to see if that would shed some light.

I noticed in the log that because this backup is much larger than the rest of them.. the next backup starts before this one completes.  I had them spaced out 10 mins apart (the one cron job is set to run every 10 mins).   Normally they complete within a min or two including ftp upload.  But this one takes 13 mins to complete from start to finish.   It takes 6 mins to build the backup then another 7mins to transfer and the next one is already running by the time this one starts.

I also noticed that the upload does complete but there is no goodbye message just shows it completed then disconnected.  The other backups show a goodbye message.  So i'm hoping this is because it has something to do with the next backup already starting from the same server.  

Would be nice if you could disable keeping the backup file in the home directory weather it thinks the backup successfully transferred or not.  If anyone knows if this could be scripted; let me know as i have no idea.  But I can see problems for others if an ftp backup transfer gets interrupted or something happens.. most likely it would be more important to discard the backup then to clog up the home directory.

So for now i've adjusted the backups to run every 30 mins instead of 10.  Giving large backup plenty of time to complete.   I will report back if adjusting the backup period resolves the issue.  I'm hoping that it does. 
22
WHM Backup Solutions Script Support / Re: The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
Quote from: rob_van on
Quote from: rob_van on
Quote from: rob_van on
So i did a little research with my FTP server - it appears that connection timeout setting on the server may come into play here.   My guess is the client (whm/cpanel server in this case)  is not giving a reply because the connection was closed (as it takes awhile for the large file transfer).

sorry i mean - the client is given a reply from the FTP server

i'll post any updates to see if the connection time out fixes the problem

err..  no reply is given to the client rather.  Sorry not sure if i can edit a post.. :)  or delete them.. 

Hopefully this fixes.. will update tomorrow

unfortunately this did not resolve the issue..  still getting upload failed..  i will continue to investigate.. if anyone has any ideas please let me know..
23
WHM Backup Solutions Script Support / Re: The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
Quote from: rob_van on
Quote from: rob_van on
So i did a little research with my FTP server - it appears that connection timeout setting on the server may come into play here.   My guess is the client (whm/cpanel server in this case)  is not giving a reply because the connection was closed (as it takes awhile for the large file transfer).

sorry i mean - the client is given a reply from the FTP server

i'll post any updates to see if the connection time out fixes the problem

err..  no reply is given to the client rather.  Sorry not sure if i can edit a post.. :)  or delete them.. 

Hopefully this fixes.. will update tomorrow
24
WHM Backup Solutions Script Support / Re: The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
Quote from: rob_van on
So i did a little research with my FTP server - it appears that connection timeout setting on the server may come into play here.   My guess is the client (whm/cpanel server in this case)  is not giving a reply because the connection was closed (as it takes awhile for the large file transfer).

sorry i mean - the client is given a reply from the FTP server

i'll post any updates to see if the connection time out fixes the problem
25
WHM Backup Solutions Script Support / Re: The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
I'm just going to post some updates here in the hopes to help someone else with this problem.

After examining the email I receive from the problem account - the subject and the first line say..  "A full backup has completed, but the upload has failed. "

The backup does complete though - the file is there on the ftp server and intact.... 

So i did a little research with my FTP server - it appears that connection timeout setting on the server may come into play here.   My guess is the client (whm/cpanel server in this case)  is not giving a reply because the connection was closed (as it takes awhile for the large file transfer).  Cpanel assumes the transfer failed.   So i checked the connection timeout setting; it was set to 120 seconds on the server by default.   I've increased this to 1 hour (could disable it entirely) although I figure an hour is enough for me the transfer only takes a few mins.    This may not help though because firewalls or routers could force the connection to close earlier.  There are keep alive settings but i dont see this option on the server side.     

I'm hoping this will resolve the problem; i will try and post back if it does.

The biggest problem is that cpanel will store the file locally in a shared server/reseller environment (with no way to configure this); in the clients account if it fails.. so its going to run out of disk space.  If disk space runs out then the client wont recieve emails and this is a big problem    It's expensive to just double up all users disks just because of backups (incase one fails).  It'd be nice if there was a n on or off switch for this; or if it could be scripted.. but seems like this is a cpanel thing not configurable or if it is; it's not available to resellers...

Seems a tad dangerous to run this way.. could use rsync alternatively i guess.. and just do file level backups from another server.. But this starts to defeats the purpose i guess - as you may as well just run vps at this point.. 

i will post any updates - hopefully this resolves the issue.
26
WHM Backup Solutions Script Support / The subprocess ended prematurely because it received the “KILL” (9) signal.
Last post by rob_van -
Hello,

Thanks for this wonderful script.   Recently i've been having an issue with a larger account.  The strange thing is the backup completes alright - I use SFTP site and the file gets transferred okay..

But I received an alert that one account was out of disk space..  I noticed a large backup file that was sitting in the home directory...  and the user was out of disk space.  So i increased the disk space but the problem still happens.  I noticed this in the generated backup email.. below:

The backup file is named “backup-1.23.2020_01-00-02_xxxxxxx.tar.gz”
The backup transferred via “FTP” to the server “xxxxxxxx.canadacentral.cloudapp.azure.com” as user “xxxxxxxxxx” in the “/” directory.
The backup process encountered the following error:
The subprocess ended prematurely because it received the “KILL” (9) signal.

When i examine the log file.. the last line instead of saying the file was transferred via ftp successfully.. it says
The subprocess ended prematurely because it received the “KILL” (9) signal with no ftp tranfer successfull message.

But strangely enough - the file appears to be transferred to the ftp site and it does say it was transferred in the email..     But because it doesn't think it has been transferred it wont remove the file from the account and disk space is getting chewed up.. that or the clean up script is failing - if it deletes the file does it permanently delete the file or put into a recycleing bin.. Maybe its not able to delete the file because of a space issue (if it's not permanently deleting the file).  If i delete the file manually it asks if i want to permanently delete the file i always choose yes.

So for now i've been manually remove the backup file - so there is no inturrption in email flow to the account (so it doesn't run out of disk space) .. but any idea what could be the issue?

I've check my ftp server - there is no limit on data transfer that i can see I'm using filezilla server - i see a file sitting there at 12GB's.. and its been growing.. after backups.

Is there anything in the script that would have a limit or ftp transfer?  I guess my next step would be to enable logging on filezilla.. i've yet to get the host involved; as the backup runs fine; i'm not sure it has anything to do with them at this point.

Anyone seen this error before - or have any idea what the problem might be.  At first i thought its the cleanup script? or a memory issue? but now i'm leaning towards an ftp transfer issue; although the file looks intact on the other side.. from what i can tell.

27
Change Log / V1.3 & V1.4
Last post by Pete -
This change log is merged for versions 1.3 and 1.4.
Due to some issues affecting the curl timeout and the upgrade process when using command line/cron job, i've pushed these updates out with a matter of urgency.

Unfortunately due to a bug fixed in V1.4, the script isn't able to upgrade to the latest version automatically unless run in the web browser.
28
Change Log / V1.2
Last post by Pete -
The final build of 2019! Resolving a few issues identified as a result of users who've got in contact.

  • BUG FIX: cPanel API CURL Timeout Added.
  • BUG FIX: WHM port value was being ignored.
  • COMMENT FIX: $config['whm_port'] comment referred to this as the cPanel login port value. This should be the port used for logging into WHM as per the variable name.

For a full list of commits/changes, see https://bitbucket.org/peterk1992/whm-backup-solutions/commits/
29
WHM Backup Solutions Script Support / Re: "Run Account Backup" Cron Timing
Last post by Pete -
Hi JCWacky,

Nothing bad will happen. The documentation guide refers to 10 minutes, to just reduce/balance out any backups. However, reducing this to even every 2 minutes shouldn't create much of an issue as behind the scenes. Each cPanel server is configured to only let backups be created when the server load is below a certain value (Set by your webhost or root user). If the server load is above that value it will simply be added to a queue until the server load drops enough for it to start processing backups.
30
WHM Backup Solutions Script Support / "Run Account Backup" Cron Timing
Last post by jcwacky -
The instructions state that the "Run Account Backup" cron should be set to run every 10 mins. Just wondering the reasoning behind this value and what would happen if I were to reduce it to 5 mins? Do bad things happen if it tries to back up the next account before the previous one is complete?

With 100 accounts, backing up one every 10 mins takes over 16 hours, so just wondering if I can reduce this time by setting this cron to run more often?

Thanks!