Re: [Burp-users] backup of local server stucks
Brought to you by:
grke
|
From: John S. <jo...@st...> - 2026-01-26 22:35:17
|
>>>>> "Marcin" == Marcin Mirosław <ma...@me...> writes:
Just a thought, does the backup fail if you setup a new (local) client
with just that single directory listed as to be backed up? Does it
still fail with just that one file in the directory? Or does it now
suceed?
Just a thought... and it might make it easier to replicate and
actually keep more detailed logs.
> W dniu 2026-01-26 14:04, Marcin Mirosław napisał(a):
>> Hi,
>> I saw a little similar problem described by Mark in thread "Timeout?"
>> but there were no clear solution nor description of root problem. I've
>> got burp server, it does backup network connected clients without
>> issue. Local client can't do backup since 2025-09-28, burp client seems
>> to stuck short after start of phase2.
>> In backup directory there is a couple of files, client stuck, I think,
>> when i starts to read a little bigger file (about 2-3MB). I could
>> suspect something like MTU problem but connection is via 127.0.0.1
>> (also tried using ip of eth interface - no change) so MTU shouldn't be
>> case in this configuration. Strace shows:
>>
>> n\0%s %s\n\0Packaged by %s (%"..., 4096) = 4096
>> 13141 12:54:23.810144 pselect6(5, [], [4], [4], {tv_sec=1, tv_nsec=0},
>> NULL) = 0 (Timeout)
>> 13141 12:54:24.811442 read(5, "backup is given)\n numbered, t make
>> numbered backups\n existing, nil numbered if numbered backups exist,
>> simple otherwise\n simple, never always make simple
>> backups\n\0\0\0\nUsing -s
>> ignores -L and -P. Otherwise, the last option specified
>> controls\nbehavior when a TARGET is a symbolic link, defaulting to
>> %s.\n\0\0\0\0\0\0\0Report any translation bugs to
>> <https://translationproject.org/team/>\n\0\0https
>> ://www.gnu.org/software/coreutils/\0or available locally via: info
>> '(coreutils) %s%s'\n\0\0\0\0\0\0multiple target directories
>> specified\0\0\0cannot do --relative without --symbolic\0cannot combine
>> --target-directory and --n
>> o-target-directory\0\0\0\0\0missing destination file operand after
>> %s\0\0\0\0\0\0\0# buckets used: %lu
>> (%.2f%%)\n\0\0\0\0\0\0\0\0License GPLv3+: GNU GPL version 3 or later
>> <%s>.\nThis is free software: you are free to cha
>> nge and redistribute it.\nThere is NO WARRANTY, to the extent permitted
>> by
>> law.\n\0\0\0\0\0\0https://gnu.org/licenses/gpl.html\0\0\0\0\0\0\0Written
>> by %s, %s, %s,\nand %s.\n\0Written by %s, %s, %s,\n%s, and "..., 4096)
>> = 409
>> 6
>> 13141 12:54:24.811797 pselect6(5, [], [4], [4], {tv_sec=1, tv_nsec=0},
>> NULL) = 0 (Timeout)
>> 13141 12:54:25.813136 read(5,
>> "x\37\0\0\220\314\377\377\244\37\0\0\20\315\377\377\320\37\0\0\20\316\377\377\374\37\0\0P\316\377\377\30
>> \0\0\220\316\377\3774 \0\0\260\316\377\377P \0\0\320\316\377\377l
>> \0\0\20\317\377\377\230"...
>> , 4096) = 4096
>> 13141 12:54:25.813555 pselect6(5, [], [4], [4], {tv_sec=1, tv_nsec=0},
>> NULL) = 0 (Timeout)
>> 13141 12:54:26.814914 pselect6(5, [], [4], [4], {tv_sec=1, tv_nsec=0},
>> NULL) = 0 (Timeout)
>> 13141 12:54:27.816160 pselect6(5, [], [4], [4], {tv_sec=1, tv_nsec=0},
>> NULL) = 0 (Timeout)
>>
>>
>>
>> What could be a reason of this problem with taking backup?
>> Marcin
>>
> client throwed:
> ff2026-01-26 14:12:52 +0100: burp[30645] main socket 4: Got network
> write error
> 2026-01-26 14:12:52 +0100: burp[30645] main socket 4: network write
> problem in asfd_do_write_ssl: 5 - 110=Connection timed out
> 80ABF6F7A17F0000:error:8000006E:system
> library:tls_retry_write_records:Connection timed
> out:../openssl-3.5.4/ssl/record/methods/tls_common.c:1942:tls_retry_write_records
> failure
> 2026-01-26 14:12:52 +0100: burp[30645] This is probably caused by the
> peer exiting.
> 2026-01-26 14:12:52 +0100: burp[30645] Please check the peer's logs.
> 66
> --------------------------------------------------------------------------------
> Start time: 2026-01-26 13:56:40
> End time: 2026-01-26 14:12:52
> Time taken: 16:12
> New Changed Duplicate Deleted Total |
> Scanned
> ------------------------------------------------------------
> Files: 66 0 0 0 66 |
> 275105
> Meta data: 0 0 0 0 0 |
> 33803
> Directories: 0 0 0 0 0 |
> 20809
> Hard links: 0 0 0 0 0 |
> 1491
> Soft links: 0 0 0 0 0 |
> 13191
> Special files: 0 0 0 0 0 |
> 1227
> Grand total: 66 0 0 0 66 |
> 345626
> ------------------------------------------------------------
> Messages: 0
> Warnings: 16
> Bytes estimated: 15521570387 (14.46 GB)
> Bytes in backup: 10926403 (10.42 MB)
> Bytes received: 7737 (7.56 KB)
> Bytes sent: 64739830 (61.74 MB)
> --------------------------------------------------------------------------------
> 2026-01-26 14:12:52 +0100: burp[30645] Error in phase 2
> 2026-01-26 14:12:52 +0100: burp[30645] Phase 2 end (send file data)
> server log:
> 026-01-26 13:56:48 +0100: burp[30646] End phase1 (file system scan)
> 2026-01-26 13:56:48 +0100: burp[30646] Begin phase2 (receive file data)
> 2026-01-26 14:12:52 +0100: burp[30646] main socket 8: Got network read
> error
> 2026-01-26 14:12:53 +0100: burp[30646] main socket 8: network read
> problem in asfd_do_read_ssl: 5 - 104=Connection reset by peer
> 2026-01-26 14:12:53 +0100: burp[30646] This is probably caused by the
> peer exiting.
> 2026-01-26 14:12:53 +0100: burp[30646] Please check the peer's logs.
> 2026-01-26 14:12:53 +0100: burp[30646] error in backup_phase2_server_all
> 2026-01-26 14:12:53 +0100: burp[30646] last tried file:
> f:0073:/[snip]/.fastresume
> 2026-01-26 14:12:53 +0100: burp[30646] End phase2 (receive file data)
> 2026-01-26 14:12:53 +0100: burp[30646] error in backup phase 2
> 2026-01-26 14:12:53 +0100: burp[30646] Backup failed
> _______________________________________________
> Burp-users mailing list
> Bur...@li...
> https://lists.sourceforge.net/lists/listinfo/burp-users
|