pushpool - open source pool software

[Xenland]

After 18hours of attempting to get pushpool working ive ran into just about everyproblem. Ill be writing an install guide right after i finish the front end interface for pushpool.

Any one know why when i enable sharelog:true, that it would send the shares as questions marks.

Heres mysql query: "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

[1714824957]

1714824957

[1714824957]

1714824957

[1714824957]

1714824957

[1714824957]

1714824957

[1714824957]

1714824957

[nzbtc]

After 18hours of attempting to get pushpool working ive ran into just about everyproblem. Ill be writing an install guide right after i finish the front end interface for pushpool.

Any one know why when i enable sharelog:true, that it would send the shares as questions marks.

Heres mysql query: "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

Perfection! Can't wait!

[redshark1802]

Hello,


i get the following error when running ./configure:"
./configure: line 5431: syntax error near unexpected token `,'
./configure: line 5431: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'
"

I have libcurl installed but I'm stuck for about 3hrs now -.-.
please could someone help me.

[oVPN]

....
I have libcurl installed but I'm stuck for about 3hrs now -.-.
please could someone help me.

whats your OS?

[xf2_org]

i get the following error when running ./configure:"
./configure: line 5431: syntax error near unexpected token `,'
./configure: line 5431: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'
"

You built the configure script incorrectly.

Do not use the git repo, that's for experts.  Download and run the tarball (see first post).

[redshark1802]

It actually was the tarball dude.
I have solved it. I reinstalled all libcurl stuff and installed i via source.

[dds]

Could anyone tell how to configure pushpool long-polling with poclbm miner?
Looks like it doesn't work. Miner reports "long poll exception" and "invalid or stale" shares from time to time.
I have "longpoll.disable" : false in pushpool config.

[Xenland]

Could anyone tell how to configure pushpool long-polling with poclbm miner?
Looks like it doesn't work. Miner reports "long poll exception" and "invalid or stale" shares from time to time.
I have "longpoll.disable" : false in pushpool config.

Well in my experience I'm using poclbm and i rarely get invalid and i think i got long pool exception

[dds]

Well in my experience I'm using poclbm and i rarely get invalid and i think i got long pool exception

What exactly rarely mean? 
I have about 4% of stale shares in my pushpool DB.
btw, how many MH/s do you have on your pushpool instance?

[Xenland]

Well in my experience I'm using poclbm and i rarely get invalid and i think i got long pool exception

What exactly rarely mean? 
I have about 4% of stale shares in my pushpool DB.
btw, how many MH/s do you have on your pushpool instance?

Rarly as in probubly around 1 in 100 shares, 4% dosent sound bad or alarming but maybe your packets are being dropped by a firewall. I get about the same MH/s as i do with other pools which is 85-90 range.

[davout]

Could anyone tell how to configure pushpool long-polling with poclbm miner?
Looks like it doesn't work. Miner reports "long poll exception" and "invalid or stale" shares from time to time.
I have "longpoll.disable" : false in pushpool config.

From my understanding you'd need to active blkmon so it monitors new blocks.
It should then send SIGUSR1 to the pushpoold to notify it

[Xenland]

Could anyone tell how to configure pushpool long-polling with poclbm miner?
Looks like it doesn't work. Miner reports "long poll exception" and "invalid or stale" shares from time to time.
I have "longpoll.disable" : false in pushpool config.

From my understanding you'd need to active blkmon so it monitors new blocks.
It should then send SIGUSR1 to the pushpoold to notify it

Dude, Is that what that does? I could never get it started.... but Im having a bit of an issue geting pushpoold started on my VPS it reports that its listening on 127.0.0.1 but it shuts down immediately right after it reports this any solutions?

[davout]

Could anyone tell how to configure pushpool long-polling with poclbm miner?
Looks like it doesn't work. Miner reports "long poll exception" and "invalid or stale" shares from time to time.
I have "longpoll.disable" : false in pushpool config.

From my understanding you'd need to active blkmon so it monitors new blocks.
It should then send SIGUSR1 to the pushpoold to notify it

Dude, Is that what that does? I could never get it started.... but Im having a bit of an issue geting pushpoold started on my VPS it reports that its listening on 127.0.0.1 but it shuts down immediately right after it reports this any solutions?

Yes, you need it only for long polling tho

[turlando]

Hello,
I'm a newbie here and this is my first post.

I'm trying to set up a pushpool server using PostgreSQL as SQL server but I have some troubles: I compiled the daemon, I modified the configuration file in order to use postgresql and I adapted the mysql query that I found here for pgsql, but when I try to connect to the server, the daemon prints out this error:

Code:

[1307005729.968275] pg_pwdb_lookup query failed: ERROR:  syntax error at end of input
LINE 1: SELECT password FROM pool_worker WHERE username = ?

In PostgreSQL the object of the WHERE clause have to be in quotes, as you can see:

Code:

pushpool=# SELECT password FROM pool_worker WHERE username = test;
ERROR:  column "test" does not exist
LINE 1: SELECT password FROM pool_worker WHERE username = test;
                                                          ^
