Bitcoin Forum
December 08, 2016, 11:53:03 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 »
  Print  
Author Topic: Pushpool - Tech Support  (Read 126764 times)
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
July 05, 2012, 06:12:53 PM
 #501

Code:
checking for pg_config... no
no
./configure: line 5740: syntax error near unexpected token `,'
./configure: line 5740: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'
someone help?

Your curl-devel (or libcurl-dev or whatever) package is missing the requisite autoconf macros needed to properly regenerate the configure script.


Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
1481197983
Hero Member
*
Offline Offline

Posts: 1481197983

View Profile Personal Message (Offline)

Ignore
1481197983
Reply with quote  #2

1481197983
Report to moderator
1481197983
Hero Member
*
Offline Offline

Posts: 1481197983

View Profile Personal Message (Offline)

Ignore
1481197983
Reply with quote  #2

1481197983
Report to moderator
1481197983
Hero Member
*
Offline Offline

Posts: 1481197983

View Profile Personal Message (Offline)

Ignore
1481197983
Reply with quote  #2

1481197983
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Greedi
Sr. Member
****
Offline Offline

Activity: 266


LitecoinTalk


View Profile WWW
July 05, 2012, 06:32:48 PM
 #502

just installed it, still get the same errors

LitecoinTalk - Sign up today!
Try out LTC-Aarade!
Buy Shares!
Greedi
Sr. Member
****
Offline Offline

Activity: 266


LitecoinTalk


View Profile WWW
July 05, 2012, 07:12:46 PM
 #503

Code:
checking for pg_config... no
no
./configure: line 5740: syntax error near unexpected token `,'
./configure: line 5740: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,'
someone help?

Your curl-devel (or libcurl-dev or whatever) package is missing the requisite autoconf macros needed to properly regenerate the configure script.



t@69-248:/pushpool# apt-get install libcurl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcurl-dev is a virtual package provided by:
  libcurl4-openssl-dev 7.21.0-2.1+squeeze2
  libcurl4-gnutls-dev 7.21.0-2.1+squeeze2
You should explicitly select one to install.

E: Package 'libcurl-dev' has no installation candidate

i installed both

LitecoinTalk - Sign up today!
Try out LTC-Aarade!
Buy Shares!
Greedi
Sr. Member
****
Offline Offline

Activity: 266


LitecoinTalk


View Profile WWW
July 05, 2012, 09:16:18 PM
 #504

ok, i got it fixed, and now it should be fine, but when i connect my miner i get

in pushpool
Code:
[2012-07-05 21:15:13.440003] client host ::ffff:199.26.85.34 port 58177 connected
[2012-07-05 21:15:41.648995] client host ::ffff:199.26.85.34 port 58178 connected
in minerd
Code:
[2012-07-05 23:16:05] HTTP request failed: Recv failure: Connection was reset
[2012-07-05 23:16:05] json_rpc_call failed, retry after 30 seconds

LitecoinTalk - Sign up today!
Try out LTC-Aarade!
Buy Shares!
Greedi
Sr. Member
****
Offline Offline

Activity: 266


LitecoinTalk


View Profile WWW
July 05, 2012, 11:40:04 PM
 #505

ok, got that part to working also now, i geting shares and al that, but it not sending it to the sql db?

LitecoinTalk - Sign up today!
Try out LTC-Aarade!
Buy Shares!
maxcarjuzaa
Full Member
***
Offline Offline

Activity: 179


View Profile
July 15, 2012, 05:25:20 PM
 #506

Hi there, I need some help if you are so kind.

I have the sw running but my miner is running at half speed compared to when it connects to other pool and i am not finding any share.

I have the Artforz version for litecoin

Here is the server side


~/pool/sbin$ ./pushpoold -E -F -D 2
[2012-07-15 17:16:3.004533] Debug output enabled
[2012-07-15 17:16:3.015238] Forcing local hostname to localhost.localdomain
[2012-07-15 17:16:3.040686] Listening on host :: port 8342
[2012-07-15 17:16:3.047742] Listening on host :: port 8341
[2012-07-15 17:16:3.051543] Listening on host :: port 8344
[2012-07-15 17:16:3.056850] Listening on host 127.0.0.1 port 8338
[2012-07-15 17:16:3.090090] initialized
JSON protocol request:
{"method": "getwork", "params": [], "id":1}

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

