Bitcoin Forum
May 08, 2024, 08:44:40 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Help, I started "bitcoind -daemon -keypool=10000 &" and its 18 hours already...  (Read 4258 times)
miernik (OP)
Sr. Member
****
Offline Offline

Activity: 334
Merit: 250


View Profile WWW
May 15, 2012, 04:19:58 AM
 #1

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?

1715157880
Hero Member
*
Offline Offline

Posts: 1715157880

View Profile Personal Message (Offline)

Ignore
1715157880
Reply with quote  #2

1715157880
Report to moderator
1715157880
Hero Member
*
Offline Offline

Posts: 1715157880

View Profile Personal Message (Offline)

Ignore
1715157880
Reply with quote  #2

1715157880
Report to moderator
1715157880
Hero Member
*
Offline Offline

Posts: 1715157880

View Profile Personal Message (Offline)

Ignore
1715157880
Reply with quote  #2

1715157880
Report to moderator
In order to achieve higher forum ranks, you need both activity points and merit points.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715157880
Hero Member
*
Offline Offline

Posts: 1715157880

View Profile Personal Message (Offline)

Ignore
1715157880
Reply with quote  #2

1715157880
Report to moderator
1715157880
Hero Member
*
Offline Offline

Posts: 1715157880

View Profile Personal Message (Offline)

Ignore
1715157880
Reply with quote  #2

1715157880
Report to moderator
payb.tc
Hero Member
*****
Offline Offline

Activity: 812
Merit: 1000



View Profile
May 15, 2012, 04:43:39 AM
 #2

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 (OP)
Sr. Member
****
Offline Offline

Activity: 334
Merit: 250


View Profile WWW
May 15, 2012, 05:09:19 AM
 #3

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.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!