Pushpool - Tech Support

[Viceroy]

doesn't seem to make any difference.  

i still don't see any 'initialized'

nor can I mine on any of the ports (8333,8338,8341,8342,8344)

[Xenland]

doesn't seem to make any difference.  

i still don't see any 'initialized'

nor can I mine on any of the ports (8333,8338,8341,8342,8344)

I see, This might sound dumb but for some reason the bitcoin.conf file that you have I believe comes with the bitcoin download, that NEVER works for me i just do a simple 4 line config.
Make sure all files have the correct read permissions. This includes any log files that pushpoold uses in the /tmp/ folder, aswell as the bitcoin.config and server.json files.

Example Simple bitcoin.conf

Code:

rpcuser=someusername
rpcpassword=somereallylongrandompassword
rpcallowip=127.0.0.1
rpcport=8362

[Viceroy]

it makes sense to test with a simpler config file.

simpler config file still not getting the 'initialized' statement
still unable to mine with pushpoold
able to mine just fine with bitcoind on 8332 with rpc user and pw


your notes are confusing you say not to use 8332 in the config file:

# RPC settings | Notice how this ISN'T port number 8332 this is becuase the same port number should not becuase inconjunction with the JSON RPC port other wise you'll get 500 errors

 but then, two posts back, you said I *should* use 8332.


my current bitcoin.conf:

rpcuser=test
rpcpassword=x
rpcallowip=*
rpcport=8332


what port is my miner supposed to mine on when it attaches to pushpool?

[Viceroy]

ok, new day, let's start again.



bitcoind:
seems to be working as expected.
can connect and start mining@   192.168.2.52:8332

bitcoin.conf file is ultra simple:
rpcuser=test
rpcpassword=x
rpcallowip=*
rpcport=8332
server=1

so I must put that user name and machine ip addy in my server.json file.

server.json:

        "rpc.url" : "http://192.168.2.52:8332/",
        "rpc.user" : "test",
        "rpc.pass" : "x",

yep it's in there.

running....
./pushpoold -E -F --debug=2

output:
[2011-07-23 14:46:28.854801] Debug output enabled
[2011-07-23 14:46:28.855140] Forcing local hostname to localhost.localdomain
[2011-07-23 14:46:28.858717] Listening on host :: port 8342
[2011-07-23 14:46:28.858843] Listening on host :: port 8341
[2011-07-23 14:46:28.858913] Listening on host :: port 8344
[2011-07-23 14:46:28.858958] Listening on host 127.0.0.1 port 8338


damnit, no initialized.


doesn't seem there is anything actually listening, other than bitcoin:

netstat -p -l | grep bit
tcp        0      0 *:8332                      *:*                         LISTEN      3333/bitcoind
tcp        0      0 *:8333                      *:*                         LISTEN      3333/bitcoind

netstat -p -l | grep push
(no output)

netstat -p -l | grep pool
(no output)


in /tmp we have:
/tmp/request.log 
/tmp/shares.log

both 0 length

no pid file in temp directory

no activity in mysqld.log

tail -4 /var/log/mysqld.log
110722 18:03:37  mysqld started
110722 18:03:38  InnoDB: Started; log sequence number 0 43665
110722 18:03:38 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

(mysql been up 14 hours)

[Flowz]

ok, new day, let's start again.



bitcoind:
seems to be working as expected.
can connect and start mining@   192.168.2.52:8332

bitcoin.conf file is ultra simple:
rpcuser=test
rpcpassword=x
rpcallowip=*
rpcport=8332
server=1

so I must put that user name and machine ip addy in my server.json file.

server.json:

        "rpc.url" : "http://192.168.2.52:8332/",
        "rpc.user" : "test",
        "rpc.pass" : "x",

yep it's in there.

running....
./pushpoold -E -F --debug=2

output:
[2011-07-23 14:46:28.854801] Debug output enabled
[2011-07-23 14:46:28.855140] Forcing local hostname to localhost.localdomain
[2011-07-23 14:46:28.858717] Listening on host :: port 8342
[2011-07-23 14:46:28.858843] Listening on host :: port 8341
[2011-07-23 14:46:28.858913] Listening on host :: port 8344
[2011-07-23 14:46:28.858958] Listening on host 127.0.0.1 port 8338


damnit, no initialized.


doesn't seem there is anything actually listening, other than bitcoin:

netstat -p -l | grep bit
tcp        0      0 *:8332                      *:*                         LISTEN      3333/bitcoind
tcp        0      0 *:8333                      *:*                         LISTEN      3333/bitcoind

netstat -p -l | grep push
(no output)

netstat -p -l | grep pool
(no output)


in /tmp we have:
/tmp/request.log 
/tmp/shares.log

both 0 length

no pid file in temp directory

no activity in mysqld.log

tail -4 /var/log/mysqld.log
110722 18:03:37  mysqld started
110722 18:03:38  InnoDB: Started; log sequence number 0 43665
110722 18:03:38 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source distribution

