Pushpool - Tech Support

[crimsonredmk]

OK, connecting to the right port this time gets me new errors (great...):

[1306732202.090055] mysql pwdb query failed at prep
[1306732202.090236] memcached store(/pushpoold/cred_cache/mikes) failed: WRITE FAILURE

"mikes" is the username Phoenix is using to connect. I'm certain server.json has the right MySQL DB, username, and password.

[1713471905]

1713471905

[1713471905]

1713471905

[1713471905]

1713471905

[1713471905]

1713471905

[Xenland]

OK, connecting to the right port this time gets me new errors (great...):

[1306732202.090055] mysql pwdb query failed at prep
[1306732202.090236] memcached store(/pushpoold/cred_cache/mikes) failed: WRITE FAILURE

"mikes" is the username Phoenix is using to connect. I'm certain server.json has the right MySQL DB, username, and password.

Yep Mysql pwdb query failed at prep.
It's most likely its having trouble retrieving password and or username from the mysql database. What does your Table look like?

[crimsonredmk]

I ran

Code:

CREATE TABLE shares (
  id int(11) NOT NULL AUTO_INCREMENT,
  rem_host text NOT NULL,
  username text NOT NULL,
  our_result text,
  upstream_result text,
  reason text,
  solution text,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

CREATE TABLE pool_worker (
  id int(11) NOT NULL AUTO_INCREMENT,
  mikes varchar(128) NOT NULL,
  `waffleman` varchar(128) NOT NULL,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

And as a result got: http://www.cl.ly/152j0K0i383c2d1o4501 (phpMySQL print view)

Edit: No idea what print to PDF did, here's a screenshot: http://cl.ly/3J0n2b2p3V4345381c3V

[Xenland]

I ran

Code:

CREATE TABLE shares (
  id int(11) NOT NULL AUTO_INCREMENT,
  rem_host text NOT NULL,
  username text NOT NULL,
  our_result text,
  upstream_result text,
  reason text,
  solution text,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

CREATE TABLE pool_worker (
  id int(11) NOT NULL AUTO_INCREMENT,
  mikes varchar(128) NOT NULL,
  `waffleman` varchar(128) NOT NULL,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

And as a result got: http://www.cl.ly/152j0K0i383c2d1o4501 (phpMySQL print view)

Edit: No idea what print to PDF did, here's a screenshot: http://cl.ly/3J0n2b2p3V4345381c3V

Your tables are technically valid, You just need to "INSERT" into `pool_worker` with the username and password, in this case it looks like your username and password fields are mikes and waffleman. Look a my original post, I posted up the tables I used to, make sure you "INSERT" into the table.

If you found that this guide was helpful please send in your donations I would like to upgrade my 64MB ram server to 512MB server, so you'll know that your Bitcoins are going back into the community Any thing helps

[crimsonredmk]

Ah, of course. Fixed with

Code:

INSERT INTO pool_worker
(username, password) VALUES('mikes', 'waffleman' )

Next up: 500 error on pushpoold.  Sorry to be such a damned bother to you, you'll be getting some Bitcoins soon!

I have this in my ~/.bitcoin/bitcoin.conf:

Code:

rpcuser=mikes
rpcpassword=waffles
rpcport=8332

and run it with "./bitcoin-0.3.21/bin/64/bitcoind -daemon -gen=0". I of course have the right rpc details in server.json and memcached is running. Going to bed now, but I'll surely be back in the morning with more problems. Sorry!

[Xenland]

Ah, of course. Fixed with

Code:

INSERT INTO pool_worker
(username, password) VALUES('mikes', 'waffleman' )

Next up: 500 error on pushpoold.   Sorry to be such a damned bother to you, you'll be getting some Bitcoins soon!

I have this in my ~/.bitcoin/bitcoin.conf:

Code:

rpcuser=mikes
rpcpassword=waffles
rpcport=8332

and run it with "./bitcoin-0.3.21/bin/64/bitcoind -daemon -gen=0". I of course have the right rpc details in server.json and memcached is running. Going to bed now, but I'll surely be back in the morning with more problems. Sorry!

You are not a bother at all I like to donate my time to be helpful. Especially for something like Bitcoins that might possibly change the world in a positive way for alternative solutions to our problems, and not corrupt it with "Hush! Hush! details about how to get into the game"(which I see alot around here)
 If your referring to the part in my post about the upgrade I just want to let all those who read this guide to announce that I am in need of something that is for the general community so it's in every ones interest to do their part.

*about your error I'm defiantly going to need more details then just a 500server error. Is this what you get when running a miner to connect to pushpoold or when you enter through the browser and type in the details?

[crimsonredmk]

Sounds great 

My 500 error is what pushpoold spits out every time Phoenix tries to connect to it, not through a browser. Phoenix says "MSG: upstream RPC error". Looking around old IRC logs tells me that the connection between pushpoold and bitcoind is to blame here, but I can't find any solutions.

[pwrcycle]

i have my pool up and running using xenland's setup.
I changed the ports around so that it would run on 8332 like the other pools:

http://pool.cloakvpn.com:8332

there's no web front end yet, but the pool is working.
if anyone's interested in testing it out, let me know and i'll setup an account manually.
i think i'll be using the payout account as the username and bitcoin as the password.

[dikidera]

I'd advise against using char in the user table. Char is used for storing fixed length data which a username is not hence VARCHAR should be used with.

[Xenland]

Sounds great 

My 500 error is what pushpoold spits out every time Phoenix tries to connect to it, not through a browser. Phoenix says "MSG: upstream RPC error". Looking around old IRC logs tells me that the connection between pushpoold and bitcoind is to blame here, but I can't find any solutions.

Hmmm surprisingly I've haven't encountered this error yet and a 500 error code is really generic. I would just recommend that your pushpoold server.json file has the correct #RPC Settings, that match your configuration file in /.bitcoin/bitcoin.conf

If that dosent work you might be on a VPS server which blocks ports until opened up with iptables.

[Xenland]

I'd advise against using char in the user table. Char is used for storing fixed length data which a username is not hence VARCHAR should be used with.

Diki is correct in that Char will always use up the same amount of data at the specified length, and Varchar will save data/disk space. I posted up revised table data;
Thanks for the contribution diki!

[nzbtc]

Awesome guide Xenland!

I will play with this later today, and hopefully get experimenting with a front end for pushpool! (I've been delayed as I couldn't set it up >.<)

[pwrcycle]

update:
I finished a workable pool setup. Still under construction, not much to look at but it'll float. graphics etc to come later.

http://pool.cloakvpn.com
Use your payout account number as the username.
The password is "bitcoin"

The pool server is http://pool.cloakvpn.com:8332
Your username is (your bitcoin pay account)
The password is bitcoin
example start string:
minerd -t 2 --url http://pool.cloakvpn.com:8332 --userpass 12QY5HYbiT5Nx6fek8ss5pAywPsV3kqdu3:bitcoin &

[crimsonredmk]

Tried this on a LAN with absolutely no firewalls anywhere and I'm still getting the 500 error. No one else has seen this? What IP should I put in where it says 10.0.0.1? I must be missing something, but I don't know what...

[pwrcycle]

last update for the night:

I got the signup page for http://pool.cloakvpn.com working and doing the user setups automatically now.
You can submit your account and begin mining immediately.
i'll be working on hash rate & share count, etc this week.

[Xenland]

Tried this on a LAN with absolutely no firewalls anywhere and I'm still getting the 500 error. No one else has seen this? What IP should I put in where it says 10.0.0.1? I must be missing something, but I don't know what...

Okay, I think that is it, try setting all the ip addresses that are 10.0.0.1 and set them to your localhost address 127.0.0.1.
My router ip address is 10.0.0.1 so I set it to that to see if could connect to it external with other people on the router.
I think I'll update the JSON file to work for initial set-ups

[redshark1802]

Sounds great  

My 500 error is what pushpoold spits out every time Phoenix tries to connect to it, not through a browser. Phoenix says "MSG: upstream RPC error". Looking around old IRC logs tells me that the connection between pushpoold and bitcoind is to blame here, but I can't find any solutions.

Hello,

i recieved the 500 error when starting bitcoind with a fresh config eq new username and password.
Bitcoin downloads for first the time a lot of  data and the cpu usage spikes.
Just be patient until bitcoin hast done everything. It took about 1 1/2h on my machine.


Now I have a question too:
Can someone please give me a database entry, when a block got solved .


regards, redshark1802

[crimsonredmk]

Thank you Xenland, that finally did it, along with clearing out MySQL completely and starting fresh there. I knew bitcoind took forever to download the blocks at first but I could connect on 8332 and not through pushpoold. All is better now! Thank you! Payment sent.

[nzbtc]

Right, just got in, am going to install this on my vps now. Wish me luck!

Update:

So its all installed and running, However I can't get anything to connect to the server.
I am a little confused about this part of the server.json file:

Code:

   # network ports
   "listen" : [
      # binary protocol (default), port 8342
      { "host" : "127.0.0.1", "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" : "MYSERVERSEXTERNALIP" },

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

Why do I need to open so many ports/listeners? Shouldn't one suffice?
The above does not work when I point my miner(s) at myserversexternalip:8338 (8342,8341,8344)

Help? 

[Xenland]

Right, just got in, am going to install this on my vps now. Wish me luck!

Update:

So its all installed and running, However I can't get anything to connect to the server.
I am a little confused about this part of the server.json file:

Code:

  # network ports
   "listen" : [
      # binary protocol (default), port 8342
      { "host" : "127.0.0.1", "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" : "MYSERVERSEXTERNALIP" },

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

Why do I need to open so many ports/listeners? Shouldn't one suffice?
The above does not work when I point my miner(s) at myserversexternalip:8338 (8342,8341,8344)

Help?  

Okay set your ip address that says #binary protocol, localhost-only port 8338
to  your MYSERVEREXTERNALIP  I think they have to be the same its worth a shot, and report back what happens
As to your question why theirs so many ports, I have no idea. That's up to the maintainer of the pushpool project and most likely needs all those ports.