Re: Db::open/Db::close "Bad file descriptor" exception

Private email with Martti Malmi (sirius-m) · 4 messages · from 16 November 2009 · with Satoshi Nakamoto, mmalmi@cc.hut.fi

Read in Satoshi Mail Archive source

Satoshi Nakamoto to Liberty Standard <newlibertystandard@gmail.com> · 16 November 2009, 06:20 UTC · original

I have an idea for a workaround, but it depends on what files the errors are on. If you've accumulated several errors in db.log, could you send it to me? (even if it's rather simple and boring) Is the file listed always blkindex.dat, or does it include addr.dat or wallet.dat too?

Liberty Standard wrote:
I moved the data directory back to my SSD card and started bitcoin test 6. It encountered a segmentation fault today with Db::open in the log. I had changed the settings to only use one processor/core while I watched a 720p mkv movie. I noticed the segmentation fault after the film had ended. On Sun, Nov 15, 2009 at 12:45 AM, Satoshi Nakamoto <satoshin@gmx.com <mailto:satoshin@gmx.com>> wrote: Here's one where I linked Berkeley DB a different way. It's worth a try. Otherwise identical to test5. (Keep the datadir on the hard drive at least until you get it to fail the same way there. That has a fair chance of success.)

mmalmi@cc.hut.fi to Satoshi Nakamoto <satoshin@gmx.com> · 18 November 2009, 01:50 UTC · original

Here's the logs in case they're still useful.

I have an idea for a workaround, but it depends on what files the errors are on. If you've accumulated several errors in db.log, could you send it to me? (even if it's rather simple and boring) Is the file listed always blkindex.dat, or does it include addr.dat or wallet.dat too?

Satoshi Nakamoto to mmalmi@cc.hut.fi · 18 November 2009, 05:14 UTC · original

Thanks. The db::open/close errors confirm the pattern. More interesting is the zombie sockets activity towards the end, and the socket thread monitor tripped but didn't get it going again. Was the machine disconnected from the net? MSG_DONTWAIT in test5 solved the zombie problem for Liberty. What test version were you running? (I should print the test version in the log)

mmalmi@cc.hut.fi wrote:
Here's the logs in case they're still useful. > I have an idea for a workaround, but it depends on what files the > errors are on. If you've accumulated several errors in db.log, could > you send it to me? (even if it's rather simple and boring) Is the file > listed always blkindex.dat, or does it include addr.dat or wallet.dat > too?

mmalmi@cc.hut.fi to Satoshi Nakamoto <satoshin@gmx.com> · 18 November 2009, 19:32 UTC · original

I think it was test version 5, not completely sure though. I'm running the Linux version on a laptop which I move between different locations and use the hibernate-feature instead of powering down.

Thanks. The db::open/close errors confirm the pattern. More interesting is the zombie sockets activity towards the end, and the socket thread monitor tripped but didn't get it going again. Was the machine disconnected from the net? MSG_DONTWAIT in test5 solved the zombie problem for Liberty. What test version were you running? (I should print the test version in the log) mmalmi@cc.hut.fi wrote: > Here's the logs in case they're still useful. > >> I have an idea for a workaround, but it depends on what files the >> errors are on. If you've accumulated several errors in db.log, could >> you send it to me? (even if it's rather simple and boring) Is the file >> listed always blkindex.dat, or does it include addr.dat or wallet.dat >> too? >