Bitcoin Forum
December 04, 2016, 01:58:13 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 126680 times)
gateway
Hero Member
*****
Offline Offline

Activity: 504


View Profile
May 02, 2013, 09:08:34 PM
 #541

Pushpool newbie and thanks for creating this hope you add to it..

I was unsable to see where the mysql data base tables are for setting up the db.. the only thing I have is the pool worker which has user and pass.. in the github section I didnt see any .sql files or missed anything about table creation..

next issue.. I have bitcoind running, and have pushpull running as far as I can tell, Im connecting cgminer to my pool via

cgminer -o 172.18.251.190:8337 -u abc -p 123  (this is whats in the push pull db)

In the pushpull log im seeing:

Code:
> POST / HTTP/1.1
Authorization: Basic xxxxxxxxxxxxxxxxx
Host: 127.0.0.1:8332
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 46

* HTTP 1.0, assume close after body
< HTTP/1.0 401 Authorization Required
< Date: Thu, 02 May 2013 21:31:16 +0000
< Server: bitcoin-json-rpc/v0.8.1.0-g34d62a8-beta
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="jsonrpc"
< Content-Type: text/html
< Content-Length: 296
* The requested URL returned error: 401
* Closing connection #0

my server.json is

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

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

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

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

        # 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" : "pushpool",
                "username" : "root",
                "password" : "12345678",

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

        # 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
        "rpc.url" : "http://127.0.0.1:8332/",
        "rpc.user" : "mybitcoinduser",
        "rpc.pass" : "mybitcoindpass",

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

        # allow clients to update the ntime field of their work

btc config is

Code:
server=1
daemon=1
rpcallowip=*
rpcuser=mybitcoinduser
rpcpassword=mybitcoindpass

any thoughts? :?

// Pepper Mining Co. - The Habanero
// Eligius.st - Webmaster
// Donations: btc 1D5K2WV1K4uiv56vZyMS66gBCPYVEdy6v
1480816693
Hero Member
*
Offline Offline

Posts: 1480816693

View Profile Personal Message (Offline)

Ignore
1480816693
Reply with quote  #2

1480816693
Report to moderator
1480816693
Hero Member
*
Offline Offline

Posts: 1480816693

View Profile Personal Message (Offline)

Ignore
1480816693
Reply with quote  #2

1480816693
Report to moderator
1480816693
Hero Member
*
Offline Offline

Posts: 1480816693

View Profile Personal Message (Offline)

Ignore
1480816693
Reply with quote  #2

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

Posts: 1480816693

View Profile Personal Message (Offline)

Ignore
1480816693
Reply with quote  #2

1480816693
Report to moderator
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 02, 2013, 09:13:50 PM
 #542

Can you post the whole log from pushpool? do you see the intialized message?

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
gateway
Hero Member
*****
Offline Offline

Activity: 504


View Profile
May 02, 2013, 10:04:49 PM
 #543

