Bitcoin Forum
May 08, 2024, 12:18:13 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Need Pushpool Help - mysql pwdb query failed at fetch  (Read 712 times)
c4n10 (OP)
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250



View Profile
March 22, 2013, 02:27:58 PM
 #1

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...?
1715170693
Hero Member
*
Offline Offline

Posts: 1715170693

View Profile Personal Message (Offline)

Ignore
1715170693
Reply with quote  #2

1715170693
Report to moderator
1715170693
Hero Member
*
Offline Offline

Posts: 1715170693

View Profile Personal Message (Offline)

Ignore
1715170693
Reply with quote  #2

1715170693
Report to moderator
If you want to be a moderator, report many posts with accuracy. You will be noticed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715170693
Hero Member
*
Offline Offline

Posts: 1715170693

View Profile Personal Message (Offline)

Ignore
1715170693
Reply with quote  #2

1715170693
Report to moderator
1715170693
Hero Member
*
Offline Offline

Posts: 1715170693

View Profile Personal Message (Offline)

Ignore
1715170693
Reply with quote  #2

1715170693
Report to moderator
1715170693
Hero Member
*
Offline Offline

Posts: 1715170693

View Profile Personal Message (Offline)

Ignore
1715170693
Reply with quote  #2

1715170693
Report to moderator
gateway
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
May 06, 2013, 01:00:52 AM
 #2

did you ever find a resolution to this?
BitcoinOxygen
Sr. Member
****
Offline Offline

Activity: 336
Merit: 250



View Profile WWW
May 06, 2013, 04:12:52 PM
 #3

did you ever find a resolution to this?

Yeah, He found a solution to this. He now runs a litecoin pool.

BTCOxygen PPS Mining Pool 2% Fee  <<<  Join Now
gateway
Hero Member
*****
Offline Offline

Activity: 552
Merit: 500


View Profile
May 06, 2013, 09:20:47 PM
 #4

did you ever find a resolution to this?

Yeah, He found a solution to this. He now runs a litecoin pool.

Mind sharing what you did to get the shares db populating, I see a lot of people having similar issues.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!