Pushpool - Tech Support

[davout]

they want todo there own

explain your problem better.

can you launch the bitcoin daemon ?
do you get a result when trying a command such as getinfo on the command line ?

if yes, your bitcoin daemon is set up correctly, take this info, copy it in pushpool config for "rpc.user" and "rpc.password"

this appears pretty clearly in the pushpool example config file

[1714508615]

1714508615

[1714508615]

1714508615

[1714508615]

1714508615

[Wayno]

Ok,

so far i can connect to the rpc via 8332 it starts working with the bitcoind password but it isnt using poolpushd

when i try the other ports.

port 8342
[1307118013.669588] client host ::ffffmyip port 55180 connected
Client Error: Problems communicating with bitcoin RPC

[1307117971.398973] Listening on host :: port 8341
[1307118053.782549] HTTP request failed: The requested URL returned error: 401
Client Error: upstream RPC error

[1307117971.399029] Listening on host :: port 8344
[1307118083.360229] HTTP request failed: The requested URL returned error: 401
Client Error: upstream RPC error

[1307117971.399089] Listening on host 110.173.226.41 port 8338
[1307118106.557565] client host MYIP port 55204 connected
Client Error: Problems communicating with bitcoin RPC

that is it

[davout]

Ok,

so far i can connect to the rpc via 8332 it starts working with the bitcoind password but it isnt using poolpushd

when i try the other ports.

port 8342
[1307118013.669588] client host ::ffffmyip port 55180 connected
Client Error: Problems communicating with bitcoin RPC

[1307117971.398973] Listening on host :: port 8341
[1307118053.782549] HTTP request failed: The requested URL returned error: 401
Client Error: upstream RPC error

[1307117971.399029] Listening on host :: port 8344
[1307118083.360229] HTTP request failed: The requested URL returned error: 401
Client Error: upstream RPC error

[1307117971.399089] Listening on host 110.173.226.41 port 8338
[1307118106.557565] client host MYIP port 55204 connected
Client Error: Problems communicating with bitcoin RPC

that is it

upstream rpc error = pushpool has trouble connecting to the bitcoin client
401 = wrong credentials

[Wayno]

then the question is where is the thing going wrong?

is there a way to tell that poolpushd is connecting to bitcoind?

[davout]

then the question is where is the thing going wrong?

is there a way to tell that poolpushd is connecting to bitcoind?

try to run pushpool with
$ pushpool --debug=2 --config=[your config file] --stderr --foreground

check your logs, normally /tmp/shares.log and /tmp/requests.log see if something funny appears

check your bitcoin client's debug.log to see if pushpool sends getwork requests

triple check your DB config

double check the filesystem permissions for the log files directory

if all of that fails direct your friends to an existing pool and erase system32 directory, it makes your computer faster

also post your pushpool config, bitcoin config and the command line used to run a remote miner, maybe there's something obvious here

[Wayno]

Code:

JSON protocol request:
{"method": "getwork", "params": [], "id":3}

