Bitcoin Forum
September 11, 2024, 11:50:24 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: PushpoolD  (Read 625 times)
Daelus (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
April 15, 2013, 12:21:21 AM
Last edit: April 15, 2013, 02:19:49 AM by Daelus
 #1

PushpoolD seems to be running fine and i'm getting the initialized, miners from GUIminer can connect and they start to mine however shortly after a loop of errors start which look like this.

Code:
[2013-04-15 02:05:11.543893] Debug output enabled
[2013-04-15 02:05:11.544628] Forcing local hostname to localhost.localdomain
[2013-04-15 02:05:11.642582] Listening on host :: port 8342
[2013-04-15 02:05:11.642707] Listening on host :: port 8341
[2013-04-15 02:05:11.642794] Listening on host :: port 8332
[2013-04-15 02:05:11.642842] Listening on host 127.0.0.1 port 8338
[2013-04-15 02:05:11.676607] 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 'Daelus'
> POST / HTTP/1.1
Authorization: Basic RGFlbHVzOjU3NzQ=
Host: 127.0.0.1:8335
Accept: */*
Accept-Encoding: deflate, gzip
Content-type: application/json
Content-Length: 45

* additional stuff not fine transfer.c:1037: 0 0
* additional stuff not fine transfer.c:1037: 0 0
* HTTP 1.1 or later with persistent connection, pipelining supported
< HTTP/1.1 200 OK
< Date: Mon, 15 Apr 2013 02:05:22 +0000
< Connection: keep-alive
< Content-Length: 592
< Content-Type: application/json
< Server: bitcoin-json-rpc/v0.8.1-beta
<
* Connection #0 to host 127.0.0.1 left intact
JSON protocol response:
{
   "error": null,
   "result": {
      "target": "0000000000000000000000000000000000000000000000be2f02000000000000",
      "midstate": "b6dc6b123ab080dc451e5fb9b1597cc7b44ae3d58be58818de00d99996d93cf3",
      "hash1": "00000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000010000",
      "data": "0000000238268a767cdcd48c910b0a233ec0fb1a6cbd9727a55f01bb0000020900000000d7832a1659ce8964e1e01b261ccf4a57286dcbc8bf447857732fe0b89b1744d2516b60611a022fbe00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000"
   },
   "id": 1
}

Also, here is my Server.Json file
Code:
{
# network ports
"listen" : [
# binary protocol (default), port 8336
{ "port" : 8342 },

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

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

# 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" : "127.0.0.1",

# 'port' uses proper default port for the DB engine,
# if not specified
"port" : 3306,

"name" : "miningfarm",
"username" : "root",
"password" : "5774",

"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:8335/",
"rpc.user" : "Daelus",
"rpc.pass" : "5774",

# rewrite returned 'target' to given number of zero bits, 32 equals difficulty-1
"rpc.target.bits" : 32,

# how long before work expires?
"work.expire" : 120,

# allow clients to update the ntime field of their work
"roll.ntime.disable" : false
}
Daelus (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
April 15, 2013, 04:37:22 PM
 #2

The error continuously loops with only the ID going up each time. The error logs stay the same.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!