Bitcoin Forum
December 06, 2016, 08:15:42 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   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 126736 times)
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
August 13, 2011, 03:38:34 PM
 #461

I've found about every 24 hours or so pushpoold will "lock up" and stop responding to everything. a killall -HUP doesn't help, I have to kill it and restart it and then everything works fine again. It's getting really bad. Does anyone have any tips?

Check "netstat -au"  and see how many TIME_WAIT handles you have open.  If that number exceeds your ufile limit, that would be why.

However, in my case, I implemented a patch to fix that problem and I'm still seeing it.

I think the RPC multithreading has some issues - I've observed that every once in awhile, it matches the wrong response to an outgoing request.
1481055342
Hero Member
*
Offline Offline

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

1481055342
Report to moderator
1481055342
Hero Member
*
Offline Offline

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

1481055342
Report to moderator
1481055342
Hero Member
*
Offline Offline

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

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

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

1481055342
Report to moderator
1481055342
Hero Member
*
Offline Offline

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

1481055342
Report to moderator
1481055342
Hero Member
*
Offline Offline

Posts: 1481055342

View Profile Personal Message (Offline)

Ignore
1481055342
Reply with quote  #2

1481055342
Report to moderator
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
August 13, 2011, 03:43:08 PM
 #462



Hey guys,

Was wondering if you came across this before, my miner tries to connect but doesn't get any work. I can see when miner connects but get the following:

Connecting my miner.

Quote
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
* Connected to 127.0.0.1 (127.0.0.1) port 8333 (#0)
* Server auth using Basic with user 'username'
> POST / HTTP/1.1
Authorization: Basic enRqdWg6dGVzdDEyMw==
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
[2011-07-14 01:27:16.074094] HTTP request failed: Empty reply from server
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* Connection #0 seems to be dead!
* Closing connection #0
* About to connect() to 127.0.0.1 port 8333 (#0)
*   Trying 127.0.0.1... * TCP_NODELAY set
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8333 (#0)
* Server auth using Basic with user 'username'
> POST / HTTP/1.1
Authorization: Basic enRqdWg6dGVzdDEyMw==
Host: 127.0.0.1:8333
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45


Any ideas what you think could be wrong?

Thanks in advance!

Cheers,
Wes.

I think it would be one of two things:

1. You're using the wrong bitcoin RPC credentials (I don't think so - you'd be seeing a 401 Authorization Required response) -
2. Pushpool is connecting on the wrong port. That's likely the problem. Make sure the rpc port specific in server.json is the same as the rpcport specified in bitcoin.conf.

Also make sure pushpool isn't listening on any ports that are the same as the bitcoin rpc port.
wezzy
Jr. Member
*
Offline Offline

Activity: 31


View Profile WWW
August 15, 2011, 01:25:13 AM
 #463



Thanks mate! I will give it a try and let you know. Cheers for the info.

Wes.

GPUTECH.NET 1% fee/LP/SSL/PPLNS/API/ Instant/Auto Payout /

JOIN NOW - https://www.gputech.net/register.php
Keninishna
Hero Member
*****
Offline Offline

Activity: 551



View Profile WWW
August 26, 2011, 05:52:41 AM
 #464

On my ubuntu server I got pushpoold compiled and installed but when I try to run it, it says can't locate libevent.so.5 file not found. I installed libevent according to the guide, I also found there is a shortcut for it in /usr/local/lib I'm not too sure what to do. I went into /etc/ld.so.conf and added a line "include /usr/local/lib/*.*" no go. Maybe i'm just being a linux noob  Roll Eyes
simplecoin
Sr. Member
****
Offline Offline

Activity: 406



View Profile WWW
August 26, 2011, 07:03:33 AM
 #465

On my ubuntu server I got pushpoold compiled and installed but when I try to run it, it says can't locate libevent.so.5 file not found. I installed libevent according to the guide, I also found there is a shortcut for it in /usr/local/lib I'm not too sure what to do. I went into /etc/ld.so.conf and added a line "include /usr/local/lib/*.*" no go. Maybe i'm just being a linux noob  Roll Eyes

just run: sudo apt-get install libevent-dev

Donations: 1VjGJHPtLodwCFBDWsHJMdEhqRcRKdBQk
Keninishna
Hero Member
*****
Offline Offline

Activity: 551



View Profile WWW
August 26, 2011, 07:17:09 AM
 #466

I ran export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
and that fixed it. But I'll run that too.
Vadtec
Newbie
*
Offline Offline

Activity: 15


View Profile
August 31, 2011, 02:20:16 AM
 #467

Sorry, missed this one. We're multi-threading a single thread. Hah! Smiley

1. Correct mode = up to you. Strictly speaking there's no need to record the failed shares. They are useful for paying out for pool participation, though Smiley In which case the correct mode = true.
2. Yes
3. I've made the same observation. Even when I know the load is sufficient to produce a value, "gethashespersec" always returns 0.  Must be a bug in bitcoin, but one I haven't bothered to track down. The solution I've seen to this exists within the MiningFarm and SimpleCoin pool frontends - essentially they make the following calculation:

* Count all current shares (or shares over a selected time range)
* hashrate = round(((NUMSHARES*4294967296)/600)/1000000, 0);

The magic numbers are:

4294967296 = hashes/share.  When multiplied by shares, gives you a total count of hashes. I'm assuming this magic number is correct; I haven't personally verified it.
600 = seconds in 10 minutes. You'd change this according to your time window. The division here gives you "hashes/sec".
1000000 = hashes/sec to Mhash/s.   Technically I think that number should be 1048576 (1024^2) to fit the strict definition of "mega", but I wouldn't be a stickler about it.  And it would deflate the apparent hash rate.

Late reply I know, but, thanks for the response.


Find my post useful? Send me a few bitcent @ 1NFBQg4fMpZoP2UEE2CnSyFDdNVy5fSrqc
bully
Newbie
*
Offline Offline

Activity: 14


View Profile
August 31, 2011, 01:24:02 PM
 #468

I'm also stuck at pushpool configuration. I read through the whole thread and the only solution to get rid of the error messages when connecting a miner is to have the rpc port (pushpool) pointing to the rpcport configured in bitcoin.conf.

However when i connect my miner I get error 500.
Quote
root@bully:/home/pushpool/sbin# ./pushpoold -E -F
[2011-08-29 22:03:43.948838] Listening on host :: port 8342
[2011-08-29 22:03:43.949297] Listening on host :: port 8341
[2011-08-29 22:03:43.949385] Listening on host :: port 8334
[2011-08-29 22:03:43.949513] Listening on host 127.0.0.1 port 8338
[2011-08-29 22:03:43.976058] initialized
[2011-08-29 22:03:46.627102] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:47.673728] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:48.752518] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:49.827042] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:50.948836] HTTP request failed: The requested URL returned error: 500

