From: Holger P. <wb...@pa...> - 2014-07-02 20:29:35
|
Hi, Les Mikesell wrote on 2014-07-02 07:48:16 -0500 [Re: [BackupPC-users] BUG (IMHO): BackupPC_Dump on QNAP QTS 4.1]: > On Wed, Jul 2, 2014 at 5:55 AM, Paolo Basenghi <pao...@fc...> wrote: > > Il 30/06/2014 19:14, Les Mikesell ha scritto: > >> I'm still confused as to what executing an ssh command has to do with > >> the smb.conf file. [...] > > It turned out that are the QNAP ssh and scp binaries that produce the > > warning about smb.conf parameter, not the smbclient like I guessed. I believe there was also a suspect 'sudo' case? > > I opened a support ticket with QNAP. > > > > But why does BackupPC rsync method block until timeout upon this warning? Good question. > Does ssh work otherwise? BackupPC isn't happy about additional text > coming ahead of the rsync startup, but that usually causes a quick > 'version mismatch' error. During the timeout period you could check > that rsync is actually running at the other end. Bad question :-). You might want to reread the original message: Paolo Basenghi wrote on 2014-06-28 13:04:16 +0200 [[BackupPC-users] BUG (IMHO): BackupPC_Dump on QNAP QTS 4.1]: > [...] > incr backup started back to 2014-06-25 20:00:12 (backup #238) for directory / > started incr dump, share=/ > Running: /opt/bin/ssh -q -x -l root afrodite /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive . / > Xfer PIDs are now 10454 > xferPids 10454 > Got remote protocol 1869506377 > Fatal error (bad version): Ignoring unknown parameter "conn log" > > Sent include: /root > [...] > Sent exclude: /opt/* > fileListReceive() failed > Done: 0 files, 0 bytes > Got fatal error during xfer (fileListReceive failed) > Backup aborted by user signal > dump failed: fileListReceive failed BackupPC *does* in fact detect a "bad version" as expected. I have no idea why it would continue anyway. Note that it *does* continue, not wait for ssh to exit or something like that. Regards, Holger |