On Tue, Jan 07, 2014 at 12:09:51PM +0000, Amir Taaki wrote:
> What kind of load are you running against it? Is there some periodic
> activity that can trigger the behaviour?

Just receiving the blockchain.

Basically no user load (probably just me using sx).

It exits like this (run in GDB):

> ... (many similar messages about new and old blocks) ...
> INFO [poller]: Block #252555 00000000000000446e2d3a260ce1ab89428e49a09e21db55b513c424ba377d2b
> INFO [poller]: Block #252557 00000000000000388b38aeac8459bcf4a901dc1d318b83801d4941441003a494
> INFO [poller]: Block #252558 00000000000000149ea3f2c23e1576b8cd6421c3e48085d2afc7d0ae886a56b1
> ERROR [poller]: Storing block 00000000000000188327880fe9b6be184f935db3010ae5d96a1a6af165fd42ed: Matching previous object found
> INFO [poller]: Block #252559 000000000000002a521a4a6cceb6903b34f04367e2343ab3f97cb18810587f12
> INFO [poller]: Block #252560 000000000000004eb87fade1bcc0783b6a45d5002a774f1b63c8822eff29f91a
> [Thread 0x7fffe6c4f700 (LWP 13102) exited]
> ... (13 more threads exited) ...
>
> Program terminated with signal SIGKILL, Killed.
> The program no longer exists.
> (gdb) backtrace
> No stack.

Same happens when run outside of GDB.

Chances are, this is just a VPS issue. If no one else sees this happen,
we probably shouldn't bother (yet).