Quote from: spiccioli on June 04, 2014, 09:05:37 PM

Quote from: andmax on June 04, 2014, 08:36:53 PM

Quote from: spiccioli on June 04, 2014, 08:33:35 PM

Quote from: andmax on June 04, 2014, 08:27:00 PM

Quote from: jonnybravo0311 on June 04, 2014, 01:29:54 PM

Quote from: andmax on June 04, 2014, 11:22:35 AM

Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot.

andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333
2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty)
2014-06-04 04:53:52.347840
2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'xxxxxxx'...
2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection:
2014-06-04 04:53:52.349666 > Traceback (most recent call last):
2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.
2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection:
2014-06-04 04:53:53.351698 > Traceback (most recent call last):
2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused

You have any restrictions on the number of connections allowed to your bitcoind process? Did you try stopping/restarting bitcoind? Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)? Can you telnet into that IP/port successfully?

Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now.

andmax,

are the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ?

spiccioli

Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into.

and server=1 ? do you have it inside bitcoin.conf?

and rpcallowip=? do you have it/what value has it?

as you can see I'm thinking about a misconfiguration between bitcoind and p2pool.

maybe it is something else entirely.

spiccioli

A couple more questions...

When you reinstalled your BTC node, did you build it from source, or install a pre-built package from somewhere? Did you make sure that wherever you installed it, it has permissions to read from the directory in which the .conf file resides? Did you double/triple/quadruple check all of your settings in the .conf file, and ensure that all permissions are set properly? Did the Ubuntu upgrade cause any of the dependent packages to break/malfunction? Did you upgrade all of your installed packages after you did the base Ubuntu upgrade?