Pushpool - Tech Support

[Pontius]

1) It would help if could tell us which cryptocurrency exactly you are trying to mine.

2) Don't run pushpool as root. Never ever....

[1713973394]

1713973394

[NothinG]

1) It would help if could tell us which cryptocurrency exactly you are trying to mine.

2) Don't run pushpool as root. Never ever....

1) PPC (new one just coming out)
2) I only did it just to test to make sure everything works.

[Edit]: I got everything to work with poold.py, but I don't like the fact that it (1) doesn't have LP support, (2) and doesn't have MySQL support (I'm currently in the middle of converting it).

[randomdraw.org]

I'm running into this issue right now.  I've checked the passwords, database is running correctly from what I can tell as I've added a username and password and it's the same in the miner, but in PuTTY this is what I see after setting everything up.  Any suggestions?  I'm confused on why it's connecting, but then changing ports every couple of seconds or less and not running.

If you need some more specifics on the .json file or the .conf for BitcoinD I can put that up there, but if it's connecting I don't think those two are the issue as they are running.  I have a feeling it's somehow with the database, but it's beyond me at this point on why it's repeating.

OS: Ubuntu 10.10LTS x64
Memory: 4GB
HDD: 250GB SSD RAID+1
Bandwidth: 1Gbps Single Mode Fiber in Colorado

Code:

root@server:~/pushpool-0.5.1# pushpoold -E -F
[2012-09-17 02:33:46.215660] Listening on host :: port 8342
[2012-09-17 02:33:46.215949] Listening on host :: port 8347
[2012-09-17 02:33:46.216053] Listening on host :: port 8344
[2012-09-17 02:33:46.216126] Listening on host xxx.xxx.xxx.xxx port 9332
[2012-09-17 02:33:46.219237] initialized
[2012-09-17 02:33:50.073888] client host xxx.xxx.xxx.xxx port 51218 connected
[2012-09-17 02:33:54.380851] client host xxx.xxx.xxx.xxx port 51219 connected
[2012-09-17 02:33:58.622966] client host xxx.xxx.xxx.xxx port 51220 connected
[2012-09-17 02:34:48.820656] client host xxx.xxx.xxx.xxx port 51228 connected
[2012-09-17 02:34:53.046884] client host xxx.xxx.xxx.xxx port 51229 connected

I have a bunch of dedicated servers I'm attempting to setup for the Bitcoin public which I'm hoping to just make enough to pay the bills for it to run, not looking to make a fortune.. I love the idea behind Bitcoins, but obviously I'm not going to throw my money out there forever and pay for it completely free, so hoping this gains some ground to at least pay for the server bills!

Thanks in advance!

EDIT: I've also been reading about this subject and Google'ing for hours now, I've had to get a few beers to help filter through all of this! So much appreciation to the person who helps fix it.  In fact, as a promise whoever does help me gets the first 10 BTC I get.   -- I've also put Xenforo on a server for our forums, so as you can tell I'm not messing about, I really want to get this up and running and if you'd like to join me send me a message!

EDIT 2: Also, the user I'm running this under is not root, I just put root@server just for the scenario.

[randomdraw.org]

Nevermind on the post above.  Have sorted it out on my own finally.

Pool service should be starting sometime today!

[BTCMiners.net]

Hey, I'm having a small issue with pushpool.

Here is my readout:

Code:

~/pushpool# pushpoold -E -F -D 2
[2012-09-26 18:03:30.311169] Debug output enabled
[2012-09-26 18:03:30.312361] Forcing local hostname to xxx.xxx.xxx.xxx
[2012-09-26 18:03:30.320688] Listening on host :: port 8342
[2012-09-26 18:03:30.320985] Listening on host :: port 8351
[2012-09-26 18:03:30.321187] Listening on host :: port 8344
[2012-09-26 18:03:30.321297] Listening on host 127.0.0.1 port 8338
[2012-09-26 18:03:30.326450] initialized

When I connect, it does this:

Code:

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

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

* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact

Any suggestions?

Here is my server.json and bitcoin.conf

server.json:

