EagleTM

I'm seeing the same issue here: server with 4 GB RAM and 4 GB swap dies after around a week of running, with caches at half the size of the...

We're investigating the issue. Thomas' server is using less than 2 gigs of RES RAM, while I'm at 11 gig. It might be the plyvel verison. I've updated to 0.9...

Sorry, no progress here currently. The RAM recommendations still stand. I've put them into the HOWTO for now

We could check for output of the 2nd ever transaction: bitcoind getrawtransaction 0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098 1 if it returns error: {"code":-5,"message":"No information available about transaction"} there is pruning happening at bitcoind level....

A better tx is f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 in block 170 because it's actually spent If bitcoind getrawtransaction f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 0 170 returns raw output there is no pruning active and the patch to...

It seems to work well on a voluntary basis in the server banner. The verison info can actually be retrieved from bitcoin-core with a cli call: https://www.reddit.com/r/Bitcoin/comments/3c305f/if_you_are_using_any_wallet_other_than_bitcoin/cstt2vb Not sure what...

newer versions of bitcoin core (0.13.x) require libdb+ it seems, not sure what's wrong with having bdb 5+.

How recent is the codebase you're running and how much RAM do you have in the server and free to use for electrum server? It might be related to #126...

However I have at least one other server operator who runs with 16 gig and 512 MB swap and runs into this issue. I think it's one possible side effect...

OK it's independent of the RAM thing after all. It seems under some circumstances the ssl thread dies - pretty early after starting up it seems - while tcp and...