Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Backup transport errors

Discussion in 'Data Protection' started by Israel_Paya, Sep 4, 2017.

Tags:
  1. Israel_Paya

    Israel_Paya Active Member

    Joined:
    Sep 18, 2015
    Messages:
    36
    Likes Received:
    2
    Trophy Points:
    8
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    I am experiencing problems with backup transport files. It does not transport any of the accounts backup to my NAS. It used to work fine, but last night it gave up transporting the files to my NAS. Is it due to a cPanel update? How can it be solved?

    Thank you.
     
  2. Eminds

    Eminds Well-Known Member

    Joined:
    Nov 10, 2016
    Messages:
    204
    Likes Received:
    12
    Trophy Points:
    18
    Location:
    India
    cPanel Access Level:
    Root Administrator
    If you have root access of the server check the below logs at

    /usr/local/cpanel/logs/cpbackup & /usr/local/cpanel/logs/cpbackup_transporter and it will give you an idea of whats happening.
     
  3. 24x7server

    24x7server Well-Known Member

    Joined:
    Apr 17, 2013
    Messages:
    1,445
    Likes Received:
    56
    Trophy Points:
    28
    Location:
    India
    cPanel Access Level:
    Root Administrator
    ,
    To check the issue again, you have to execute it manually again and see what do you see whether there is connection issue or timeout. Execute it manually and then keep an eye on it for first few backups.
     
  4. Israel_Paya

    Israel_Paya Active Member

    Joined:
    Sep 18, 2015
    Messages:
    36
    Likes Received:
    2
    Trophy Points:
    8
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    Thank you for your prompt reply.

    This is what these 2 files say:
    Code:
    root@server1 [/usr/local/cpanel/logs/cpbackup]# ls -la
    total 8936
    drwx------ 2 root root   4096 Sep  5 02:00 ./
    drwx--x--x 8 root root   4096 Sep  5 02:13 ../
    -rw------- 1 root root 720131 Aug 26 05:47 1503705601.log
    -rw------- 1 root root 725701 Aug 27 05:58 1503792002.log
    -rw------- 1 root root 719779 Aug 28 05:47 1503878402.log
    -rw------- 1 root root 726440 Aug 29 05:59 1503964801.log
    -rw------- 1 root root 728979 Aug 30 06:03 1504051201.log
    -rw------- 1 root root 719915 Aug 31 05:47 1504137601.log
    -rw------- 1 root root 724143 Sep  1 05:54 1504224001.log
    -rw------- 1 root root 719470 Sep  2 05:48 1504310401.log
    -rw------- 1 root root 726214 Sep  3 06:00 1504396801.log
    -rw------- 1 root root 850987 Sep  4 06:32 1504483201.log
    -rw------- 1 root root 865420 Sep  4 14:18 1504509603.log
    -rw------- 1 root root 846675 Sep  5 06:25 1504569601.log
    root@server1 [/usr/local/cpanel/logs/cpbackup]# cd /usr/local/cpanel/logs/cpbackup_transporter
    root@server1 [/usr/local/cpanel/logs/cpbackup_transporter]# ls -la
    total 6668
    drwx------ 2 root root    4096 Sep  5 02:04 ./
    drwx--x--x 8 root root    4096 Sep  5 02:13 ../
    -rw-r----- 1 root root  412108 Aug 23 10:58 cpbackup_transporter.1503392728.log
    -rw-r----- 1 root root  212040 Aug 25 02:08 cpbackup_transporter.1503566100.log
    -rw-r----- 1 root root  412694 Aug 26 10:59 cpbackup_transporter.1503653005.log
    -rw-r----- 1 root root  418666 Aug 28 10:57 cpbackup_transporter.1503824269.log
    -rw-r----- 1 root root  419298 Aug 30 11:09 cpbackup_transporter.1503997284.log
    -rw------- 1 root root  214242 Sep  1 02:08 cpbackup_transporter.1504170278.log
    -rw-r----- 1 root root  416488 Sep  2 11:08 cpbackup_transporter.1504256861.log
    -rw------- 1 root root  244995 Sep  4 02:09 cpbackup_transporter.1504429649.log
    -rw-r----- 1 root root 1977027 Sep  4 09:30 cpbackup_transporter.1504499804.log
    -rw-r----- 1 root root 2031802 Sep  5 02:11 cpbackup_transporter.1504527777.log
    root@server1 [/usr/local/cpanel/logs/cpbackup_transporter]# tail -f cpbackup_transporter.1504527777.log
        cPanel::TaskQueue::__ANON__() called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 237
        eval {...} called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/StateFile.pm line 237
        cPanel::StateFile::Guard::call_unlocked(cPanel::StateFile::Guard=HASH(0x3cb35d8), CODE(0x3cabd28)) called at /usr/local/cpanel/3rdparty/perl/524/lib64/perl5/cpanel_lib/cPanel/TaskQueue.pm line 637
        cPanel::TaskQueue::process_next_task(cPanel::TaskQueue=HASH(0x35b6ac0)) called at /usr/local/cpanel/bin/cpbackup_transporter line 151
        eval {...} called at /usr/local/cpanel/bin/cpbackup_transporter line 149
    [2017-09-05 02:11:04 +0200] info [cpbackup_transporter] Error encountered
    [2017-09-05 02:11:04 +0200] info [cpbackup_transporter] Error is not a reference Unable to make path, bad root
    [2017-09-05 02:11:13 +0200] info [cpbackup_transporter] cpbackup_transporter - Checking queue for tasks
    [2017-09-05 02:11:13 +0200] info [cpbackup_transporter] cpbackup_transporter - Exiting - the queue has been emptied; no more work to do
    [2017-09-05 02:11:13 +0200] info [cpbackup_transporter] cPanel Backup Transporter Queue Daemon is being stopped.
    tail -f 1504569601.log
    ^C
    root@server1 [/usr/local/cpanel/logs/cpbackup_transporter]# cd ..
    root@server1 [/usr/local/cpanel/logs]# cd cpbackup
    root@server1 [/usr/local/cpanel/logs/cpbackup]# tail -f 1504569601.log
    [2017-09-05 06:24:59 +0200] info [backup] Pruning backup directory: /home/backup/2017-08-29
    [2017-09-05 06:25:12 +0200] info [backup] Queuing prune operation for remote destination daily backups
    [2017-09-05 06:25:12 +0200] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:73175
    [2017-09-05 06:25:12 +0200] info [backup] leaving queue_backup_transport_item
    [2017-09-05 06:25:12 +0200] info [backup] Queuing transport reporter
    [2017-09-05 06:25:12 +0200] info [backup] no_transport = 0 .. and queueid = TQ:TaskQueue:73176
    [2017-09-05 06:25:12 +0200] info [backup] leaving queue_backup_transport_item
    [2017-09-05 06:25:12 +0200] info [backup] Completed at Tue Sep  5 06:25:12 2017
    [2017-09-05 06:25:12 +0200] info [backup] Final state is Backup::Success (0)
    [2017-09-05 06:25:12 +0200] info [backup] Sent Backup::Success notification.
    
    
     
    #4 Israel_Paya, Sep 5, 2017
    Last edited by a moderator: Sep 5, 2017
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,080
    Likes Received:
    1,364
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    Could you verify if switching to the "yourdirectory/" path for this backup destination, or leaving the field blank, results in the same error message? If so, could you verify if the remote SFTP server you are configuring runs Windows 10? There's an internal case open to address a related issue:

    Backup to remote has auth issues

    Thank you.
     
  6. Israel_Paya

    Israel_Paya Active Member

    Joined:
    Sep 18, 2015
    Messages:
    36
    Likes Received:
    2
    Trophy Points:
    8
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    The folder is created in the remote NAS, for example, 2017-0-04 and the system files are transported, but not the rest of the hostings. I have entered /home/backup, which is where the backups are stored in the server and have realized that from 2017-09-04, which is when Centos or cPanel were updated, something strange happens. Before the zip files created inside /home/backup another file with the name of the hosting plus -\=-meta appears. I think this is not allowing the transport of the files. See some of the files I found inside /home/backup:

    -rw------- 1 root root 1191636 Sep 6 05:02 quantumexperimen-\=-meta
    -rw------- 1 root root 114106833 Sep 6 05:02 quantumexperimen.tar.gz
    -rw------- 1 root root 1053190 Sep 6 06:05 ranchobuena296-\=-meta
    -rw------- 1 root root 161731552 Sep 6 06:04 ranchobuena296.tar.gz
    -rw------- 1 root root 3584456 Sep 6 05:37 rodrigopronuevaw-\=-meta
    -rw------- 1 root root 788586556 Sep 6 05:37 rodrigopronuevaw.tar.gz

    Why does this happen? How can I solve, please?
     
  7. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,080
    Likes Received:
    1,364
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page