Ubuntu bitcoind Error: No Response from Server

[bigbeninlondon]

So I decided to go ahead and put up a bitcoin full node on a recently repurposed machine.  I installed bitcoind and ran the daemon using

Code:

sudo bitcoind -daemon

.  The debug.log shows it is syncing the block chain.  When I try to issue a command like

Code:

bitcoind getinfo

it responds with

Code:

error: no response from server

I have the bitcoin.conf file set with an rpcuser and rpcpassword, but I'm running the commands from the same machine so I shouldn't need rpc authentication, right?  Additionally even if it did need rpc authentication, I should still get SOME kind of response, right? What am I missing here?

[RedDiamond]

Maybe you need to open some ports in firewall. Please see this installation script
https://raw.github.com/XertroV/BitcoinAutoNode/master/bitcoinAutoNode.sh

[bigbeninlondon]

ufw not previously installed, so no help there.  I noticed the bitcoin.conf from the script was having the following lines added:

Code:

echo "server=1" > $config
echo "daemon=1" >> $config
echo "connections=40" >> $config

I added those, restarted bitcoind and still no luck...

[cr1776]

ufw not previously installed, so no help there.  I noticed the bitcoin.conf from the script was having the following lines added:

Code:

echo "server=1" > $config
echo "daemon=1" >> $config
echo "connections=40" >> $config

I added those, restarted bitcoind and still no luck...

Can you kill and restart bitcoind?

Is your local interface up? (E.g. ifconfig lo up)

Did you just start it on this machine? Iirc, sometime when it is just coming up it takes some time to respond.

[bigbeninlondon]

Code:

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:42104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42104 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12639748 (12.6 MB)  TX bytes:12639748 (12.6 MB)

It's up...

I've let bitcoind sit for over an hour now.  Also, it appears to be syncing the blockchain just fine when I query the debug.log so it appears to be running just fine.

[Shahrukh]

By the error "No response from server" it means no response from bitcoin daemon. Try stopping the daemon by bitcoind stop and after 30 seconds start it again by bitcoind see if the server is taking time to start as well ? If yes then you should stop some other process to free some RAM

[Shahrukh]

By the error "No response from server" it means no response from bitcoin daemon. Try stopping the daemon by bitcoind stop and after 30 seconds start it again by bitcoind see if the server is taking time to start as well ? If yes then you should stop some other process to free some RAM

[cr1776]

Assuming you tried killing it and restarting...Can you netstat to make sure bitcoind is listening on the correct port? (Or telnet?)

[bigbeninlondon]

What port should it be listening on for local connections?

[Shahrukh]

What port should it be listening on for local connections?

8333

[bigbeninlondon]

What port should it be listening on for local connections?

8333

Yup, it's there

Code:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0     0         *:8333                    *:*                         LISTEN     root       14141894  7755/bitcoind

[bigbeninlondon]

Could it have something to do with permissions?  I run the daemon with "sudo", and I'm doing it from a remote terminal since the machine is headless.  I'm at a loss.

[bigbeninlondon]

Here's a copy of my debug.log file after starting with -debug -debugnet:

Code:

2014-02-16 02:17:54 Opening LevelDB in /home/ben/.bitcoin/blocks/index
2014-02-16 02:17:54 Opened LevelDB successfully
2014-02-16 02:17:54 Opening LevelDB in /home/ben/.bitcoin/chainstate
2014-02-16 02:17:54 Opened LevelDB successfully
2014-02-16 02:17:58 LoadBlockIndexDB(): last block file = 115
2014-02-16 02:17:58 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=428, size=84657946, heights=285672...286099, time=2014-02-13...2014-02-16)
2014-02-16 02:17:58 LoadBlockIndexDB(): transaction index disabled
2014-02-16 02:17:58 LoadBlockIndexDB(): hashBestChain=00000000000000006d8af9e14bfc0184efb9641454794b272a13233d7da76b41  height=286099 date=2014-02-16 02:17:19
2014-02-16 02:17:58 init message: Verifying blocks...
2014-02-16 02:17:58 Verifying last 288 blocks at level 3
2014-02-16 02:18:06 No coin database inconsistencies in last 136 blocks (40342 transactions)
2014-02-16 02:18:07  block index           12647ms
2014-02-16 02:18:07 init message: Loading wallet...
2014-02-16 02:18:07 nFileVersion = 80600
2014-02-16 02:18:07  wallet                  460ms
2014-02-16 02:18:07 init message: Loading addresses...
2014-02-16 02:18:07 Loaded 9493 addresses from peers.dat  26ms
2014-02-16 02:18:07 mapBlockIndex.size() = 286100
2014-02-16 02:18:07 nBestHeight = 286099
2014-02-16 02:18:07 setKeyPool.size() = 100
2014-02-16 02:18:07 mapWallet.size() = 0
2014-02-16 02:18:07 mapAddressBook.size() = 1
2014-02-16 02:18:07 dnsseed thread start
2014-02-16 02:18:07 Loading addresses from DNS seeds (could take a while)
2014-02-16 02:18:07 addcon thread start
2014-02-16 02:18:07 net thread start
2014-02-16 02:18:07 opencon thread start
2014-02-16 02:18:07 init message: Done loading
2014-02-16 02:18:07 msghand thread start
2014-02-16 02:18:07 dumpaddr thread start
2014-02-16 02:18:07 Added 24 addresses from 178.18.90.41: 8 tried, 9499 new
2014-02-16 02:18:07 GetMyExternalIP() received [XX.XXX.X.XXX] XX.XXX.X.XXX:0
2014-02-16 02:18:07 GetMyExternalIP() returned XX.XXX.X.XXX
2014-02-16 02:18:07 AddLocal(XX.XXX.X.XXX:8333,4)
2014-02-16 02:18:07 Added 7 addresses from ::: 8 tried, 9499 new
2014-02-16 02:18:08 trying connection 75.66.129.109:8333 lastseen=4.3hrs
2014-02-16 02:18:08 Added 20 addresses from 192.3.11.20: 8 tried, 9512 new
2014-02-16 02:18:08 Added 7 addresses from ::: 8 tried, 9513 new
2014-02-16 02:18:08 94 addresses found from DNS seeds
2014-02-16 02:18:08 dnsseed thread exit
2014-02-16 02:18:13 connection timeout
2014-02-16 02:18:13 trying connection 82.243.97.138:8333 lastseen=4.9hrs
2014-02-16 02:18:18 connection timeout
2014-02-16 02:18:19 trying connection 90.201.55.96:8333 lastseen=5.4hrs

Anything here?

[bigbeninlondon]

I figured out my answer.  I had the mining proxy for a Block Erupter running and listening on 8332.  Ugh, now my mining proxy isn't working.  Gotta love it.

[grifferz]

What port should it be listening on for local connections?

8333

Yup, it's there

Code:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode       PID/Program name
tcp        0     0         *:8333                    *:*                         LISTEN     root       14141894  7755/bitcoind

By running bitcoind on the command line are you not trying to talk JSON-RPC to the listener, not bitcoin protocol?

It listens on a different port for RPC, as set by the rpcport option. Your output only has one listening port so I do not think you have enabled RPC. Have you set rpcuser, rpcpassword and rpcport?

FWIW for me:

Code:

$ sudo lsof -p 11819 | grep LISTEN
bitcoind 11819 bitcoind    6u  IPv6 xxxxxx20       0t0    TCP *:8333 (LISTEN)
bitcoind 11819 bitcoind    7u  IPv4 xxxxxx21       0t0    TCP *:8333 (LISTEN)
bitcoind 11819 bitcoind  105u  IPv4 xxxxxx50       0t0    TCP localhost:8332 (LISTEN)
bitcoind 11819 bitcoind  109u  IPv6 xxxxxx48       0t0    TCP localhost:8332 (LISTEN)