Code:
netcom@u12:/opt/pushpool$ /opt/pushpool/sbin/pushpoold --debug=2 --config server.json --stderr --foreground
[2013-05-02 21:13:12.728423] Debug output enabled
[2013-05-02 21:13:12.729447] Forcing local hostname to localhost.localdomain
[2013-05-02 21:13:12.734267] Listening on host :: port 8336
[2013-05-02 21:13:12.734667] Listening on host :: port 8337
[2013-05-02 21:13:12.738452] initialized
[2013-05-02 21:14:22.856040] client host ::ffff:172.18.1.240 port 55619 connected
[2013-05-02 21:14:22.856165] client ::ffff:172.18.1.240 ended
[2013-05-02 21:14:22.856742] client host ::ffff:172.18.1.240 port 55620 connected
[2013-05-02 21:14:22.856942] client ::ffff:172.18.1.240 ended
[2013-05-02 21:14:22.857587] client host ::ffff:172.18.1.240 port 55621 connected
[2013-05-02 21:14:22.857653] client ::ffff:172.18.1.240 ended
[2013-05-02 21:14:24.929252] client host ::ffff:172.18.1.240 port 55629 connected
[2013-05-02 21:14:24.929353] client ::ffff:172.18.1.240 ended
[2013-05-02 21:14:24.929847] client host ::ffff:172.18.1.240 port 55630 connected
[2013-05-02 21:14:24.939533] client ::ffff:172.18.1.240 ended
[2013-05-02 21:14:24.940080] client host ::ffff:172.18.1.240 port 55631 connected
[2013-05-02 21:14:24.940147] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:33.795761] client host ::ffff:172.18.1.240 port 55663 connected
[2013-05-02 21:16:33.795870] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:33.796711] client host ::ffff:172.18.1.240 port 55664 connected
[2013-05-02 21:16:33.797012] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:33.797626] client host ::ffff:172.18.1.240 port 55665 connected
[2013-05-02 21:16:33.797692] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:35.879581] client host ::ffff:172.18.1.240 port 55673 connected
[2013-05-02 21:16:35.879690] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:35.880525] client host ::ffff:172.18.1.240 port 55674 connected
[2013-05-02 21:16:35.880594] client ::ffff:172.18.1.240 ended
[2013-05-02 21:16:35.881230] client host ::ffff:172.18.1.240 port 55675 connected
[2013-05-02 21:16:35.881296] client ::ffff:172.18.1.240 ended
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 'userbitcoind'
> POST / HTTP/1.1
Authorization: Basic Z2sfsdf
Host: 127.0.0.1:8332
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

* HTTP 1.0, assume close after body
< HTTP/1.0 401 Authorization Required
< Date: Thu, 02 May 2013 21:18:17 +0000
< Server: bitcoin-json-rpc/v0.8.1.0-g34d62a8-beta
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="jsonrpc"
< Content-Type: text/html
< Content-Length: 296
* The requested URL returned error: 401
* Closing connection #0
[2013-05-02 21:18:17.067743] HTTP request failed: The requested URL returned error: 401
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* 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 'userbitcoind'
> POST / HTTP/1.1
Authorization: Basic Zsdff
Host: 127.0.0.1:8332
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

* HTTP 1.0, assume close after body
< HTTP/1.0 401 Authorization Required
< Date: Thu, 02 May 2013 21:18:18 +0000
< Server: bitcoin-json-rpc/v0.8.1.0-g34d62a8-beta
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="jsonrpc"
< Content-Type: text/html
< Content-Length: 296
* The requested URL returned error: 401
* Closing connection #0
[2013-05-02 21:18:18.984823] HTTP request failed: The requested URL returned error: 401
JSON protocol request:
{"method": "getwork", "params": [], "id":3}

// Pepper Mining Co. - The Habanero
// Eligius.st - Webmaster
// Donations: btc 1D5K2WV1K4uiv56vZyMS66gBCPYVEdy6v
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 03, 2013, 01:20:06 PM
 #544

looks like your pushpool cant connect to bitcoind, are you running bitcoind (already synchronized) before pushpool?

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
gateway
Hero Member
*****
Offline Offline

Activity: 504


View Profile
May 03, 2013, 05:12:58 PM
 #545

looks like your pushpool cant connect to bitcoind, are you running bitcoind (already synchronized) before pushpool?

its resolved... my rpc password for bitcoin.conf and server.json some reason had some weird random chrs in it that would cause auth to not happen.. ..


// Pepper Mining Co. - The Habanero
// Eligius.st - Webmaster
// Donations: btc 1D5K2WV1K4uiv56vZyMS66gBCPYVEdy6v
gateway
Hero Member
*****
Offline Offline

Activity: 504


View Profile
May 03, 2013, 05:13:42 PM
 #546

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

I see this a lot, and with simplecoin I see this shares db, but for some reason im not getting any inserts, is this query wrong, how can this be debugged.. ?

// Pepper Mining Co. - The Habanero
// Eligius.st - Webmaster
// Donations: btc 1D5K2WV1K4uiv56vZyMS66gBCPYVEdy6v
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 03, 2013, 06:03:39 PM
 #547

