same problem here with Debian Jessie on amd64 with python-larch 1.20131130-1
and obnam 1.8-1.
Did anyone found an alternative? I just need:
* backup over sftp
* gpg encryption support (signature using different key would be nice too)
* automatic checkpoints
* should be in Debian Jessie
*
On Fri, Aug 21, 2015 at 12:30:31PM +, Franz Schrober wrote:
same problem here with Debian Jessie on amd64 with python-larch
1.20131130-1 and obnam 1.8-1.
Do you get an error message saying there are too many open files, or
just an error message that a node is missing?
--
sic transit disci
Package: obnam
Followup-For: Bug #682798
There seems to be a problem with how obnam deals with ENOMEM conditions,
causing it to leak pipes.
Yet another trial run failed. This time I ran a lsof process periodically in
another screen window:
% (export LC_ALL=C ; while :; do date; really lsof
Package: obnam
Followup-For: Bug #682798
I tried to continue the backup with a raised open file limit, similar failure.
(The backup disk is mounted over NFS, which may complicate things.)
[... lots of too many open files errors deleted ...]
2012-07-26 17:58:21 ERROR Can't back up
Package: obnam
Followup-For: Bug #682798
I have another attempt running so far for 4½ hours; lsof shows obnam has a lot
of pipes open!
# lsof -c obnam | grep -c pipe$
2042
# lsof -c obnam | grep pipe$ | head
obnam 21834 root1w FIFO0,7 0t0 10250227 pipe
obnam 21834 root2w
Package: obnam
Version: 1.1-1
I've been trying to do an initial full backup of my server using obnam, but it
reliably fails with the error message
ERROR: Node 1598 cannot be found in the node store 1566508680438567912
(the numbers change between attempts) about 12 hours into the backup run. I
6 matches
Mail list logo
