Help, I started "bitcoind -daemon -keypool=10000 &" and its 18 hours already...

miernik

sr. member

Activity: 334

Merit: 250

In the end it had nothing to do with keypool=10000. For some unknown reason my local interface was down. I fixed it with:

Code:

ifconfig lo up

I killed the bitcoin daemon with kill $PID, started it again and within a minute I could do bitcoind getbalance.

payb.tc

hero member

Activity: 812

Merit: 1000

Quote from: miernik on May 15, 2012, 12:19:58 AM

Can I safely kill the bitcoind?
With which signal?

if you've properly backed up your wallet and bitcoind stop doesn't work, then kill -9

if you haven't properly backed up your wallet and bitcoind stop doesn't work, then i'd suggest waiting another 18 hours first before doing anything.

it looks like there are a few people having issues with the latest version.

miernik

sr. member

Activity: 334

Merit: 250

Before I had keypool=1000 and everything was fine.

Now I started the daemon with:

Code:

bitcoind -daemon -keypool=10000 &

and it's been 18 hours and I still can't connect to it. When I try:

Code:

bitcoind getbalance

I get:

Code:

error: couldn't connect to server

It's version 0.6.2.2 from latest Debian sid package (0.6.2.2-1).

Also when I try to connect to a locally (on the same machine) run webserver I get a timeout:

Code:

$ telnet 192.168.178.35 8000
Trying 192.168.178.35...
telnet: Unable to connect to remote host: Connection timed out

I posted the last 200 lines from ~/.bitcoin/debug.log at http://dpaste.com/748342/plain/ in case it helps:
http://dpaste.com/748342/plain/

This is insane, its 18 hours already, what's going on?
How can I safely stop this madness?
Can I safely kill the bitcoind?
With which signal?

Topic: Help, I started "bitcoind -daemon -keypool=10000 &" and its 18 hours already... (Read 4259 times)