Same problem as with the insert in networkBlocks, add a COMMIT call to the SQL server after the insert, it should work then.

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 02:42:30 AM
 #548

Hello miners...
Having an issue with pushpool and FeatherCoin...

Running Debian all packages and requirements installed.
Pushpool checks worker login from Mysql DB correctly but does not write share to the Database or to the shares.log file in /tmp/

I do not get any errors when starting pushpoold with -E -F --debug=2

Already reinstalled the server same issue :@

When I setup a LTC pool with pushpool no issues ...
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 02:07:09 PM
 #549

What could be the issue when PushPool can check worker user/pass from DB but does not write shares to DB or to /tmp/shares.log?

Pushpool successfully executes this query:
Quote
"stmt.pwdb" : "SELECT `password` FROM `pool_worker` WHERE `username` = ?",

Pushpool is not excuting this query:
Quote
"stmt.sharelog" : "INSERT INTO  `pool_user`.`shares` (`rem_host` ,`username` ,`our_result` ,`upstream_result` ,`reason` ,`solution`)VALUES (?, ?, ?, ?, ?, ?)"

Also /tmp/shares.log empty!

Quote
* 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
}


Im lost Smiley

KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 05:29:09 PM
 #550

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

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 05:38:22 PM
 #551

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

I still have an empty shares table...

Quote
{
        # 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
}
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 05:41:46 PM
 #552

Try this:

Code:
"stmt.sharelog" : "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?); COMMIT;"

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 05:46:13 PM
 #553

Try this:

Code:
"stmt.sharelog" : "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?); COMMIT;"

Same results:

My ./pushpoold -E -F --debug=2 gives back shares... Only they are not writting into the database...

When I tail my mysql query logs, i see the select query for worker authentification but not the insert query...

Quote
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
}

Also, mysql database user has INSERT access...

It seems "stmt.sharelog" is not being executed by pushpool. I have removed the extra "sharelog" : true, as that was a test... but fact that the select query is executed and the INSERT is not im puzzled.. Also I reinstalled the entire server already same results...

KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 05:55:12 PM
 #554

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.

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 06:02:22 PM
 #555

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.

Sure few questions:
Did you start your LTC of Feathercoin daemon with -pollpidfile=/tmp/pushpoold.pid ?

My feathercoin.conf
Quote
server=1
daemon=1
rpcallowip=127.0.0.1
rpcport=9667
rpcuser=admin
rpcpass=****

I dont think it will be at the side of the feathercoind...

strange thing is that when I edit the "stmt.pwdb" : to an INSERT query, there are rows written into the database... But those are bullshit ofcourse Smiley

KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 06:05:35 PM
 #556

try removing this line:

Code:
"rpc.target.bits" : 32

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?


If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 06:06:36 PM
 #557

try removing this line:

Code:
"rpc.target.bits" : 32

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?



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

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 06:14:09 PM
 #558

try removing this line:

Code:
"rpc.target.bits" : 32

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?



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

Debug window shows share:

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

This i a Feathercoin pool... My LTC pool runs with rpc.target.bits : 20 just fine...

I though that it could be feathercoin related, then I also installed litecoin on the server waited for blocks to sync, and had the same issue... Then I reinstalled everything still same issue Smiley



OversightNL
Jr. Member
*
Offline Offline

Activity: 56


View Profile
May 05, 2013, 06:16:21 PM
 #559

try removing this line:

Code:
"rpc.target.bits" : 32

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?



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

Also one miner is connected with 1100 Kh/Sec.. no shares are giving... 0:0 shares
KALRONG
Jr. Member
*
Offline Offline

Activity: 52



View Profile WWW
May 05, 2013, 06:19:55 PM
 #560

Did you check this guide?

https://bitcointalk.org/index.php?topic=178286.msg1867412#msg1867412

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.

If I helped you feel free to donate any quantity, it will help me continuing to be able to test and improve things Smiley

BTC:  1HAKsmg8ZrXwydBfAh4VNTp
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!