When I connect to port 8333 I get "empty reply from server":

Quote
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
[2011-08-31 13:04:1.015652] HTTP request failed: Empty reply from server
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* Connection #0 seems to be dead!
* Closing connection #0
* About to connect() to 127.0.0.1 port 8333 (#0)
*   Trying 127.0.0.1... * TCP_NODELAY set
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8333 (#0)
* Server auth using Basic with user 'hidden'
> POST / HTTP/1.1
Authorization: Basic Zm9jazphbG90dA==
Host: 127.0.0.1:8333
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

these are my config files:

bitcoin.conf
Quote
server=1
rpcuser=hidden
rpcpassword=morehidden
rpcallowip=127.0.0.1
rpcport=8332
gen=0

server.json
Quote
{
        # network ports
        "listen" : [
                # binary protocol (default), port 8342
                { "port" : 8342 },

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

                # HTTP JSON-RPC protocol, port 8344,
                # with trusted proxy appserver.example.com forwarding
                # requests to us
                { "port" : 8334, "protocol" : "http-json",
                  "proxy" : "my.external.ip.addr" },

                # 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" : "bitcoin",
                "username" : "blablablasabsa",
                "password" : "blablablasabsa",
                "sharelog" : true,
                "stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, sol$

        },
        # 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 b$
        "rpc.url" : "http://127.0.0.1:8333/",
        "rpc.user" : "hidden",
        "rpc.pass" : "morehidden",

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

some lines are cut by "$" because i copied/paste it from a text editor, but those shouldn't be interesting...

bitcoind runs as normal user, and I'm able to connect my miner directly to bitcoind (using rpcuser and rpcpass).
pushpool and bitcoind run on the same machine.

some more debug output:
Quote
root@bully:~# lsof -i :8332
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bitcoind 3248 user   14u  IPv4  27381      0t0  TCP *:8332 (LISTEN)
root@bully:~# lsof -i :8333
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bitcoind  3248 user    6u  IPv4  27375      0t0  TCP *:8333 (LISTEN)

Quote
mysql> show tables;
+-------------------+
| Tables_in_bitcoin |
+-------------------+
| pool_worker       |
| shares            |
+-------------------+
2 rows in set (0.00 sec)

mysql> describe pool_worker;
+------------------+-------------+------+-----+---------+----------------+
| Field            | Type        | Null | Key | Default | Extra          |
+------------------+-------------+------+-----+---------+----------------+
| id               | int(25)     | NO   | PRI | NULL    | auto_increment |
| associatedUserId | int(25)     | NO   |     | NULL    |                |
| username         | varchar(50) | YES  | UNI | NULL    |                |
| password         | varchar(60) | YES  |     | NULL    |                |
+------------------+-------------+------+-----+---------+----------------+
4 rows in set (0.25 sec)

mysql> select * from pool_worker;
+--------+------------------+----------+-------------+
| id     | associatedUserId | username | password    |
+--------+------------------+----------+-------------+
| 100000 |              100 | bully    | mypassword |
+--------+------------------+----------+-------------+
1 row in set (0.02 sec)

the password is stored unencrypted in the table.

any help is appreciated :-/
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
August 31, 2011, 05:44:25 PM
 #469

I'm also stuck at pushpool configuration. I read through the whole thread and the only solution to get rid of the error messages when connecting a miner is to have the rpc port (pushpool) pointing to the rpcport configured in bitcoin.conf.

However when i connect my miner I get error 500.
Quote
root@bully:/home/pushpool/sbin# ./pushpoold -E -F
[2011-08-29 22:03:43.948838] Listening on host :: port 8342
[2011-08-29 22:03:43.949297] Listening on host :: port 8341
[2011-08-29 22:03:43.949385] Listening on host :: port 8334
[2011-08-29 22:03:43.949513] Listening on host 127.0.0.1 port 8338
[2011-08-29 22:03:43.976058] initialized
[2011-08-29 22:03:46.627102] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:47.673728] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:48.752518] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:49.827042] HTTP request failed: The requested URL returned error: 500
[2011-08-29 22:03:50.948836] HTTP request failed: The requested URL returned error: 500