< HTTP/1.1 200 OK
< Date: Sun, 15 Jul 2012 17:16:10 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: litecoin-json-rpc/v0.6.3-6-g8148a30-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "0000000000000000000000000000000000000000000000000000852b00000000",
      "midstate": "5728c8adecd466a51aa699136798538aa42620ec633f9f6749aeee6ef3279c61",
      "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
      "data": "000000011cc1d46de8b568618a3fce07166e8b610dd0fdcb6ab759f4a6fbb8fb5917e4093823f5c 33ecb6e3643b6542a4dd76360d94ccf8d64f79f796908d6886714ea2f5002fad91c2b8500000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000"
   },
   "id": 1
}
[2012-07-15 17:16:10.446854] new block, target 0000000000000000000000000000000000000000000000000000852b00000000
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* Re-using existing connection! (#0) with host 127.0.0.1
* Connected to 127.0.0.1 (127.0.0.1) port 8332 (#0)
* Server auth using Basic with user 'notecuesta'
> POST / HTTP/1.1
Authorization: Basic bm90ZWN1ZXN0YTpuYWRhbmFkYSYm
Host: 127.0.0.1:8332
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

< HTTP/1.1 200 OK
< Date: Sun, 15 Jul 2012 17:17:08 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: litecoin-json-rpc/v0.6.3-6-g8148a30-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "0000000000000000000000000000000000000000000000000000852b00000000",
      "midstate": "de4f05f1c4b5842dbbf91924288cae7044eafcf9e6d67112b3c0a8ccd8813d24",
      "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
      "data": "000000011cc1d46de8b568618a3fce07166e8b610dd0fdcb6ab759f4a6fbb8fb5917e4096874ddd 244d3457092c0e2c68f59153074d5e15f6260649eac7c441bf9e0b5da5002fb131c2b8500000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000"
   },


This is the miner side

[2012-07-15 14:16:10] 2 miner threads started, using 'scrypt' algorithm.
[2012-07-15 14:16:10] Binding thread 1 to cpu 1
[2012-07-15 14:16:10] Binding thread 0 to cpu 0
[2012-07-15 14:16:10] Long-polling activated for http://192.168.1.101:8341/LP
[2012-07-15 14:16:12] thread 1: 4096 hashes, 2.19 khash/s
[2012-07-15 14:16:12] thread 0: 4096 hashes, 2.08 khash/s
[2012-07-15 14:17:08] thread 0: 120494 hashes, 2.16 khash/s
[2012-07-15 14:17:09] thread 1: 127023 hashes, 2.21 khash/s


This is my server.json file

{
        # 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" : 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" : "pushpool",
                "username" : "pushpool",
                "password" : "j5kIK&_/H4rf",
                "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:8332/",
        "rpc.user" : "pushpool",
        "rpc.pass" : "ujK_.[}w6sj/kd3&",

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




Any ideas?


Thank you!!!

Max
Tittiez
Hero Member
*****
Offline Offline

Activity: 686



View Profile
July 24, 2012, 05:02:33 AM
 #507

I have libmysqlclient-dev (mysql-devel) installed, but I am still recieving this error:
Code:
server.c:106:2: error: #error ("No valid database engines defined")
make[1]: *** [server.o] Error 1
make[1]: Leaving directory `/home/tittiez/pushpool'
make: *** [all] Error 2
Any help?

Edit:

Nevermind I had to configure again.
NothinG
Hero Member
*****
Offline Offline

Activity: 560



View Profile
August 20, 2012, 05:05:07 PM
 #508

Code:
root@mein:~/ppool# sudo ./pushpoold -E -D 2
[2012-08-20 16:59:53.121413] Debug output enabled
[2012-08-20 16:59:53.121687] Forcing local hostname to localhost.localdomain
root@mein:~/ppool# [2012-08-20 16:59:53.126800] Listening on host :: port 9942
[2012-08-20 16:59:53.126874] Listening on host :: port 9941
[2012-08-20 16:59:53.126924] Listening on host :: port 9944
[2012-08-20 16:59:53.126957] Listening on host 127.0.0.1 port 9938
root@mein:~/ppool#

I've been at this since last night and went through this whole thread looking for answers.

I'm trying to get Pushpoold to work with an alternative Crypt-Currency, but am not having any luck getting it to initialize.
The alt currency is the same format as Bitcoin (with RPC commands and everything).

I made sure the DB, RPC, as well as the file permission/locations where correct.

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

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

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

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

        # database settings
        "database" : {
                "engine" : "mysql",
                "host" : "localhost",
                "port" : 3306,
                "name" : "*",
                "username" : "*",
                "password" : "*",
                "sharelog" : true,
                "stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_resul$

        },

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

        "pid" : "/root/pushpoold.pid",

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

        "log.requests" : "/root/request.log",
        "log.shares" : "/root/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 numbe$
        "rpc.url" : "http://127.0.0.1:9932/",
        "rpc.user" : "*",
        "rpc.pass" : "*",

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

}

Pontius
Full Member
***
Offline Offline

Activity: 225


View Profile
August 21, 2012, 06:41:26 AM
 #509

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

Activity: 560



View Profile
August 21, 2012, 06:42:40 AM
 #510

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
Newbie
*
Offline Offline

Activity: 8


View Profile
September 17, 2012, 02:45:29 AM
 #511

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! Smiley

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. Tongue  -- 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! Smiley

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

Activity: 8


View Profile
September 17, 2012, 10:32:19 PM
 #512

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

Pool service should be starting sometime today! Smiley
BTCMiners.net
Sr. Member
****
Offline Offline

Activity: 252



View Profile WWW
September 26, 2012, 08:11:04 AM
 #513

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

Buy Cloud Hashing! $8.50 USD per GH/s!  [32.231 TH/s] Remaining
https://bitcointalk.org/index.php?topic=329674.20  -- www.BTCMiners.net
c4n10
Sr. Member
****
Offline Offline

Activity: 294



View Profile
March 22, 2013, 07:19:40 PM
 #514

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
Sr. Member
****
Offline Offline

Activity: 294



View Profile
March 22, 2013, 07:30:55 PM
 #515

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
Sr. Member
****
Offline Offline

Activity: 294



View Profile
March 22, 2013, 09:55:10 PM
 #516

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
Sr. Member
****
Offline Offline

Activity: 294



View Profile
March 22, 2013, 11:33:57 PM
 #517

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
Sr. Member
****
Offline Offline

Activity: 294



View Profile
March 28, 2013, 11:11:09 PM
 #518

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

Activity: 798


www.multipool.us


View Profile
April 01, 2013, 06:13:30 AM
 #519

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..

Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
Xenland
Legendary
*
Offline Offline

Activity: 980


I'm not just any shaman, I'm a Sha256man


View Profile
April 01, 2013, 07:50:37 AM
 #520

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 Smiley
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!