* About to connect() to 127.0.0.1 port 8335 (#0)
*   Trying 127.0.0.1... * TCP_NODELAY set
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8335 (#0)
* Server auth using Basic with user 'coinz'
> POST / HTTP/1.1
Authorization: Basic Y29pbno6Y2lvbnoxMQ==
Host: 127.0.0.1:8335
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

* HTTP 1.0, assume close after body
< HTTP/1.0 401 Authorization Required
< Date: Fri, 03 Jun 2011 17:58:10 +0000
< Server: bitcoin-json-rpc/0.3.21-beta
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="jsonrpc"
< Content-Type: text/html
< Content-Length: 296
* The requested URL returned error: 401
* Closing connection #0
[1307123890.859317] HTTP request failed: The requested URL returned error: 401

Code:

{
   # network ports
   "listen" : [
      # binary protocol (default), port 8342
      #{ "port" : 8342 },

      # HTTP JSON-RPC protocol, port 8341
      { "port" : 8341, "protocol" : "http-json" },

      # HTTP JSON-RPC protocol, port 8344,
      #proxy is most likely your external ip address if your running a public pool | Public pools WON'T have the following ip addresses: (10.0.0.1, 127.0.0.1, 192.168.1.100, or 192.168.254.254,etc,etc)
      # requests to us | "proxy" should be set to your ip address that people will connect through
      { "port" : 8344, "protocol" : "http-json",
        "proxy" : "110.173.226.1" },

      # binary protocol, localhost-only port 8338
      # host is most likely your localhost address
      { "host" : "110.173.226.1", "port" : 8338, "protocol" : "binary" }
   ],

   # database settings
   "database" : {
      "engine" : "mysql",

      "host" : "localhost",

      "port" : 3306,

      #database name
      "name" : "pushpool",
      #database username
      "username" : "bitcoin",
      #database password
      "password" : "bitcoin11",
      #enable sharelog | to insert share data or sometimes known as "work"
      "sharelog" : true,
      "stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",
      
      "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

   },

   #uncoment this when you want to use memcached (Recommended for servers over 1.5gb of ram)
   # cache settings
   #"memcached" : {
   #   "servers" : [
   #      { "host" : "127.0.0.1", "port" : 11211 }
   #   ]
   #},

   "pid" : "/tmp/pushpoold.pid",

   # overrides local hostname detection
   "forcehost" : "localhost.localdomain",

   "log.requests" : "/tmp/request.log",
   "log.shares" : "/tmp/shares.log",

   # the server assumes longpolling (w/ SIGUSR1 called for each blk)
   "longpoll.disable" : false,

   # length of time to cache username/password credentials, in seconds
   "auth.cred_cache.expire" : 75,

   # RPC settings
   #Bitcoind Protocal settings
   #Host were bitcoind can be found on the network
   "rpc.url" : "http://127.0.0.1:8335/",
   #Username & password to connect to bitcoind
   "rpc.user" : "coinz",
   "rpc.pass" : "cionz11",

   # rewrite returned 'target' to difficulty-1?
   "rpc.target.rewrite" : true
}

Code:

rpcuser=coinz
rpcpassword=coinz11
rpcport=8335
server=1
gen=0
rpcallowip=*

Code:

./bitcoind -server -deamon
./pushpoold -E -F

[davout]

401 = wrong credentials

And because I'm nice I'll tell you the problem is in the pushpool config file

[Wayno]

omg thanks u 1 spelling mistake off :\

stupid me :\

[nzbtc]

So, still havent figured it out... I think that the connection between pushpoold and bitcoind is null.

When I launch pushpoold:

Code:

root@testserver:/home/root/pushpool/sbin# ./pushpoold --debug=2 --stderr --foreground
[1307137799.257380] Debug output enabled
[1307137799.258044] Forcing local hostname to localhost.localdomain
[1307137799.261883] Listening on host :: port 8342
[1307137799.262155] Listening on host :: port 8341
[1307137799.262364] Listening on host :: port 8344
[1307137799.262578] Listening on host xx.xxx.xx.xx port 8338
[1307137799.266777] initialized
[1307137804.486011] client host xxx.xxx.xx.xxx port 58435 connected
[1307137804.493953] client xxx.xxx.xx.xxx ended
[1307137805.852921] client host xxx.xxx.xx.xxx port 58436 connected
[1307137805.858515] client xxx.xxx.xx.xxx ended
[1307137807.207877] client host xxx.xxx.xx.xxx port 58437 connected
[1307137807.212642] client xxx.xxx.xx.xxx ended
[1307137808.567177] client host xxx.xxx.xx.xxx port 58438 connected
[1307137808.572342] client xxx.xxx.xx.xxx ended

The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though ).

Am quite lost now..

[davout]

The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though ).

Am quite lost now..

Your miner has problems connecting to pushpool, check worker credentials when launching, and in DB, check worker query.
Check query logs.

[Xenland]

The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though ).

Am quite lost now..

Your miner has problems connecting to pushpool, check worker credentials when launching, and in DB, check worker query.
Check query logs.

Yeah what he said, make sure you insert a worker to your database, and make sure they match exactly when typing it into your miner

[nzbtc]

Hm, I have the user in the database. Although the query logs are blank, nothing in them.

I can connect to the server's bitcoind directly.. And to the PushPoold. Its like pushpoold wont see bitcoind.

[davout]

Hm, I have the user in the database. Although the query logs are blank, nothing in them.

I can connect to the server's bitcoind directly.. And to the PushPoold. Its like pushpoold wont see bitcoind.

i don't see how you could connect to pushpool with blank query logs

[masterminer]

Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:

user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1# 

[Txyru]

Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:

user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1# 

are you sure its quitting and not just running in the background?

[Xenland]

Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:

user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1# 

are you sure its quitting and not just running in the background?

With the -F flag it should never display the last line user1@226776:. Which means it silenctly shutting down but yet again pushpool never tells us why the things it does....

[masterminer]

Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:

user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1# 

are you sure its quitting and not just running in the background?

No PID, no output to any logs, nothing. I tried using the cfg file example Xenland had posted, along with my own variant, no dice either time. Any ideas?

[dikidera]

Do you have mysql or any other database engine running? It's mandatory, also, bitcoinD should be running prior to launching pushpool

[masterminer]

Do you have mysql or any other database engine running? It's mandatory, also, bitcoinD should be running prior to launching pushpool

Yeah, mysqld running and bitcoind running as well. How strange, it just exits right after launching pretty much ... I've recompiled it, restarted processes - nothing. What am I missing here?

EDIT: Fixed it. Looks like I had the some issue someone else had, permissions problem. I changed all references of '/tmp' to /home/user1'

Woohoo! That consumed way too much time ... I wish pushpoold had kicked out an error or something about it.

[dikidera]

I don't know, i never had any problems regarding permissions. Even the first ever time i ran pushpool. Some people said it's not safe for pushpool to use the /tmp folder, but why?