(mysql been up 14 hours)

Try doing the following..
First of all, use more 127.0.0.1 since it's all running on the same machine. Second of all use a other port for bitcoind. 8362 for example
server.json:

Code:

        "rpc.url" : "http://127.0.0.1:8362/",
        "rpc.user" : "test",
        "rpc.pass" : "x",

bitcoind is running on the same machine as pushpoold is running, 192.168.2 could work too but 127.0.0.1 is fine!

bitcoin.conf:

Code:

rpcuser=test
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=8362

Only the server needs to acces the wallet, so leave that localhost/127.0.0.1.

 

[Viceroy]

no difference.

still no "initialized"
and not able to mine

what port should I be able to mine on from pushpoold?

doesn't this all put out text output?
can't I just telnet to these ports and read the stream?
(I don't seem able to telnet to these ports).

[Viceroy]

Only the server needs to acces the wallet, so leave that localhost/127.0.0.1.

What wallet?  this was compiled without the wallet flag or keystore.

[Flowz]

no difference.

still no "initialized"
and not able to mine

what port should I be able to mine on from pushpoold?

doesn't this all put out text output?
can't I just telnet to these ports and read the stream?
(I don't seem able to telnet to these ports).

Hmm Maybe re-check the MySQL settings?
Ofcourse telnet won't work. pushpoold isn't running.

[Flowz]

Only the server needs to acces the wallet, so leave that localhost/127.0.0.1.

What wallet?  this was compiled without the wallet flag or keystore.

Sorry! I ment that it was the only one who needs to acces bitcoind.

[Viceroy]

Hmm Maybe re-check the MySQL settings?
Ofcourse telnet won't work. pushpoold isn't running.

yea, I changed is a little, still no "initialized"

how are you calling your database name?

I don't see an option to name the database, just the table... so I'm assuming I should use:
                "name" : "`btcWorkers`.`shares`",

Where btcWorkers is the "database" and shares is the "table".

what port are you mining on?

what do you see with
netstat -p -l

[Flowz]

Hmm Maybe re-check the MySQL settings?
Ofcourse telnet won't work. pushpoold isn't running.

yea, I changed is a little, still no "initialized"

how are you calling your database name?

I don't see an option to name the database, just the table... so I'm assuming I should use:
                "name" : "`btcWorkers`.`shares`",

Where btcWorkers is the "database" and shares is the "table".

what port are you mining on?

what do you see with
netstat -p -l

1. I'm using a remote host, mine is called: themalwa_pushpool. My advantage: I got phpMyAdmin then

2. I don't know what you mean.. In what file?

3. 8344

4.

Code:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 *:6665                      *:*                         LISTEN      5954/ircd
tcp        0      0 *:mysql                     *:*                         LISTEN      27772/mysqld
tcp        0      0 *:8362                      *:*                         LISTEN      13611/bitcoind
tcp        0      0 *:6666                      *:*                         LISTEN      5954/ircd
tcp        0      0 *:ircd                      *:*                         LISTEN      5954/ircd
tcp        0      0 *:6668                      *:*                         LISTEN      5954/ircd
tcp        0      0 *:8333                      *:*                         LISTEN      13611/bitcoind
tcp        0      0 *:6669                      *:*                         LISTEN      5954/ircd
tcp        0      0 localhost.localdomain:8338  *:*                         LISTEN      25659/pushpoold
tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      11483/sendmail: acc
tcp        0      0 *:http                      *:*                         LISTEN      3880/httpd
tcp        0      0 *:8342                      *:*                         LISTEN      25659/pushpoold
tcp        0      0 *:ssh                       *:*                         LISTEN      11337/sshd
tcp        0      0 *:8344                      *:*                         LISTEN      25659/pushpoold
tcp        0      0 *:8347                      *:*                         LISTEN      25659/pushpoold
raw        0      0 *:icmp                      *:*                         7           -
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node PID/Program name    Path
unix  2      [ ACC ]     STREAM     LISTENING     381087114 9509/brcm_iscsiuio  @ISCSID_UIP_ABSTRACT_NAMESPACE
unix  2      [ ACC ]     STREAM     LISTENING     381087587 11648/saslauthd     /var/run/saslauthd/mux
unix  2      [ ACC ]     STREAM     LISTENING     393123351 27772/mysqld        /var/lib/mysql/mysql.sock

[Viceroy]

hmmm.

* Viceroy scratches head

I like seeing those listeners in your netstat.  They definitely don't appear in mine.

The line I pulled was in server.json

        # database settings
        "database" : {
                "engine" : "mysql",
                "host" : "localhost",
                "port" : 3306,
                "name" : "`btcWorkers`.`shares`",
                "username" : "remoteusername",
                "password" : "remoteuserpasswd",
                "sharelog" : true,
                "stmt.pwdb":"SELECT `password` FROM `btcWorkers`.`pool_worker` WHERE username = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

        },

what does your working "name" line look like?
what about the "stmt.pwdb", is it like mine?

Anyone know if there is another variable to set database name?  or is this format correct?

[Flowz]

hmmm.

* Viceroy scratches head

I like seeing those listeners in your netstat.  They definitely don't appear in mine.

The line I pulled was in server.json

        # database settings
        "database" : {
                "engine" : "mysql",
                "host" : "localhost",
                "port" : 3306,
                "name" : "`btcWorkers`.`shares`",
                "username" : "remoteusername",
                "password" : "remoteuserpasswd",
                "sharelog" : true,
                "stmt.pwdb":"SELECT `password` FROM `btcWorkers`.`pool_worker` WHERE username = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

        },

what does your working "name" line look like?
what about the "stmt.pwdb", is it like mine?

Anyone know if there is another variable to set database name?  or is this format correct?

Code:

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

      "host" : "host",

      "port" : 3306,

      #database name
      "name" : "themalwa_pushpool",
      #database username
      "username" : "themalwa_node1",
      #database password
      "password" : "password",
      #enable sharelog | to insert share data or sometimes known
      "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 (?, ?, ?$

   },

Seems like you messed up a bit! you keep those things default, you only change: name,username,password and in my case host. you change the SQL queries but you need to keep them default. If you really really want to use the db name infront of the table then you must do (NOT NEEDED!):
databasename.table
btcWorkers.pool_worker
It's all not necessery but whatever you want!

Fix this:

Code:

  "name" : "`btcWorkers`.`shares`",

Code:

  "name" : "btcWorkers"

Code:

                "stmt.pwdb":"SELECT `password` FROM `btcWorkers`.`pool_worker` WHERE username = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

        },

