bitcoind json rpc getting stuck sometimes

[btc_enigma]

Hi,

Sometimes bitcoind json rpc just gets stuck and don't respond to bitcoind getinfo calls.
When I see .bitcoin/debug I can see that bitcoind is still running and processing blocks correctly

2014-12-25 13:25:20 UpdateTip: new best=00000000000000002f83c6701e80513909ca76e56d0cece11574d0ec1dbe4750  height=301076  log2_work=78.627149  tx=38896050  date=2014-05-16 18:36:59 progress=0.519573
2014-12-25 13:25:21 UpdateTip: new best=0000000000000000633634f6829720785451ee93ece1610f0df0d4baba7a052a  height=301077  log2_work=78.627267  tx=38896879  date=2014-05-16 18:41:10 progress=0.519591
2014-12-25 13:25:22 Pre-allocating up to position 0xd00000 in rev00140.dat
2014-12-25 13:25:22 UpdateTip: new best=00000000000000006a55f80015b6f96fd80e79672ed842b8f722d1ec1b0545c7  height=301078  log2_work=78.627384  tx=38897472  date=2014-05-16 18:48:36 progress=0.519607

I am using bitcoind 90100. What is the best way to fix this, instead to kill and restarting bitcoind ? I am facing this every few days

[1715031887]

1715031887

[1715031887]

1715031887

[1715031887]

1715031887

[bitsta]

Hi,

Sometimes bitcoind json rpc just gets stuck and don't respond to bitcoind getinfo calls.
When I see .bitcoin/debug I can see that bitcoind is still running and processing blocks correctly

2014-12-25 13:25:20 UpdateTip: new best=00000000000000002f83c6701e80513909ca76e56d0cece11574d0ec1dbe4750  height=301076  log2_work=78.627149  tx=38896050  date=2014-05-16 18:36:59 progress=0.519573
2014-12-25 13:25:21 UpdateTip: new best=0000000000000000633634f6829720785451ee93ece1610f0df0d4baba7a052a  height=301077  log2_work=78.627267  tx=38896879  date=2014-05-16 18:41:10 progress=0.519591
2014-12-25 13:25:22 Pre-allocating up to position 0xd00000 in rev00140.dat
2014-12-25 13:25:22 UpdateTip: new best=00000000000000006a55f80015b6f96fd80e79672ed842b8f722d1ec1b0545c7  height=301078  log2_work=78.627384  tx=38897472  date=2014-05-16 18:48:36 progress=0.519607

I am using bitcoind 90100. What is the best way to fix this, instead to kill and restarting bitcoind ? I am facing this every few days

are you running the daemon on a vps?

[shorena]

-snip-
are you running the daemon on a vps?

I have similar issues and I suspect its because I run it on a VPS.

[bitsta]

-snip-
are you running the daemon on a vps?

I have similar issues and I suspect its because I run it on a VPS.

yes correctly, thats why i was asking him.

@shorena: can you post something about the config you were using @VPS (OS, RAM, CPU, HDD).
just out of curiosity: did you have this issue on ubuntu?

[shorena]

-snip-
are you running the daemon on a vps?

I have similar issues and I suspect its because I run it on a VPS.

yes correctly, thats why i was asking him.

@shorena: can you post something about the config you were using @VPS (OS, RAM, CPU, HDD).
just out of curiosity: did you have this issue on ubuntu?

Yes its Ubuntu 14.04.1 LTS, with 2GB Ram, single core CPU and 50 GiB SSD. I have no idea which SSD/CPU they use and the ISP changed the offer by now. Its a deal I only got because I study IT/SC at my university. We theyd charge me the regular amount Id be well known to their support by now.

The picture below shows nicely how sometimes the shellscript gethering data from bitcoin core does not finish within 30 seconds. The white spots are unknown values / no data which occure when the script can not finish to feed the database. I thought about giving it more time as it runs every minute, but I dont think it should run that long. I never had this issue on any other machine, but every other machine is also a bare metal one and is not running 24/7 (yet), thus I suspect its because I have a cheap VPS any my priority on the machine is very low.

[btc_enigma]

-snip-
are you running the daemon on a vps?

I have similar issues and I suspect its because I run it on a VPS.

Yes, I am running on VPS
Ubuntu 13.10, 2G RAM

Update, now I have upgraded to bitcond 90300 , this seems to have fixed the issue. Didn't see any hangs for last three days. CPU usage also low