zakoliverz
|
|
April 17, 2013, 03:24:53 PM |
|
My installation work great!
|
|
|
|
raubaut
Newbie
Offline
Activity: 20
Merit: 0
|
|
April 18, 2013, 11:51:10 PM |
|
After everything, I get to the last steps and: ./configure: line 5901: syntax error near unexpected token `,' ./configure: line 5901: `LIBCURL_CHECK_CONFIG(, 7.10.1, ,' you need libcurl.m4 placed in a pkg-config folder somewhere. Thank you for setting me on the right path. In case anyone else is having this problem, this is how I solved it: I found hangover's helpful post which mentioned the following steps: cp /usr/local/share/doc/curl/libcurl/libcurl.m4 m4
Then add string "ACLOCAL_AMFLAGS = -I m4" to file Makefile.am and edit file autogen.sh - replace string "aclocal" with "aclocal -I m4". Before I could do this, I had to do the following: apt-get install libcurl3-dev curl-dev apt-get install locate updatedb locate libcurl.m4 This showed me where libcurl.m4 was. Then I could copy it to the m4 directory, and the rest is history.
|
|
|
|
calonew
|
|
April 19, 2013, 07:32:40 AM |
|
After 4 hours of running pushpool server, the server freezes and reports a lot of: ... [warn] accept_socket: bad accept: Too many open files [warn] accept_socket: bad accept: Too many open files [warn] accept_socket: bad accept: Too many open files [warn] accept_socket: bad accept: Too many open files [warn] accept_socket: bad accept: Too many open files
Any idea of what is causing this? And how can I prevent it?
|
|
|
|
jgarzik
Legendary
Offline
Activity: 1596
Merit: 1100
|
|
April 19, 2013, 07:39:17 AM |
|
Increase the open file limit for the process, and/or don't have so many connections.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
montdidier
Newbie
Offline
Activity: 19
Merit: 0
|
|
April 19, 2013, 08:22:09 AM |
|
Is there any documentation stating the meaning of the command line arguments flags for pushpool?
|
|
|
|
thisway
Newbie
Offline
Activity: 46
Merit: 0
|
|
April 19, 2013, 11:08:09 AM |
|
You could try sbin/pushpoold --help
|
|
|
|
Minertor
Newbie
Offline
Activity: 8
Merit: 0
|
|
April 20, 2013, 07:24:19 PM Last edit: April 20, 2013, 08:03:00 PM by Minertor |
|
now 30000 shares, still no upstream_result with "N" or "Y"
problems?
upstream_result is when the pool detects a share at or higher than the network target, ONLY THEN does it allow it to get to bitcoind. That's why, basically. I'm having same problem, I have bit difficulty set to 17 and have around 30,000 shares in database and non have been changed Y or N is this normal?
|
|
|
|
thisway
Newbie
Offline
Activity: 46
Merit: 0
|
|
April 20, 2013, 10:00:27 PM |
|
How did you change the difficulty? I'm stuck. I tried "rpc.target.bits" : 18 but without success
|
|
|
|
Minertor
Newbie
Offline
Activity: 8
Merit: 0
|
|
April 20, 2013, 11:14:23 PM |
|
How did you change the difficulty? I'm stuck. I tried "rpc.target.bits" : 18 but without success "rpc.target.bits" : 17, Is how it is set in mine. So far have mined about 35k shares and non have ever put anything into UPSTREAM JSON protocol request: {"method": "getwork", "params": [], "id":23}
* Re-using existing connection! (#0) with host 127.0.0.1 * Connected to 127.0.0.1 (127.0.0.1) port 9333 (#0) * Server auth using Basic with user 'USERNAME' > POST / HTTP/1.1 Authorization: Basic bGl0ZXVzZXJ4OnA0c3N3b3JkMTIz Host: 127.0.0.1:9333 Accept: */* Accept-Encoding: deflate, gzip Content-type: application/json Content-Length: 46
< HTTP/1.1 200 OK < Date: Sat, 20 Apr 2013 23:12:20 +0000 < Connection: keep-alive < Content-Length: 623 < Content-Type: application/json < Server: litecoin-json-rpc/v0.6.1-670-g7fd4c83-beta < * Connection #0 to host 127.0.0.1 left intact JSON protocol response: { "error": null, "result": { "target": "00000000000000000000000000000000000000000000000000ddb30000000000", "midstate": "be1e1718bf00428e1163df7f605522174c7c6dba7ae4831eaa6cc59b9b19c017", "algorithm": "scrypt:1024,1,1", "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000", "data": "00000001d30a0b25d62d45c56189381944ebc0c61c3604afbc1560810bea22463c37e49dd05d99190632119b2e918b1faf067ee5dec7fca63ea8c0282ed1d6a0e36113fa517320ea1c00b3dd00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000" }, "id": 23
This is what i'm geting when running in debug. is "error" null, normally every time or am I missing something?
|
|
|
|
calonew
|
|
April 21, 2013, 02:24:02 PM |
|
to change the pool difficulty, is enough to modify the config.json file? Is enough to add this code? "rpc.target.bits" : 17 can you post a config.json file that works for you? if you set bit difficulty to 17... what difficulty shares are served to miners by pushpool?
|
|
|
|
montdidier
Newbie
Offline
Activity: 19
Merit: 0
|
|
April 22, 2013, 01:16:47 AM |
|
You could try sbin/pushpoold --help
Ok silly me. Of course. Found them.
|
|
|
|
fcmatt
Legendary
Offline
Activity: 2072
Merit: 1001
|
|
April 26, 2013, 04:39:31 AM |
|
What pushpool release is considered the best for litecoin mining? Artforz's github version? Or should i be playing around with a diff version?
|
|
|
|
gateway
|
|
May 02, 2013, 09:08:34 PM |
|
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: > 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 { # 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 server=1 daemon=1 rpcallowip=* rpcuser=mybitcoinduser rpcpassword=mybitcoindpass any thoughts? :?
|
|
|
|
KALRONG
Newbie
Offline
Activity: 52
Merit: 0
|
|
May 02, 2013, 09:13:50 PM |
|
Can you post the whole log from pushpool? do you see the intialized message?
|
|
|
|
gateway
|
|
May 02, 2013, 10:04:49 PM |
|
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}
|
|
|
|
KALRONG
Newbie
Offline
Activity: 52
Merit: 0
|
|
May 03, 2013, 01:20:06 PM |
|
looks like your pushpool cant connect to bitcoind, are you running bitcoind (already synchronized) before pushpool?
|
|
|
|
gateway
|
|
May 03, 2013, 05:12:58 PM |
|
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.. ..
|
|
|
|
gateway
|
|
May 03, 2013, 05:13:42 PM |
|
"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.. ?
|
|
|
|
KALRONG
Newbie
Offline
Activity: 52
Merit: 0
|
|
May 03, 2013, 06:03:39 PM |
|
Same problem as with the insert in networkBlocks, add a COMMIT call to the SQL server after the insert, it should work then.
|
|
|
|
OversightNL
Newbie
Offline
Activity: 56
Merit: 0
|
|
May 05, 2013, 02:42:30 AM |
|
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 ...
|
|
|
|
|