Code:

      "stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",
      "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?$

   },

[Viceroy]

ahhhhhhhhhhhhhhh    


They are looking for the name of the database, not the table.
I guess I never changed that one.  

* Viceroy blushes

so then the tablename 'shares' is hardcoded into pushpool?

I see the table name pool_worker is, indeed, hard coded into the mysql file
 /home/pushpool/pushpool-0.5.1/db-mysql.c

Yep, shares is in there as well:

#define DEFAULT_STMT_SHARELOG \
        "INSERT INTO shares (rem_host, username, our_result, "          \
        "                    upstream_result, reason, solution) "       \
        "VALUES(?,?,?,?,?,?)"


ok, getting "initialized"... and some new errors.  


 ./pushpoold -E -F --debug=2 &

[2] 3272
[2011-07-23 21:58:13.772935] Debug output enabled
[2011-07-23 21:58:13.776582] Listening on host :: port 8342
[2011-07-23 21:58:13.776711] Listening on host :: port 8341
[2011-07-23 21:58:13.776781] Listening on host :: port 8344
[2011-07-23 21:58:13.776828] Listening on host 127.0.0.1 port 8338
[2011-07-23 21:58:13.779497] initialized
JSON protocol request:
{"method": "getwork", "params": [], "id":1}

* About to connect() to 192.0.0.1 port 8362
*   Trying 192.0.0.1... * TCP_NODELAY set
* Connection timed out
* couldn't connect to host
* Closing connection #0
[2011-07-23 21:58:34.799230] HTTP request failed: couldn't connect to host
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* About to connect() to 192.0.0.1 port 8362
*   Trying 192.0.0.1... * TCP_NODELAY set


I'm sure this will be an easy fix

[Flowz]

ahhhhhhhhhhhhhhh    




They are looking for the name of the database, not the table.

so then the tablename 'shares' is hardcoded into pushpool?

I don't know + Not needed for now, aslong as pushpoold can connect to your MySQL server and pick out the database it will say: 'initialized' but if the SQL structure isn't right and you start mining then pushpoold will give you an error.

Too Long; Made no sense: The tables/columns don't have to be correct to get the initialized message!
 Just connecting is enough. We'll fix that later.

MiningFarm provides you the full table and column construction for your pool to work.

[Viceroy]

yep, it was.  testing.

Thank you Flowz

[Flowz]

yep, it was.  testing.

Thank you Flowz

You're welcome Viceroy, if you need help with the front-end of the pool don't hassle to contact me.
The front-end is pretty easy to setup, but I dislike the lay-out of MiningFarm so I'm modificating that a lot!

[Viceroy]

modificating

You're like sarah palin, you make up words

It's a cool sounding word, I wish I'd thought it up.

[Flowz]

modificating

You're like sarah palin, you make up words

It's a cool sounding word, I wish I'd thought it up.

I'm not Sarah Palin! I'm a world leader znd she will never be one.
I actually wanted to write: modifieing/modifying but I don't know how to spell it
To modify and to modificate, Those 2 are correct right?
Btw, we're going off topic with this so if you face any problem in regards of pushpoold/bitcoin/miningfarm. We're here to help you

[jgarzik]

The init steps are as follows:

1. other stuff
2. init network ports
3. init database
4. print "initialized"

It sounds like your database is causing some sort of crash upon init.