duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] OSError: [Errno 35] Resource temporarily unavailabl


From: edgar . soldin
Subject: Re: [Duplicity-talk] OSError: [Errno 35] Resource temporarily unavailable
Date: Fri, 24 Jun 2011 17:10:52 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11

this really smells like all the gpg processes keep hanging around an python 
cannot get/deliver more file handlers.

see
http://article.gmane.org/gmane.comp.sysutils.backup.duplicity.general/3630/match=resource+temporarily+unavailable

we have a solution for linux. but that seems not to work under mac osx as in 
your case.

btw. your backup chain is really really really long. you should consider doing 
fulls from time to time, which circumvents the error above and has teh 
advantage that not every chain gets corrupted becuase one volume might be.

could you try restoring on a machine with more ram OR raise the setting for 
open file descriptors on osx (ulimit n reports 256 on an osx here).


ede/duply.net

On 24.06.2011 16:41, Chris Poole wrote:
> Hi,
> 
> I am trying to restore a backup. It gets so far then falls over, ending with
> these messages:
> 
>     Traceback (most recent call last):
>       File "/usr/local/bin/duplicity", line 1311, in <module>
>         with_tempdir(main)
>       File "/usr/local/bin/duplicity", line 1304, in with_tempdir
>         fn()
>       File "/usr/local/bin/duplicity", line 1238, in main
>         restore(col_stats)
>       File "/usr/local/bin/duplicity", line 569, in restore
>         restore_get_patched_rop_iter(col_stats)):
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 521, in Write_ROPaths
>         for ropath in rop_iter:
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 493, in integrate_patch_iters
>         for patch_seq in collated:
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 378, in yield_tuples
>         setrorps( overflow, elems )
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 367, in setrorps
>         elems[i] = iter_list[i].next()
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 112, in difftar2path_iter
>         tarinfo_list = [tar_iter.next()]
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 328, in next
>         self.set_tarfile()
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/patchdir.py",
> line 322, in set_tarfile
>         self.current_fp = self.fileobj_iter.next()
>       File "/usr/local/bin/duplicity", line 606, in get_fileobj_iter
>         manifest.volume_info_dict[vol_num])
>       File "/usr/local/bin/duplicity", line 630, in restore_get_enc_fileobj
>         fileobj = tdp.filtered_open_with_delete("rb")
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/dup_temp.py",
> line 114, in filtered_open_with_delete
>         fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/path.py",
> line 741, in filtered_open
>         return gpg.GPGFile(False, self, gpg_profile)
>       File "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/gpg.py",
> line 152, in __init__
>         'logger': self.logger_fp})
>       File 
> "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/GnuPGInterface.py",
> line 357, in run
>         create_fhs, attach_fhs)
>       File 
> "/usr/local/Cellar/duplicity/0.6.14/libexec/duplicity/GnuPGInterface.py",
> line 399, in _attach_fork_exec
>         process.pid = os.fork()
>     OSError: [Errno 35] Resource temporarily unavailable
> 
> (Please find the complete verbosity 9 log attached.)
> 
> Both the backup location and restore directory are on the same local
> (USB) drive, which has
> been fine when I checked another backup with it just yesterday.
> 
> I was using Duplicity 0.6.13, but upgraded to 0.6.14, and the same
> error is produced.
> 
> If anyone can offer any thoughts as to what the issue is, I'd be very 
> grateful.
> 
> 
> Thanks,
> 
> Chris Poole
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk



reply via email to

[Prev in Thread] Current Thread [Next in Thread]