On Fri, Jan 09, 2009 at 10:58:45AM -0800, Matthias Brantner wrote:
> I'm developing a C++ library (libaws) on top of libcurl for interfacing
> with the Amazon Web Services. With this library, I created a fuse-based
> file system for S3. It seems to work quite well. However, after doing a
> few hundred requests, libcurl suddenly starts to return the error code 6
> (CURLE_COULDNT_RESOLVE_HOST).
>
> I'm running Ubuntu 8.10 having libcurl4 installed. In order to make sure
> that I didn't do any obvious mistakes, I ran the file system with
> valgrind. The first warnings and error valgrind reports are the
> following:
>
> ==6168== Warning: invalid file descriptor 1019 in syscall socket()
> ==6168== Warning: invalid file descriptor 1019 in syscall socket()
> ==6168== Warning: invalid file descriptor 1019 in syscall open()
> ==6168== Warning: invalid file descriptor 1019 in syscall open()
> ==6168== Warning: invalid file descriptor 1019 in syscall socket()
> ==6168== Warning: invalid file descriptor 1019 in syscall socket()
> ==6168== Warning: invalid file descriptor 1019 in syscall open()
> ==6168== Warning: invalid file descriptor 1019 in syscall open()

Could it be that there are too many open sockets at once? Are you opening
a new easy handle for each transfer or reusing only a small pool of them?
Do things change if you enable/disable nscd?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved