Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: miernik on August 08, 2011, 01:28:31 PM



Title: error: no response from server
Post by: miernik on August 08, 2011, 01:28:31 PM
I use the command-line client on Debian. Version 0.3.24

By mistake I typed:

bitcoind getaccountaddress 1FQGAxWNrtcbVTHSgfADPBcpnpc4CyXwQp

but the command didn't finish for too long (no output, just hanged), so I pressed Ctrl-C.

Now any command I try to run, hangs, I can press Ctrl-C. For example:

$ bitcoind getbalance
^Cerror: no response from server
$

Even "bitcoind help" does this.

Is this a known issue? Is this a bug? Why did it hang everything? I suspect I am not the first person who run "bitcoind getaccountaddress" with the address as argument instead of the account name.

What should I do? kill -9 the bitcoind process or what?


Title: Re: error: no response from server
Post by: jackjack on August 08, 2011, 02:04:47 PM
You killed bitcoind, run it again
I mean the first bitcoind, the one without arguments


Title: Re: error: no response from server
Post by: miernik on August 08, 2011, 02:15:19 PM
Well, but its running all the time:

$ ps x | grep bitcoind
 5840 ?        Ssl  9448:30 /usr/lib/bitcoin/bitcoind -daemon
23362 pts/13   S+     0:00 grep bitcoind
$




Title: Re: error: no response from server
Post by: jackjack on August 08, 2011, 03:13:59 PM
Strange...
Kill and run it again, it must be enough


Title: Re: error: no response from server
Post by: miernik on August 08, 2011, 10:44:02 PM
But my Internet connection was OK all the time. This happened because I ran "bitcoind getaccountaddress 1FQGAxWNrtcbVTHSgfADPBcpnpc4CyXwQp".

OK, now I did kill -9 to the daemon (normal kill was not enough), and started it again with "bitcoind -daemon".


Title: Re: error: no response from server
Post by: Furyan on August 08, 2011, 11:20:34 PM
This is the classic single-threaded RPC problem.  For whatever reason your first request hung the server because you're using the standard Bitcoin distrubution downloadable at bitcoin.org.  There's an unsupported fork that multithreads the RPC to avoid exactly this problem (among others).

The server stayed hung even after you hit CTRL-C.

You'll probably never know why the first request hung your bitcoin server.