Quote from: casadebitcoin on December 15, 2013, 07:07:32 PM

Quote from: gweedo on December 15, 2013, 02:17:35 AM

Quote from: casadebitcoin on December 15, 2013, 02:05:13 AM

Quote from: gweedo on December 13, 2013, 05:57:03 PM

Quote from: yenom on December 13, 2013, 05:44:06 PM

Little tip, start it with

Code:

screen bitcoind

You can then exit the session and leave it running.

Code:

nohup

is probably the better command.

As a relative N00B does "bitcoind daemon" achive similar to nohup? I just setup bitcoind and am noticing that once I loose my SSH the bitcoind stops.

So I just started with cranking up bitcoind daemon but am not 100% sure if it keeps chugging after I close SSH.

If nohup is the way to go is the command nohup bitcoind or bitcoind nohup or drill into some directory - fyi I have bitcoind running at root since I dont use this VPS or this bitcoind for anything other than helping out seeding....

Yes you have to include the full path to where your bitcoind bin is located, unless you are already in that directory.

O.K., Cool - in root I run bitcoind -nohup and get "Bitcoin server starting.

Things run well for about 10-15 mins, (can get info from bitcoind getinfo, etc) then after about 15mins or so I get "error: couldn't connect to server"

I've also tried just running bitcoind and screen bitcoind and bitcoind -nohup - They all crank up bitcoind for about 15mins then the bitcoind server seems to die...

Any ideas thoughts on how to trouble shoot? (FYI - VPS, with bitcoind in root)

Here run

Code:

nohup &