Cannot stop bitcoind 0.9.0

[jlp]

I installed and started bitcoind 0.9.0 64 bit on Linux.  I ran the following on Linxu:

$ sudo bitcoind stop
Bitcoin server stopping

When I run:

$ pstree

bitcoind is no longer showing.  However, when I run:

$ top

bitcoind is still running, using between 140 to 150 MB of RAM.

I ran "sudo bitcoind stop" a couple of times, but bitcoind still shows up on "top".  I don't want to "kill" the process because I read that this might corrupt the database.

When I run the following:

$ bitcoind -daemon

I get the following, which seems to confirm that bitcoind is still running:

: Cannot obtain a lock on data directory /home/user/.bitcoin. Bitcoin is probably already running.

How do I stop bitcoind?

(When bitcoind was running before I tried to stop it, it was using 550 to 680 MB of RAM.  Is this normal?)

[roslinpl]

hmm interesting...

It might be some little bug or I don't yet know...

You're under Fedora?

[jlp]

I had bitcoind 0.8.6, so I had already downloaded the blockchain.  Is it possible that when I started using bitcoind 0.9.0, something was incompatible from 0.8.6?

I just rebooted and bitcoind is still showing on "top".

In the past, I have rebooted without stopping bitcoind first.  Does this corrupt the database?  Can this be the reason that I cannot stop it now?

I just tried the following:

$ bitcoin-cli stop

and now it seems to have stopped.  bitcoind is no longer showing on "top".

I just tried the following:

$ bitcoind
Bitcoin server starting
$ bitcoind stop
Bitcoin server stopping

...and bitcoind is not showing on "top".

[DeathAndTaxes]

AFAIK starting in v0.9 the RPC client has been separated out.  So to send RPC command to bitcoind using the command line the bitcoin-cli is used.  

Code:

bitcoin-cli <command>

That would include stop.  Not sure how/why

Code:

bitcoind stop

does anything (shouldn't it be bitcoin-cli stop)?  
On edit: it looks like the stop all RPC calls can be made from bitcoind (no idea why?).

Bitcoin-cli
-------------

Another change in the 0.9 release is moving away from the bitcoind executable
functioning both as a server and as a RPC client. The RPC client functionality
("tell the running bitcoin daemon to do THIS") was split into a separate
executable, 'bitcoin-cli'. The RPC client code will eventually be removed from
bitcoind, but will be kept for backwards compatibility for a release or two.

There should be no difference between bitcoind stop and bitcoin-cli stop at this point.  It looks like bitcoind failed stop cleanly on the first attempt.  Taking a look at debug.log might provide some insight.

There are no blockchain (forward) incompatibilities between v0.8.6 and v0.9.0.  If when starting bitcoind it is attempting to recreate the blockchain from the genesis block that would indicate some type of corruption.  Taking a look at debug.log might provide some insight.

[cp1]

It's also possible that you still have 0.86 installed in your path somewhere, since they now have two differently named programs to run.

[ninjarobot]

I have a similar issue running bitcoind on VPS (weloveservers.net)

bitcoind runs for a minute or 2 and then stops and becomes completely unresponsive.

from top:

Code:

404 root      20   0 1306m  59m  12m T    0  5.8   0:02.69 bitcoind

* bitcoind stop/start/getinfo/etc does nothing.
* process status = T (Traced or stopped)
* killing the process using 'kill' or 'pkill' does nothing. (EDIT: 'kill -SIGKILL 404' worked)
* debug.log does not show any warnings.
* I have 1GB RAM & 1.5 GB Swap so it should not be a memory issue.

Last 2 messages in debug.log are:

Code:

2014-06-21 23:20:20 ProcessBlock: ACCEPTED
2014-06-21 23:20:21 ProcessBlock: ORPHAN BLOCK 0, prev=00000000000000004003e37d09bc0b26c00e799bb661405cc6457174af68e147

version info:

Code:

root@cryptonode:~/.bitcoin# bitcoind getinfo
{
    "version" : 90100,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 64085,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 19.40479633,
    "testnet" : false,
    "keypoololdest" : 1403389725,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""

What could be causing this? (bug, VPS provider blocking bitcoind, etc)

[cp1]

Do you have enough disk space?

[ninjarobot]

Do you have enough disk space?

Yes, 30GB.

My node used to run fine for the last 6 weeks. Issues started a few days ago. I've reinstalled ubuntu server 12.04 LTS & bitcoind but the sudden stop issue persists.

I've contacted support and they responded:

We do not allow Bitcoin mining.

After explaining to the support guy that I'm not mining but running a transaction relay he said would pass it on to management.

EDIT: Moved to another VPS (http://cloudatcost.com/) that does not have issues. New node available here: http://fullnode.org/

EDIT2: Received a new response from weloveservers.net:

We are not killing any 'bitcoind' process or daemon on our side.