Code:

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

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

		# HTTP JSON-RPC protocol, port 8344,
		# with trusted proxy appserver.example.com forwarding
		# requests to us
		{ "port" : 8344, "protocol" : "http-json",
		  "proxy" : "127.0.0.1" },

		# binary protocol, localhost-only port 8338
		{ "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
	],

	# database settings
	"database" : {
		"engine" : "mysql",
		"host" : "localhost",
		"port" : 3306,
		"name" : "DATABASENAME",
		"username" : "USERNAME",
		"password" : "PASSWORD",
		"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 (?, ?, ?, ?, ?, ?)"

	},

	# cache settings
	"memcached" : {
		"servers" : [
			{ "host" : "127.0.0.1", "port" : 11211 }
		]
	},

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

	# overrides local hostname detection
	"forcehost" : "xxx.xxx.xxx.xxx",

	"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 | 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
	"rpc.url" : "http://127.0.0.1:8333/",
	"rpc.user" : "MyUserName",
	"rpc.pass" : "MyPasswordWasHere",

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

My Bitcoin.conf file:

Code:

# bitcoin.conf configuration file. Lines beginning with # are comments.
 
 
 # Network-related settings:
 
 # Run on the test network instead of the real bitcoin network.
 #testnet=0
 
 # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
 
 ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 #addnode=69.164.218.197
 #addnode=10.0.0.2:8333
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=10.0.0.1:8333
 
 # Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
 # find other peers.
 #noirc=0
 
 # Maximum number of inbound+outbound connections.
 #maxconnections=
 
 
 # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
 
 # server=1 tells Bitcoin-QT to accept JSON-RPC commands.
 server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 rpcuser=USERNAME
 rpcpassword=PASSWORD
 
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established. 
 rpctimeout=30
 
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character):
 rpcallowip=*
 
 # Listen for RPC connections on this TCP port:
 rpcport=8332
 
 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 rpcconnect=xxx.xxx.xxx.xxx
 
 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 #rpcssl=1
 
 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem
 
 
 # Miscellaneous options
 
 # Set gen=1 to attempt to generate bitcoins
 #gen=0
 
 # Use SSE instructions to try to generate bitcoins faster.
 #4way=1
 
 # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 #keypool=100
 
 # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 #paytxfee=0.00
 
 # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
   
 # User interface options
 
 # Start Bitcoin minimized
 #min=1
 
 # Minimize to the system tray
 #minimizetotray=1

[c4n10]

Hello all...

I'm trying to set-up pushpool and for some reason I keep receiving "mysql pwdb query failed at fetch".

Here's the run-down:

OS is Ubuntu
Running MySql
Front-end: SimpleCoin
Miners connect fine but pushpool returns "mysql pwdb query failed at fetch" when connecting because mysql is trying to read username as "?"

mysql.log shows pushpool trying to pass the following statement:

Code:

SELECT password FROM pool_worker WHERE username = ?

Which is being called by pushpool's server.json file in this section (user/pass info has been edited):

Code:

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

                # 'host' defaults to localhost, if not specified
                # "host" : "localhost",

                # 'port' uses proper default port for the DB engine,
                # if not specified
                "port" : "3306",

                "name" : "simplecoin",
                "username" : "SuperCoolUsername",
                "password" : "SuperSecretPassword",
                "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 (?, ?, ?, ?, ?, ?)"
		},

Workers have been added to table "pool_worker".

It would seem to me that the json client doesn't like the way the variable is being handled in:

Code:

"stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",

Since the "?" isn't being properly replaced by the connecting miner's username and the statement otherwise works fine when tested from mysql command line...

Any ideas on how I can fix the variable so json passes the correct statement to mysql...?

[c4n10]

Hello all...

I'm trying to set-up pushpool and for some reason I keep receiving "mysql pwdb query failed at fetch".

Here's the run-down:

OS is Ubuntu
Running MySql
Front-end: SimpleCoin
Miners connect fine but pushpool returns "mysql pwdb query failed at fetch" when connecting because mysql is trying to read username as "?"

mysql.log shows pushpool trying to pass the following statement:

Code:

SELECT password FROM pool_worker WHERE username = ?

Which is being called by pushpool's server.json file in this section (user/pass info has been edited):

Code:

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

                # 'host' defaults to localhost, if not specified
                # "host" : "localhost",

                # 'port' uses proper default port for the DB engine,
                # if not specified
                "port" : "3306",

                "name" : "simplecoin",
                "username" : "SuperCoolUsername",
                "password" : "SuperSecretPassword",
                "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 (?, ?, ?, ?, ?, ?)"
		},

Workers have been added to table "pool_worker".

It would seem to me that the json client doesn't like the way the variable is being handled in:

Code:

"stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",

Since the "?" isn't being properly replaced by the connecting miner's username and the statement otherwise works fine when tested from mysql command line...

Any ideas on how I can fix the variable so json passes the correct statement to mysql...?

