Flowz
Member
Offline
Activity: 114
Merit: 10
Bitcoin = Money for the people, by the people.
|
|
August 06, 2011, 10:57:37 AM |
|
Thanks Furyan and Flowz !!! Furyan your explanation helped me thousand times ! thanks . Even though the command didn't help, but i think it ruined the file , or i dunno . I did this , made a text file in directadmin file manager and named it server.json and moved it to the pool directory, and it reads it ! Wow . Nice .
I am only afraid of that the file permissions are for admin as seen in the directadmin file manager and not for root ...
Edit : I get this error in my directadmin
Error connecting to MySQL: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
I think my Mysql server is down , once i started pushpoold this what happened . And now it can't connect to the SQL server. strange ... what should i do ? I try to stop mysqld but it fails ...
Glad to help... So, it's probably a bad idea to run pushpool as root. Run pushpool as the same user as the owner of the server.json file. I'm not sure about that mysql error. It's supposed to run as the system account so I don't think it's a permissions problem. It's probably dead but the PID file is still around. What happens if you do wait about 30 seconds Do NOT use "service mysqld restart". Seems to be an odd problem with removal of the locking file. I've had the same happen on my own server, restart doesn't work, you have to use stop and then start (even though restart does exactly the same thing, it's the timing of how close together the calls are). Look what it gives :S root@server:/tmp# service mysqld stop Stopping mysqld: [ FAILED ] root@server:/tmp# service mysqld start Starting mysqld: [ OK ] root@server:/tmp# ps xa | grep mysqld 23794 ? S 0:00 sh -c /etc/init.d/mysqld rest art >>/dev/null 2>>/dev/null
23795 ? S 0:00 /bin/sh /etc/init.d/mysqld re start 23865 ttyp0 S+ 0:00 grep mysqld root@server:/tmp# cd /var/run/mysql/ -bash: cd: [b]/var/run/mysql/: No such file or directory[/b]
I think something deleted this whole directory ? or is it located somewhere else ? And when i start mysqld using directadmin it automatically shuts down :S I will google this to ease the pain hh I don't know what happend but if those directories don't exist then you will probably want to reinstall MySQL.. Give us the output of that file and I'll take a look into it! Btw we need the mysql-dev or mysql-devel install so it should be in there..
|
|
|
|
sareea
Member
Offline
Activity: 78
Merit: 10
|
|
August 06, 2011, 03:12:51 PM Last edit: August 06, 2011, 03:50:37 PM by sareea |
|
I reinstalled my OS , so now it is fresh ubuntu 11 without directadmin ( i figured out that i had debian 6 ) and now i could reach this root@server:/home/pool# ./pushpoold -E -F [2011-08-06 15:06:54.903903] Listening on host :: port 8 342 [2011-08-06 15:06:54.904103] Listening on host :: port 8 341 [2011-08-06 15:06:54.904196] Listening on host :: port 8 344 [2011-08-06 15:06:54.904268] Listening on host 127.0.0.1 port 8338 [2011-08-06 15:06:54.907270] initialized
and only this , but i can't get out to the shell command line , is this ok ? and how can i test my pool ? i think i have a worker test@test Edit: I figured that i must connect using port 8344 , but i these errors HTTP request failed: couldn't conncet to host. And i get from the miner upstream RPC error. The port i specified at the bitcoib.conf is 8332 . Is this the problem ? Edit2 : i rebooted my server. ran bitcoind and now i get initialized , but after some time i get HTTP request failed: Empty reply from server. and the miner cann't connect ,i changed nothing but rebooted :S What is this ? i will try to play a little Thanks Thanks !
|
|
|
|
Furyan
|
|
August 06, 2011, 08:56:23 PM |
|
I reinstalled my OS , so now it is fresh ubuntu 11 without directadmin ( i figured out that i had debian 6 ) and now i could reach this root@server:/home/pool# ./pushpoold -E -F [2011-08-06 15:06:54.903903] Listening on host :: port 8 342 [2011-08-06 15:06:54.904103] Listening on host :: port 8 341 [2011-08-06 15:06:54.904196] Listening on host :: port 8 344 [2011-08-06 15:06:54.904268] Listening on host 127.0.0.1 port 8338 [2011-08-06 15:06:54.907270] initialized
and only this , but i can't get out to the shell command line , is this ok ? and how can i test my pool ? i think i have a worker test@test It's ok for testing but you're not going to want to do that for production. For instance I've just finished installing bitcoind and pushpoold as services, and setting up Monit to monitor and restart memcached, bitcoind and pushpoold should they go down. They'll also start when the machine reboots. Set and forget. Nice thing about Monit is it has a web interface you can use for monitoring and service control. Very slick. Edit: I figured that i must connect using port 8344 , but i these errors HTTP request failed: couldn't conncet to host. And i get from the miner upstream RPC error. The port i specified at the bitcoib.conf is 8332 . Is this the problem ?
Edit2 : i rebooted my server. ran bitcoind and now i get initialized , but after some time i get HTTP request failed: Empty reply from server. and the miner cann't connect ,i changed nothing but rebooted :S What is this ? i will try to play a little Thanks Thanks !
These indicate there's a port mismatch between pushpoold and bitcoind. Make sure that the RPCport in bitcoind, is the one that pushpoold is connecting to. This took a bit of figuring out for me when I first set these up, the variable names in the config files are not especially enlightening. I actually have bitcoind open a different port that pushpoold connects to. Then I have pushpoold expose 8332 to the web for miners. No particular reason to do so except to maintain the convention of using 8332 for mining.
|
|
|
|
sareea
Member
Offline
Activity: 78
Merit: 10
|
|
August 07, 2011, 04:09:30 PM |
|
I reinstalled my OS , so now it is fresh ubuntu 11 without directadmin ( i figured out that i had debian 6 ) and now i could reach this root@server:/home/pool# ./pushpoold -E -F [2011-08-06 15:06:54.903903] Listening on host :: port 8 342 [2011-08-06 15:06:54.904103] Listening on host :: port 8 341 [2011-08-06 15:06:54.904196] Listening on host :: port 8 344 [2011-08-06 15:06:54.904268] Listening on host 127.0.0.1 port 8338 [2011-08-06 15:06:54.907270] initialized
and only this , but i can't get out to the shell command line , is this ok ? and how can i test my pool ? i think i have a worker test@test It's ok for testing but you're not going to want to do that for production. For instance I've just finished installing bitcoind and pushpoold as services, and setting up Monit to monitor and restart memcached, bitcoind and pushpoold should they go down. They'll also start when the machine reboots. Set and forget. Nice thing about Monit is it has a web interface you can use for monitoring and service control. Very slick. Edit: I figured that i must connect using port 8344 , but i these errors HTTP request failed: couldn't conncet to host. And i get from the miner upstream RPC error. The port i specified at the bitcoib.conf is 8332 . Is this the problem ?
Edit2 : i rebooted my server. ran bitcoind and now i get initialized , but after some time i get HTTP request failed: Empty reply from server. and the miner cann't connect ,i changed nothing but rebooted :S What is this ? i will try to play a little Thanks Thanks !
These indicate there's a port mismatch between pushpoold and bitcoind. Make sure that the RPCport in bitcoind, is the one that pushpoold is connecting to. This took a bit of figuring out for me when I first set these up, the variable names in the config files are not especially enlightening. I actually have bitcoind open a different port that pushpoold connects to. Then I have pushpoold expose 8332 to the web for miners. No particular reason to do so except to maintain the convention of using 8332 for mining. Thanks ! I fixed the problem , by making the same rpc port for the 3 files . ( the rpc url , the port in the bitcoin.conf and in blkmond.conf ) I did rpcallowip=*.*.*.* Can i remove this without any problem letting anyone connecting to the pool ? Thanks !
|
|
|
|
Furyan
|
|
August 08, 2011, 02:13:38 AM |
|
I reinstalled my OS , so now it is fresh ubuntu 11 without directadmin ( i figured out that i had debian 6 ) and now i could reach this root@server:/home/pool# ./pushpoold -E -F [2011-08-06 15:06:54.903903] Listening on host :: port 8 342 [2011-08-06 15:06:54.904103] Listening on host :: port 8 341 [2011-08-06 15:06:54.904196] Listening on host :: port 8 344 [2011-08-06 15:06:54.904268] Listening on host 127.0.0.1 port 8338 [2011-08-06 15:06:54.907270] initialized
and only this , but i can't get out to the shell command line , is this ok ? and how can i test my pool ? i think i have a worker test@test It's ok for testing but you're not going to want to do that for production. For instance I've just finished installing bitcoind and pushpoold as services, and setting up Monit to monitor and restart memcached, bitcoind and pushpoold should they go down. They'll also start when the machine reboots. Set and forget. Nice thing about Monit is it has a web interface you can use for monitoring and service control. Very slick. Edit: I figured that i must connect using port 8344 , but i these errors HTTP request failed: couldn't conncet to host. And i get from the miner upstream RPC error. The port i specified at the bitcoib.conf is 8332 . Is this the problem ?
Edit2 : i rebooted my server. ran bitcoind and now i get initialized , but after some time i get HTTP request failed: Empty reply from server. and the miner cann't connect ,i changed nothing but rebooted :S What is this ? i will try to play a little Thanks Thanks !
These indicate there's a port mismatch between pushpoold and bitcoind. Make sure that the RPCport in bitcoind, is the one that pushpoold is connecting to. This took a bit of figuring out for me when I first set these up, the variable names in the config files are not especially enlightening. I actually have bitcoind open a different port that pushpoold connects to. Then I have pushpoold expose 8332 to the web for miners. No particular reason to do so except to maintain the convention of using 8332 for mining. Thanks ! I fixed the problem , by making the same rpc port for the 3 files . ( the rpc url , the port in the bitcoin.conf and in blkmond.conf ) I did rpcallowip=*.*.*.* Can i remove this without any problem letting anyone connecting to the pool ? Thanks ! It's advisable to have rpcallowip only be the machines you actually want to allow to connect to bitcoind itself. Thus, you can actually just comment out the whole line. Bitcoin will always allow connections from the localhost, which is usually where pushpool is running. If you have pushpool running on a different server, you should include that server's IP in rpcallowip. You can add as many of those lines as you want, by the way.
|
|
|
|
sareea
Member
Offline
Activity: 78
Merit: 10
|
|
August 10, 2011, 10:00:20 AM Last edit: August 10, 2011, 11:43:56 AM by sareea |
|
Hello, Thanks a lot guys ! How can i see using pushpoold how many workers are connected and the total m/hashes ?
I have another problem with mining farm , i have a connected worker of 300 M/hashes and the front end doesn't recognize it , what should i do? Is it possible that pushpoold is not reporting about it ?
And i am thinking moving to simple coin, as i feel the mining farm has a problem in cronjobs what do you think ?
Can someone help please ? Thanks !
|
|
|
|
Furyan
|
|
August 10, 2011, 11:38:02 AM |
|
Hello, Thanks a lot guys ! How can i see using pushpoold how many workers are connected and the total m/hashes ?
How many workers are connected = up to you to define - the typical approach is you look at all the workers that have reported a share in a given time window, usually 10 minutes. The number of distinct workers in that list is the count of 'connected' workers. Workers don't actually "connect" - you can't think of it as a connection staying open. Data is passed back and forth between pushpool and the miners in a send/receive/end manner, so the concept of 'connected' is not really what you are measuring. You're just measuring recent active workers. I have another problem with mining farm , i have a connected worker of 300 M/hashes and the front end doesn't recognize it , what should i do? Is it possible that pushpoold is not reporting about it ?
Can someone help please ? Thanks !
It's possible pushpoold isn't reporting the shares - what is your "rpc.target.rewrite" value set to in your Pushpool json config file? Beyond that, it's a question for Xenland over at Mining Farm tech support - http://forum.bitcoin.org/index.php?topic=18886.0
|
|
|
|
sareea
Member
Offline
Activity: 78
Merit: 10
|
|
August 10, 2011, 12:21:23 PM |
|
Hello, Thanks a lot guys ! How can i see using pushpoold how many workers are connected and the total m/hashes ?
How many workers are connected = up to you to define - the typical approach is you look at all the workers that have reported a share in a given time window, usually 10 minutes. The number of distinct workers in that list is the count of 'connected' workers. Workers don't actually "connect" - you can't think of it as a connection staying open. Data is passed back and forth between pushpool and the miners in a send/receive/end manner, so the concept of 'connected' is not really what you are measuring. You're just measuring recent active workers. I have another problem with mining farm , i have a connected worker of 300 M/hashes and the front end doesn't recognize it , what should i do? Is it possible that pushpoold is not reporting about it ?
Can someone help please ? Thanks !
It's possible pushpoold isn't reporting the shares - what is your "rpc.target.rewrite" value set to in your Pushpool json config file? Beyond that, it's a question for Xenland over at Mining Farm tech support - http://forum.bitcoin.org/index.php?topic=18886.0my "rpc.target.rewrite" is set to true . I will post at that thread you gave me thanks . What do you think is better Mining farm or simplecoin ? Thanks !
|
|
|
|
Furyan
|
|
August 10, 2011, 05:41:24 PM |
|
my "rpc.target.rewrite" is set to true . I will post at that thread you gave me thanks . What do you think is better Mining farm or simplecoin ? Thanks !
Keeping in mind I don't intend to run either one, if I were to choose one I'd choose simplecoin. It's a bit more developed, cleaner. I've looked at the code for both and the sites they produce. For whatever my opinion on the subject is worth.
|
|
|
|
sareea
Member
Offline
Activity: 78
Merit: 10
|
|
August 10, 2011, 07:24:07 PM |
|
my "rpc.target.rewrite" is set to true . I will post at that thread you gave me thanks . What do you think is better Mining farm or simplecoin ? Thanks !
Keeping in mind I don't intend to run either one, if I were to choose one I'd choose simplecoin. It's a bit more developed, cleaner. I've looked at the code for both and the sites they produce. For whatever my opinion on the subject is worth. Thanks a lot dude !!!!!
|
|
|
|
eyeoh
Newbie
Offline
Activity: 31
Merit: 0
|
|
August 13, 2011, 01:02:49 AM |
|
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?
|
|
|
|
wezzy
Member
Offline
Activity: 67
Merit: 10
|
|
August 13, 2011, 05:46:58 AM |
|
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.
|
|
|
|
Furyan
|
|
August 13, 2011, 03:38:34 PM |
|
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.
|
|
|
|
Furyan
|
|
August 13, 2011, 03:43:08 PM |
|
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
Member
Offline
Activity: 67
Merit: 10
|
|
August 15, 2011, 01:25:13 AM |
|
Thanks mate! I will give it a try and let you know. Cheers for the info.
Wes.
|
|
|
|
Keninishna
|
|
August 26, 2011, 05:52:41 AM |
|
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
|
|
|
|
simplecoin
|
|
August 26, 2011, 07:03:33 AM |
|
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 just run: sudo apt-get install libevent-dev
|
Donations: 1VjGJHPtLodwCFBDWsHJMdEhqRcRKdBQk
|
|
|
Keninishna
|
|
August 26, 2011, 07:17:09 AM |
|
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
Activity: 15
Merit: 0
|
|
August 31, 2011, 02:20:16 AM |
|
Sorry, missed this one. We're multi-threading a single thread. Hah! 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 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.
|
|
|
|
bully
Newbie
Offline
Activity: 14
Merit: 0
|
|
August 31, 2011, 01:24:02 PM |
|
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. 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": * 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.confserver=1 rpcuser=hidden rpcpassword=morehidden rpcallowip=127.0.0.1 rpcport=8332 gen=0 server.json{ # 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: 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) 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 :-/
|
|
|
|
|