pushpool=# SELECT password FROM pool_worker WHERE username = 'test';
             password             
----------------------------------
      /* password in md5 */
(1 row)

So I modified the configuration file to:

Code:

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

but I get:

Code:

[1307006155.225905] pg_pwdb_lookup query failed: ERROR:  bind message supplies 1 parameters, but prepared statement "" requires 0

I'm doing wrong something or is a bug?

Sorry for my very bad English.
Tancredi.

[kjj]

The syntax is different.  Try this (lifted straight out of db-postgresql.c):

Code:

"SELECT password FROM pool_worker WHERE username = $1"

[Jine]

Take a loot at my fork of pushpoold.
Which includes a much better configuration file, with examples.

(For postgres to)

https://github.com/jine/pushpool

[turlando]

Right, I compiled jine-pushpool; it connects to the PostgreSQL server, but now I get these errors:
on the client ↓

Code:

% ./minerd --url http://192.168.1.99:8337/ --user test --pass test
[2011-06-02 14:35:18] HTTP request failed: The requested URL returned error: 403
[2011-06-02 14:35:18] json_rpc_call failed, retry after 30 seconds

on the server ↓

Code:

% ./pushpoold -E -D 2 --config=config.json
[1307021446.964664] Debug output enabled
[1307021446.977801] Listening on host :: port 8336
[1307021446.978053] Listening on host :: port 8337
[1307021446.978140] Listening on host 127.0.0.1 port 8338
[1307021447.003793] initialized
[1307021594.453532] client host ::ffff:192.168.1.210 port 45973 connected
[1307021594.453781] client ::ffff:192.168.1.210 ended

This is the configuration file:

Code:

% cat config.json
{
	# network ports
	"listen" : [
		# binary protocol (default), port 8336
		{ "port" : 8336 },

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

		# HTTP JSON-RPC protocol, port 8339,
		# with trusted proxy appserver.example.com forwarding
		# requests to us
		#
		# comment out if not using multiple servers
		#{ "port" : 8337, "protocol" : "http-json",
		#  "proxy" : "appserver.example.com" },

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

	# database settings
	"database" : {

		##
		# select one database engine and remove the other ones.
		##
		
	#	"engine" : "sqlite3",
	#	"name" : "/tmp/data.sqlite",

		# set to true to enable logging of shares to db
	#	"sharelog" : true,

		# edit queries to match your database structure if necessary
	#	"stmt.pwdb" :
	#	  "SELECT password FROM pool_worker WHERE username = ?",
		
        #        "stmt.sharelog" :
        #          "INSERT INTO shares (time, rem_host, username, our_result, upstream_result, reason, solution) VALUES (?,?,?,?,?,?,?)"

		# ... or ...

	#	"engine" : "mysql",

		# 'host' defaults to localhost, if not specified
	#	"host" : "mysql.example.com",

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

	#	"name" : "mydatabasename",
	#	"username" : "myuser",
	#	"password" : "mypass",

		# set to true to enable logging of shares to db
	#	"sharelog" : true,

		# edit queries to match your database structure if necessary
	#	"stmt.pwdb" :
	#	  "SELECT password FROM pool_worker WHERE username = ?",

        #       "stmt.sharelog" :
        #          "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?,?,?,?,?,?)"


		# ... or ...

		"engine" : "postgresql",

		"host" : "127.0.0.1",

		"port" : 5432,

		"name" : "dbname",
		"username" : "dbusername",
		"password" : "dbpassword",

		# set to true to enable logging of shares to db
		"sharelog" : true,

		# edit queries to match your database structure if necessary
		"stmt.pwdb" :
		  "SELECT password FROM pool_worker WHERE username = $1",
		
                "stmt.sharelog" :
                  "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES ($1, $2, $3, $4, $5, decode($6, 'hex'))"

	},

	# cache settings
	# comment out to disable memcache - NOT RECOMMENDED
	"memcached" : {
		"servers" : [
			{ "host" : "127.0.0.1", "port" : 11211 }
		]
	},

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

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

	# logfiles for requests and shares
	"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 to bitcoind upstream server (same as bitcoin.conf if using original client)
	"rpc.url" : "http://127.0.0.1:8332/",
	"rpc.user" : "username",
	"rpc.pass" : "password",

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

[Jine]

Have you changed the dbname/dbuser/dbpass vars in your own config?
And also, is your table actually named pool_worker and has at least to fields - username & password?

Aka. check your config, that it actually can read those tables & try again.

My version isn't any diffrent from the original, only better config & commenting.

[turlando]

Have you changed the dbname/dbuser/dbpass vars in your own config?

Obviously.

And also, is your table actually named pool_worker and has at least to fields - username & password?

Yes.

The password have to be in plain text, isn't it?
Would you like a database dump?

P.S.: Thanks for the support

[Jine]

Strange, look in syslog if pushpoold is outputted something regarding your db.
And memcache is up and running? (Just comment it out otherwise)