回复：Linux 更新

引用 Martti Malmi 的文字Martti Malmi来源 ↗

程序终止了几次，debug.log 里都是来自 Db::close 的同一个错误。Db.log 中有：

The program terminated a few times with the same error in debug.log from Db::close. Db.log has:

close: Bad file descriptor blkindex.dat: Bad file descriptor

close: Bad file descriptor blkindex.dat: Bad file descriptor

我运行的是 64 位 Ubuntu 发行版。

I'm running a 64-bit Ubuntu distribution.

引用中本聪此前的文字中本聪来源 ↗

现在唯一的问题是他遇到的 DB 异常。

The only problem now is the DB exceptions he's getting.

---

---

EXCEPTION: 11DbException Db::open: Bad file descriptor bitcoin in ThreadMessageHandler()

EXCEPTION: 11DbException Db::open: Bad file descriptor bitcoin in ThreadMessageHandler()

---

---

EXCEPTION: 11DbException Db::close: Bad file descriptor bitcoin in ThreadMessageHandler()

EXCEPTION: 11DbException Db::close: Bad file descriptor bitcoin in ThreadMessageHandler()

我原本以为那些是 Wine 的问题，但他在 Linux 上照样遇到了。他试过把 datadir 移到另一个驱动器，没有用。我从没遇到过。我正在运行一项压力测试，连续产生大量活动和数据库访问，也从没出现过。

I had expected those to be a Wine problem, but he's getting them on Linux just the same. He tried moving the datadir to a different drive, no help. I've never gotten them. I'm running a stress test that continuously generates a lot of activity and DB access and never got it.

他用 Ubuntu 64 位，我用 32 位，所以我假设区别就在这里。你的 Linux 机器是 64 位还是 32 位？你有没有遇到过 DB 异常？（也看看 db.log。）既然 test5 已经修复了僵尸问题，你能开始在自己的 Linux 机器上运行它吗？我们可以用第三个样本，更清楚地了解现在面对的情况。 DB 异常没有被捕获，所以遇到时会使程序停止。

He has Ubuntu 64-bit and I have 32-bit, so I'm assuming that's the difference. Is your Linux machine 64-bit or 32-bit? Have you ever had a DB exception? (see db.log also) Now that the zombie problem is fixed in test5, could you start running it on your Linux machine? We could use a 3rd vote to get a better idea of what we're dealing with here. The DB exception is uncaught, so it'll stop the program if you get it.

顺便说一句，zetaboards 坚持显示“会员编号”，所以你最好尽快注册，抢一个好账号数字。

BTW, zetaboards insists on displaying "Member #", so you better sign up soon and grab a good account number.