Bitcoin Forum
December 05, 2016, 08:49:30 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]
  Print  
Author Topic: Pooshpoold seems to be working, minerd connects but cannot find a single share  (Read 1472 times)
maxcarjuzaa
Full Member
***
Offline Offline

Activity: 179


View Profile
July 20, 2012, 01:42:30 AM
 #1

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

I have pushpoold running but I am not finding any share with minerd.

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

Posts: 1480927770

View Profile Personal Message (Offline)

Ignore
1480927770
Reply with quote  #2

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

Posts: 1480927770

View Profile Personal Message (Offline)

Ignore
1480927770
Reply with quote  #2

1480927770
Report to moderator
pooler
Hero Member
*****
Offline Offline

Activity: 644


View Profile
July 20, 2012, 02:22:52 AM
 #2

The target isn't being rewritten appropriately. Use the example configuration file distributed with ArtForz's fork and set rpc.target.bits to something like 18.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
burnside
Hero Member
*****
Offline Offline

Activity: 882



View Profile WWW
July 20, 2012, 05:51:22 PM
 #3

I ended up using alexhz's version.  https://github.com/alexhz/pushpool

pooler, you're a pro.  what are the pro's and con's of alexhz's vs artforz'?

I'm not a Coinbase fan -- I placed a buy order, they took the funds out of my account, then a week later the price went up and they canceled the buy and closed my account.  You've been warned.  Use a different exchange.
pooler
Hero Member
*****
Offline Offline

Activity: 644


View Profile
July 20, 2012, 06:35:42 PM
 #4

ArtForz's fork is easier to setup, as it doesn't require external notification for long polling, and has a configurable share target.
alexhz's fork includes Cryptomaniac's patches, which for instance add support for local work generation. On the other hand, long polling needs to be setup as in the original pushpool, and the share target is fixed.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
burnside
Hero Member
*****
Offline Offline

Activity: 882



View Profile WWW
July 20, 2012, 06:57:08 PM
 #5

ArtForz's fork is easier to setup, as it doesn't require external notification for long polling, and has a configurable share target.
alexhz's fork includes Cryptomaniac's patches, which for instance add support for local work generation. On the other hand, long polling needs to be setup as in the original pushpool, and the share target is fixed.

Thank you, appreciate the input!

Making sure I'm understanding this correctly, the alexhz version takes the work generation load off litecoind?

But the artforz version you can reduce the load by altering the share target?  (and thus processing less shares/second)



I'm not a Coinbase fan -- I placed a buy order, they took the funds out of my account, then a week later the price went up and they canceled the buy and closed my account.  You've been warned.  Use a different exchange.
pooler
Hero Member
*****
Offline Offline

Activity: 644


View Profile
July 20, 2012, 07:03:48 PM
 #6

ArtForz's fork is easier to setup, as it doesn't require external notification for long polling, and has a configurable share target.
alexhz's fork includes Cryptomaniac's patches, which for instance add support for local work generation. On the other hand, long polling needs to be setup as in the original pushpool, and the share target is fixed.

Thank you, appreciate the input!

Making sure I'm understanding this correctly, the alexhz version takes the work generation load off litecoind?

But the artforz version you can reduce the load by altering the share target?  (and thus processing less shares/second)

Yes and yes.

BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
maxcarjuzaa
Full Member
***
Offline Offline

Activity: 179


View Profile
July 22, 2012, 01:40:52 PM
 #7

Thank you all pool up un running!
wknight
Legendary
*
Offline Offline

Activity: 889


Bitcoin calls me an Orphan


View Profile WWW
July 22, 2012, 01:48:21 PM
 #8

Congrats!

Mining Both Bitcoin and Litecoin.
Pages: [1]
  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!