Hi there,

On Sat, 22 Jan 2022, Jeff Kosowsky wrote:

...
  log: recv cS+++++++++ rwxrwx---     1006,    1006         0 cam_socket0
  log: recv cS+++++++++ rwxrwx---     1006,    1006         0 cam_socket1
  log: recv >f+++++++++ rwx------     1000,    1000         8 hidden_volume.txt

it seems like it gets stuck somewhere between backing up
'cam_socket1' and 'hidden_volume.txt' since the last BackupPC log line
I see is:
 recv cS+++++++++ rwxrwx---     1006,    1006         0 cam_socket1

If the problem is backing up a 'socket', the problem is not in native
rsync as it proceeds fine but rather presumably in rsync_bpc.
...

Seems odd to me that it's trying to back up a socket at all.  AFAICR
neither rsync nor rsync-bpc (at least recent versions) will read a
socket without for example being given the '--specials' option.  I
believe it's mentioned in the rsync-bpc changelogs for around 2006.

Anyway I'd definitely want to avoid trying to back up sockets, raw
devices, and anything like that.

Last time I had BackupPC transfers timing out was when something which
used X went off the reservation and wrote *huge* hidden errors file in
a user's home directory.  Took a while to find. :/

--

73,
Ged.


_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to