When I connect to port 8333 I get "empty reply from server":

Quote
* Empty reply from server
* Connection #0 to host 127.0.0.1 left intact
[2011-08-31 13:04:1.015652] HTTP request failed: Empty reply from server
JSON protocol request:
{"method": "getwork", "params": [], "id":2}

* Connection #0 seems to be dead!
* Closing connection #0
* About to connect() to 127.0.0.1 port 8333 (#0)
*   Trying 127.0.0.1... * TCP_NODELAY set
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8333 (#0)
* Server auth using Basic with user 'hidden'
> POST / HTTP/1.1
Authorization: Basic Zm9jazphbG90dA==
Host: 127.0.0.1:8333
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

these are my config files:

bitcoin.conf
Quote
server=1
rpcuser=hidden
rpcpassword=morehidden
rpcallowip=127.0.0.1
rpcport=8332
gen=0

server.json
Quote
{
        # network ports
        "listen" : [
                # binary protocol (default), port 8342
                { "port" : 8342 },

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

                # HTTP JSON-RPC protocol, port 8344,
                # with trusted proxy appserver.example.com forwarding
                # requests to us
                { "port" : 8334, "protocol" : "http-json",
                  "proxy" : "my.external.ip.addr" },

                # 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" : "bitcoin",
                "username" : "blablablasabsa",
                "password" : "blablablasabsa",
                "sharelog" : true,
                "stmt.pwdb":"SELECT `password` FROM `pool_worker` WHERE `username` = ?",
                "stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, sol$

        },
        # 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 b$
        "rpc.url" : "http://127.0.0.1:8333/",
        "rpc.user" : "hidden",
        "rpc.pass" : "morehidden",

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

some lines are cut by "$" because i copied/paste it from a text editor, but those shouldn't be interesting...

bitcoind runs as normal user, and I'm able to connect my miner directly to bitcoind (using rpcuser and rpcpass).
pushpool and bitcoind run on the same machine.

--snip--

the password is stored unencrypted in the table.

any help is appreciated :-/

Your ports are all messed up.  Try this:

bitcoin.conf:
rpcport=8335 (just choosing something that isn't already taken and isn't 8332 or 8333)


server.json:
(at the bottom):
"rpc.url" : "http://127.0.0.1:8335/",

(at the top):
                # HTTP JSON-RPC protocol, port 8332
                #{ "port" : 8341, "protocol" : "http-json" },
                { "port" : 8332, "protocol" : "http-json" },

Now you'll expose 8332 to the internet via pushpool, and bitcoin/pushpool will communicate over 8335 on localhost.

That configuration should work for you.

Your miner is getting an empty reply from the server because it's trying to connect to bitcoin directly (rpcport=8332, remember?) Bitcoin only allows connections from localhost by default so it simply slams the connection shut.
bully
Newbie
*
Offline Offline

Activity: 14


View Profile
August 31, 2011, 06:06:58 PM
 #470

Your ports are all messed up.  Try this:

bitcoin.conf:
rpcport=8335 (just choosing something that isn't already taken and isn't 8332 or 8333)


server.json:
(at the bottom):
"rpc.url" : "http://127.0.0.1:8335/",

(at the top):
                # HTTP JSON-RPC protocol, port 8332
                #{ "port" : 8341, "protocol" : "http-json" },
                { "port" : 8332, "protocol" : "http-json" },

Now you'll expose 8332 to the internet via pushpool, and bitcoin/pushpool will communicate over 8335 on localhost.

That configuration should work for you.

Your miner is getting an empty reply from the server because it's trying to connect to bitcoin directly (rpcport=8332, remember?) Bitcoin only allows connections from localhost by default so it simply slams the connection shut.

I configured the ports as you told me, but i get error 500 nonetheless.
8335 in bitcoin.conf, 8335 rpc.url and connect the miner to the port i configured in HTTP JSON-RPC section

Quote
root@bully:/home/pushpool/sbin# ./pushpoold -E -F -D 2
[2011-08-31 18:04:18.021763] Debug output enabled
[2011-08-31 18:04:18.332918] Forcing local hostname to localhost.localdomain
[2011-08-31 18:04:18.754137] Listening on host :: port 8342
[2011-08-31 18:04:18.754284] Listening on host :: port 8341
[2011-08-31 18:04:18.754427] Listening on host :: port 8332
[2011-08-31 18:04:18.754526] Listening on host 127.0.0.1 port 8338
[2011-08-31 18:04:19.022037] initialized
JSON protocol request:
{"method": "getwork", "params": [], "id":1}

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

* The requested URL returned error: 500
* Closing connection #0
[2011-08-31 18:04:19.801483] HTTP request failed: The requested URL returned error: 500
Xenland
Legendary
*
Offline Offline

Activity: 980


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


View Profile
August 31, 2011, 11:19:23 PM
 #471

Just thought I'd like everyone to know that I got my first donation for 0.0005 BTC fromt this page thanks everyone for your contribution you've been a real help.
I mean yeah you all made your own pool and made tons of BTC and I'm really happy that I was even given this amount you guys are sooo giving

Tongue

Seriously tho, i got some lolz out of that donation.... that was donation enough!
bully
Newbie
*
Offline Offline

Activity: 14


View Profile
September 01, 2011, 10:21:43 PM
 #472

Just thought I'd like everyone to know that I got my first donation for 0.0005 BTC fromt this page thanks everyone for your contribution you've been a real help.
I mean yeah you all made your own pool and made tons of BTC and I'm really happy that I was even given this amount you guys are sooo giving

Tongue

Seriously tho, i got some lolz out of that donation.... that was donation enough!

isn't the satisfaction to have helped someone not donation enough?
Xenland
Legendary
*
Offline Offline

Activity: 980


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


View Profile
September 01, 2011, 11:14:31 PM
 #473

Honestly it doesn't matter at this point, before It would have helped to have a couple of Bitcents here and there at the time of writing the tutorials
bully
Newbie
*
Offline Offline

Activity: 14


View Profile
September 02, 2011, 09:09:57 AM
 #474

btw i was able to get it to work, with the configuration which gave me error 500 before.
maybe it doesn't work when the keychain isn't completley downloaded?
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
September 02, 2011, 12:11:44 PM
 #475

btw i was able to get it to work, with the configuration which gave me error 500 before.
maybe it doesn't work when the keychain isn't completley downloaded?
Ah, no it doesn't.  FYI during that period, if you submit any RPC requests to bitcoin directly via the command line it will respond with an error message saying the blockchain is currently downloading.
bully
Newbie
*
Offline Offline

Activity: 14


View Profile
September 02, 2011, 12:40:26 PM
 #476

btw i was able to get it to work, with the configuration which gave me error 500 before.
maybe it doesn't work when the keychain isn't completley downloaded?
Ah, no it doesn't.  FYI during that period, if you submit any RPC requests to bitcoin directly via the command line it will respond with an error message saying the blockchain is currently downloading.

when i connected directly to bitcoin while the keychain was downloaded it gave me that message, while connecting to it through pushpoold gave me an error.
well, just to know...
Keninishna
Hero Member
*****
Offline Offline

Activity: 551



View Profile WWW
September 07, 2011, 10:18:06 AM
 #477

any fix to pushpoold not responding after a day or so?
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
September 07, 2011, 01:19:56 PM
 #478

any fix to pushpoold not responding after a day or so?

Have you made any changes to the stock code?

What do you see as the output of "netstat -anp"?  If you're hitting your ulimit with too many TIME_WAIT's that can cause it.
vernik
Jr. Member
*
Offline Offline

Activity: 39



View Profile WWW
September 08, 2011, 05:51:55 PM
 #479

hi, after command  "netstat -anp" i had to much "CLOSE_WAIT", not "TIME_WAIT".
How to close this connections? i think this is why pushpoold does not work after some time.

DavinciJ15
Hero Member
*****
Offline Offline

Activity: 750


Bitcoin - helping to end bankster enslavement.


View Profile WWW
September 17, 2011, 09:03:53 PM
 #480

Does anyone know what these parts of the pushpool server.json file are for...

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

and

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

Do the miner clients need to connect to those ports?
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!