Topic: Pushpool - Tech Support - page 2. (Read 135232 times)

Im currently testing with 4000 KH/Sec... no a single share given for 30 min.

whats the uptime of the pool? I mean, how long have pushpool being running? it could take some time to get a share (like in p2pool) and probably as right now you are doing the same as solo mining could be that the hash rate is not enough and your are getting a long poll before actually sending any share

Well fixed the .pid file... still no shares in table shares in mysql database.

Problem is Pushpool is not generating shares... but only... how to fix  :@

If that file is not being generated one reason call be that the option doesnt exist or the name is wrong, that would be the usual.

For how long have you been running the pool? I supposse that your client is full synchronized so the problem is not that its still downloading the data hehe (happened to me )

Btw in bitcoind the option for the pid file is -pid as well in pushpool, you sure you have the right option?

Did you check this guide?

https://bitcointalksearch.org/topic/m.1867412

also if not shares are appearing in the minner then its not getting any :S did you try connecting the miner directly to the client as in solo and see if it receives shares? Im not sure how feathercoin works with the shares so Im a little bit at lost over there.

My guess is that pushpool is not actually getting shares so thats why is not logging them more of a problem with the call I would go for a problem of getting nothing to log hehe

My guess is that pushpool is not actually getting shares so thats why is not logging them more of a problem with the call I would go for a problem of getting nothing to log hehe

{
   "error": null,
   "result": {
      "target": "00000000000000000000000000000000000000000000000000a2170200000000",
      "midstate": "de93d5a64ac4c6ca5afae157a76c8bf295ad57ccbe5dd7af2f06e7a06ea214ac",
      "data": "000000014fb7d1e3eac4df9038891d48e375b3082913d0777035caa9c58738a8888683abbf082eb 3983120587b2e77b6836672f8849b9b7bbdc4ba6471ae1c9b1cfae8f951857b201c0217a2000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
      "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
      "algorithm": "scrypt:1024,1,1"
   },
   "id": 5
}

try removing this line:


Looks like that config is specific for bitcoins, should be 18 for ltc but not sure, I read about just removing it, could be preventing the pool from getting shares, btw, did you connect with a miner? does the miner receive shares?

quite strange, the problem i faced and fixed with the commit was similar but I was seeing the insert on the sql logs, let me do a little bit of research and I will be back in a few minutes.

server=1
daemon=1
rpcallowip=127.0.0.1
rpcport=9667
rpcuser=admin
rpcpass=****

Try this:

JSON protocol request:
{"method": "getwork", "params": [], "id":5}

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

< HTTP/1.1 200 OK
< Date: Sat, 04 May 2013 21:18:26 +0000
< Connection: keep-alive
< Content-Length: 622
< Content-Type: application/json
< Server: feathercoin-json-rpc/v0.6.3.0-g3aaa7ba-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "00000000000000000000000000000000000000000000000000a2170200000000",
      "midstate": "de93d5a64ac4c6ca5afae157a76c8bf295ad57ccbe5dd7af2f06e7a06ea214ac",
      "data": "000000014fb7d1e3eac4df9038891d48e375b3082913d0777035caa9c58738a8888683abbf082eb 3983120587b2e77b6836672f8849b9b7bbdc4ba6471ae1c9b1cfae8f951857b201c0217a2000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
      "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
      "algorithm": "scrypt:1024,1,1"
   },
   "id": 5
}

Not sure about the file logs but the DB problem can be fixed with a commit after the insert as I already explained before

{
        # 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" : 8332, "protocol" : "http-json",
                  "proxy" : "127.0.0.1" },

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

"sharelog" : true,

        # database settings
        "database" : {
                "engine" : "mysql",
                "host" : "localhost",
                "port" : 3306,
                "name" : "pool_user",
                "username" : "pool_user",
                "password" : "",
                "stmt.pwdb" : "SELECT `password` FROM `pool_worker` WHERE `username` = ?",
                "sharelog" : true,
                "stmt.sharelog" : "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?) COMMIT"

        },

        # 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/sharessss.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:9667/",
        "rpc.user" : "admin",
        "rpc.pass" : "----",

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

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

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

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

< HTTP/1.1 200 OK
< Date: Sun, 05 May 2013 14:22:55 +0000
< Connection: keep-alive
< Content-Length: 623
< Content-Type: application/json
< Server: feathercoin-json-rpc/v0.6.3.0-g3aaa7ba-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "00000000000000000000000000000000000000000000000000a2170200000000",
      "midstate": "f61c3632c6db16f6710e0ca8bd5ba3fd9c6dc9686ccab7a6717478999886984c",
      "data": "0000000172f0f7848d177618847be8d91bd724a745d762f5887d38395abc083204a2d53aa807b7c 266f0f167313daab9ebd6c284df30d0b24148a3a5a244a1e86e7c7ef351866b3c1c0217a2000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000",
      "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000",
      "algorithm": "scrypt:1024,1,1"
   },
   "id": 22
}