Pushpool - Tech Support

[ziomik]

pushpool and bitcoin communicate with eachother on port 8333 correct?

Yes bitcoind and pushpool

and i configure miningfarm rpc to use port 8332 for bitcoind?

No 8333

pushpool and miningfarm use the same mysql database

YES

to get everything rolling
i start bitcoind
then i run ./blkmond server.json

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

change port bitcoind in 8333

bye

[1713575478]

1713575478

[1713575478]

1713575478

[1713575478]

1713575478

[1713575478]

1713575478

[1713575478]

1713575478

[cablepair]

ok thank you, what does blkmond do?

sorry for my ignorance, but there is not much documentation on this stuff.

[cablepair]

I changed everything the way you told me to
but now I keep getting this when I start bitcoind

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12sys tem_errorEEEEE
Address already in use
bitcoin in ThreadRPCServer()

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  Address already in use
Aborted

[ziomik]

try to change the port 8333 bitcoind and, therefore, and pushpoold minifarm .. put the 8331

[ziomik]

ok thank you, what does blkmond do?

sorry for my ignorance, but there is not much documentation on this stuff.

better manage and share it prevents the loss of share. excuse for the translation google translate! ;-)

[cablepair]

i dont know whats going on man
nothing will run on port 8333 now
keeps saying address already in use

i had this problem last night and I forgot how i fixed it

thank you for helping but now im in worse shape then when i started ;/

[ziomik]

ok, try doing a nice reboot.
bye

[cablepair]

[2011-07-28 22:35:8.091291] Listening on host 127.0.0.1 port 8338


does that mean I should be connecting the miners to port 8338?

[ziomik]

No, your setting is  8341

Code:

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

[cablepair]

ok I set bitcoind to be on port 8331

started it up - its running
I can connect my miner directly to that on port 8331 using the rpcusername and password (just to test the connection)

I edited server.json so the rpcurl http://127.0.0.1:8331

this is what I got on the pushpool screen:

tom@BitCoinMinersUnion:/home/pushpool/sbin$ ./pushpoold -E -F

[2011-07-28 22:48:7.708102] Listening on host :: port 8342
[2011-07-28 22:48:7.708348] Listening on host :: port 8341
[2011-07-28 22:48:7.708427] Listening on host :: port 8332
[2011-07-28 22:48:7.708499] Listening on host 127.0.0.1 port 8338


you said to connect the miner to 8341 and that would connect to push pool? but its not working

any ideas?

 

[cablepair]

I really want to get this working, I will pay 5 BTC to the person who gets this working for me tonight!

[ziomik]

how did you write the command of the miner? write it

[cablepair]

well im using guiminer from another machine on my network

but the pushpoold never gets to the initialized screen

[ziomik]

first and then you started bitcoind pushpool?
They are active, have occurred? If you did not check with

ps aux | grep bitcoind
and
ps aux | grep pushpoold

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

[ziomik]

have entered a worker in workers mininpool?
guiminer as username and password you wrote usernamesite.usernameworker and password worker (not site)

[cablepair]

om@BitCoinMinersUnion:~$ ps aux | grep bitcoind
tom      16059  5.0  1.4 224568 59808 pts/1    Sl+  19:04   0:08 ./bitcoind -ser                                                                              ver
tom      17040  0.0  0.0  13128  1036 pts/2    S+   19:07   0:00 grep --color=au                                                                              to bitcoind
tom@BitCoinMinersUnion:~$ ps aux | grep pushpoold
tom      16607  0.0  0.1  77872  4180 pts/0    S+   19:06   0:00 ./pushpoold -E -F
tom      17081  0.0  0.0  13128  1040 pts/2    S+   19:07   0:00 grep --color=auto pushpoold
tom@BitCoinMinersUnion:~$

[cablepair]

yes i know its not a problem of how I am entering the mining information into the miner

when bitcoind is running I can get my miner going directly to the bitcoind
but it does not connect to pushpool


please just go over the steps for me again

bitcoind - pushpoold - and miningfarm all have to be on the same port - correct?
but they have to be on a seperate port from 8332 - correct?

in order to start them up
first i run ./bitcoind -server
then i run ./pushpoold - E -F

after than I should be able to mine on the pushpool mining port correct?

[cablepair]

have you setup pushpool before?

I will give you 5 btc to log into my server and fix whatever problem I am having.

[ziomik]

Ok:
SERVER.JASON

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,
		# with trusted proxy appserver.example.com forwarding
		# requests to us
		{ "port" : 8334, "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" : "namedatabase",
		"username" : "user",
		"password" : "pass",
		"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" : "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 | 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:8331/",
	"rpc.user" : "user",
	"rpc.pass" : "pass",

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

BITCOIN.CONF:

Code:

rpcuser=user
rpcpassword=pass
rpcport=8331
rpcallowip=*.*.*.*

[cablepair]

ok bitcoind started up

now pushpoold is hanging like this:

[2011-07-28 23:25:3.778328] Listening on host :: port 8342
[2011-07-28 23:25:3.778567] Listening on host :: port 8341
[2011-07-28 23:25:3.778647] Listening on host :: port 8334
[2011-07-28 23:25:3.778720] Listening on host 127.0.0.1 port 8338


miner wont connect
you ready to log in and fix it?