Bitcoin Forum
December 04, 2016, 04:16:44 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: error: no response from server  (Read 2424 times)
miernik
Sr. Member
****
Offline Offline

Activity: 334


View Profile WWW
August 08, 2011, 01:28:31 PM
 #1

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?

1480825004
Hero Member
*
Offline Offline

Posts: 1480825004

View Profile Personal Message (Offline)

Ignore
1480825004
Reply with quote  #2

1480825004
Report to moderator
1480825004
Hero Member
*
Offline Offline

Posts: 1480825004

View Profile Personal Message (Offline)

Ignore
1480825004
Reply with quote  #2

1480825004
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
jackjack
Hero Member
*****
Offline Offline

Activity: 868


May Bitcoin be touched by his Noodly Appendage


View Profile
August 08, 2011, 02:04:47 PM
 #2

You killed bitcoind, run it again
I mean the first bitcoind, the one without arguments

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
miernik
Sr. Member
****
Offline Offline

Activity: 334


View Profile WWW
August 08, 2011, 02:15:19 PM
 #3

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
$



jackjack
Hero Member
*****
Offline Offline

Activity: 868


May Bitcoin be touched by his Noodly Appendage


View Profile
August 08, 2011, 03:13:59 PM
 #4

Strange...
Kill and run it again, it must be enough

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
Ukigo
Hero Member
*****
Offline Offline

Activity: 924


View Profile
August 08, 2011, 04:29:00 PM
 #5

I experience somewhat similar problems.

i have found out , that to start first bitcoind properly  i need to be connected to the Internet BEFORE.
after 1st daemon have started "bitcoind getinfo" works Ok.
And then Internet connection may be terminated by me if needed, without affecting 1st bitcoind.

It's strange feature, probably a bug.

"...Enemies are everywhere ! Angka is all rage ! Be a good soldiers, blow everything... " <-- Pol Pot (C)
miernik
Sr. Member
****
Offline Offline

Activity: 334


View Profile WWW
August 08, 2011, 10:44:02 PM
 #6

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".

Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
August 08, 2011, 11:20:34 PM
 #7

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.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!