:: Re: [Libbitcoin] obworker uses up a…
Pàgina inicial
Delete this message
Reply to this message
Autor: Amir Taaki
Data:  
A: libbitcoin
Assumpte: Re: [Libbitcoin] obworker uses up all memory and crashes [WAS: Re: New releases for libbitcoin/Obelisk/sx]
Are you running an HDD or SSD? If it's an HDD and the write throughput
is low that blocks are not being indexed/written fast enough, then the
memory buffer is filling up as new blocks are queued in the database.

The only way to resolve that (if it's the problem) is by a) making pure
writes faster or b) indexing less data (not a fan of this) [note: not
pruning but just not indexing].

------------

Can you update from the Git repo, and enable this new switch in your
config file:

https://github.com/spesmilo/obelisk/blob/master/src/worker/worker.cfg#L32

log_requests = true

Clear your log files, then run the daemon.

$ grep request debug.log

will give you some idea of the requests being run on the daemon.

On 07/01/14 18:37, Noel Maersk wrote:
> On 06/01/14 16:33, Noel Maersk wrote:
>> Around new year I started catching a sporadic segfault from
>> obworker. I didn't save the backtraces (that's what drunkedness does
>> :/), and can't determine what triggers it and how to reproduce (yet).
>>
>> If this isn't the VPS admin being naughty, or some invisible quota
>> limit, then this bug made it into the release.
>>
>> Will get back when there's more info.
>
> 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?
>
> OK, found it.
>
> After running for some time (hours), obworker takes up all memory and
> gets terminated.
>
> There are sometimes streaks of these:
>
>> ...
>> ERROR [poller]: Storing block
>> 000000000000001e4a1dba552d7a60d5dc649185d04521c9f5516a270f1bb7f8:
>> Matching previous object found
>> ...
>
> (the block hash is different, it's not just one block)
>
> Might be related to the same hard disk write bottleneck, but maybe not.
>
> The server is limited to 2 GiB of RAM.
>
> All versions are latest git, OS is Debian Wheezy, ZeroMQ version 3
> (current Debian stable default).
>
> VPS log shows this started around midnight of December 24.
>
>
>
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>