Ok, this is fixed...

New problem...

requests.log is being populated but shares.log is not being populated...

Any help...?

[c4n10]

New problem...

requests.log is being populated but shares.log is not being populated...

Any help...?

Ok, there's not actually a "problem" per se, the issue is that I'm using with litecoind and it is trying to use BTC share diff of 1...

I've found this: https://bitcointalk.org/index.php?topic=27970.msg353618#msg353618

but the information in config.c seems to have changed and that section no longer exists, instead this is in it's place:

Code:

static void set_easy_target_bits(unsigned int bits)
{
        unsigned int i;
        char *tstr;
        if (bits == 0)
                return;
        if (bits > 255) {
                applog(LOG_ERR, "error: invalid easy target bits specified");
                exit(1);
        }
        for(i = 0; i < 32 - (bits / 8); i++)
                srv.easy_target_bin[i] = 0xff;
        if(bits % 8)
                srv.easy_target_bin[i-1] = 0xff >> (bits % 8);
        tstr = bin2hex(srv.easy_target_bin, 32);
        srv.easy_target = json_string(tstr);
        if (debugging > 0)
                applog(LOG_INFO, "set easy target %s", tstr);
        free(tstr);
}

How can I set this to the litecoin standard of something like 2-16 or 2-15?

[c4n10]

How can I set this to the litecoin standard of something like 2-16 or 2-15?

Ok, I have adjusted the difficulty successfully, now I just need to know why nothing is being written to my shares tables or shares.log even though miners are connecting and finding shares...

[c4n10]

Hello,

we are using pushpool on minelitecoin.com (I don't remember which fork it was a fork which did not support "rpc.target.bits") and we are looking to set share 16 difficulty...

We have found in config.c where it has the set EASY_TARGET = "ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000" which allows the rewrite.target : true to rewrite it share difficulty of 1.

What would we need to change "ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000" to in order to set to difficulty of 16 for litecoin...?

Thank you in advance for your help!

[flound1129]

I've got pushpool up and running, but for some reason it's not inserting anything into my shares table..  From what I can tell it's not even attempting the insert statement (no inserts in mysql.log).

Here's my DB config:

Code:

        # database settings
        "database" : {
                "engine" : "mysql",
                # 'host' defaults to localhost, if not specified
                "host" : "localhost",
                "port" : 3306,

                "name" : "xxx",
                "username" : "xxx",
                "password" : "xxx",
                "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 (?, ?, ?, ?, ?, ?)"
        },

It's definitely connecting to MySql because I can see the select statements for worker passwords..

[Xenland]

Just a heads up I will be getting to work on on the "mining farm" project in late April or early may as I must learn how to use pushpool again (as well as p2pool) and might be able to help some of the mates that are having some issues when that time comes

[jgarzik]

Given renewed interest, it is strongly tempting to jump in and fix the major misfeatures:

• getwork proxying (should be getblocktemplate for high speeds)
• internal work generation
• stratum protocol support
• separate database threads

[drkurubit]

Given renewed interest, it is strongly tempting to jump in and fix the major misfeatures:

• getwork proxying (should be getblocktemplate for high speeds)
• internal work generation
• stratum protocol support
• separate database threads

Please do

[digger]

i testing my litecoin pool,

set difficult to 20,

have submitted 10000 shares, but there are no shares upstream with "N" or "Y"

is it any problem?

[digger]

now 30000 shares, still no upstream_result with "N" or "Y"

problems?

[Remember remember the 5th of November]

now 30000 shares, still no upstream_result with "N" or "Y"

problems?

upstream_result is when the pool detects a share at or higher than the network target, ONLY THEN does it allow it to get to bitcoind. That's why, basically.

[digger]

now 30000 shares, still no upstream_result with "N" or "Y"

problems?

upstream_result is when the pool detects a share at or higher than the network target, ONLY THEN does it allow it to get to bitcoind. That's why, basically.

litecoin now only difficult 234, 30000 difficult 20 shares no one submit to litecoind?
i want to open the pool, but worry if it has problem, in the situation, will never find one block.

because litecoind testnet doesn't work, so i can't debug there.

[raubaut]

After everything, I get to the last steps and:

Code:

./configure: line 5901: syntax error near unexpected token `,'
./configure: line 5901: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'

[Remember remember the 5th of November]

After everything, I get to the last steps and:

Code:

./configure: line 5901: syntax error near unexpected token `,'
./configure: line 5901: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'

you need libcurl.m4 placed in a pkg-config folder somewhere.