Pages:
Author

Topic: Pushpool - Tech Support - page 26. (Read 135213 times)

newbie
Activity: 18
Merit: 0
June 06, 2011, 11:28:59 PM
#85
Made sure and it def. does... I am signed in as root so its not a permission issue... After installing a few extra packages like build-essentials I now get this.


Code:
bash: ./configure: No such file or directory
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 06, 2011, 11:15:14 PM
#84
I am having an issue with Installation... I am running Ubuntu 11.04 Server and when I get to the point to configure the files for install I get:
 I Enter this:
Code:
 ./configure --prefix=/home/[b]my_user_name[/b]/pushpool/


I Get This:
Quote
configure: command not found


Am I missing something that needs to be installed in Ubuntu?

Sorry I am kind of a Linux Newb.

./configure --prefix=folder you want to install

make sure that you acknowledge that this is working directory after the "--prefix=" usually your home folder other then that why it doesn't recognise "./configure" command(notice the ./) type it in exactly as I have except for the prefix part.
newbie
Activity: 18
Merit: 0
June 06, 2011, 10:26:32 PM
#83
I am having an issue with Installation... I am running Ubuntu 11.04 Server and when I get to the point to configure the files for install I get:
 I Enter this:
Code:
 ./configure --prefix=/home/[b]my_user_name[/b]/pushpool/


I Get This:
Quote
configure: command not found


Am I missing something that needs to be installed in Ubuntu?

Sorry I am kind of a Linux Newb.
newbie
Activity: 22
Merit: 0
June 06, 2011, 02:06:49 PM
#82
Hi. Me and my friend turlando are triyng to set up pushpool.
On an old server all went fine, but on a new server, with the same config (except for some passwords), we get this error:
[1307382484.476195] tcp socket: Address family not supported by protocol
This is the config:
Code:

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

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

      # HTTP JSON-RPC protocol, port 8344,
      #proxy is most likely your external ip address if your running a public pool | Public pools WON'T have the following ip addresses: (10.0.0.1, 127.0.0.1, 192.168.1.100, or 192.168.254.254,etc,etc)
      # requests to us | "proxy" should be set to your ip address that people will connect through
      { "port" : 8344, "protocol" : "http-json",
        "proxy" : "127.0.0.1" },

      # binary protocol, localhost-only port 8338
      # host is most likely your localhost address
      { "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
   ],


# database settings
"database" : {

"engine" : "postgresql",

"host" : "127.0.0.1",

"port" : 5432,

"name" : "pushpool",
"username" : "bitcoin",
"password" : "hidden",

# set to true to enable logging of shares to db
"sharelog" : true,

# edit queries to match your database structure if necessary
"stmt.pwdb" :
  "SELECT password FROM pool_worker WHERE username = $1",

                "stmt.sharelog" :
                  "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES ($1, $2, $3, $4, $5, decode($6, 'hex'))"

},

# cache settings
# comment out to disable memcache - NOT RECOMMENDED
"memcached" : {
"servers" : [
{ "host" : "127.0.0.1", "port" : 11211 }
]
},

"pid" : "/tmp/pushpoold.pid",

# overrides local hostname detection
#"forcehost" : "localhost.localdomain",

# logfiles for requests and shares
"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 to bitcoind upstream server (same as bitcoin.conf if using original client)
"rpc.url" : "http://127.0.0.1:8332/",
"rpc.user" : "bitcoin",
"rpc.pass" : "hidden",

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

We did some search but we didn't found anything. Someone can help us?
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 05, 2011, 06:51:33 AM
#81
Do you have mysql or any other database engine running? It's mandatory, also, bitcoinD should be running prior to launching pushpool

Yeah, mysqld running and bitcoind running as well. How strange, it just exits right after launching pretty much ... I've recompiled it, restarted processes - nothing. What am I missing here?

EDIT: Fixed it. Looks like I had the some issue someone else had, permissions problem. I changed all references of '/tmp' to /home/user1'

Woohoo! That consumed way too much time ... I wish pushpoold had kicked out an error or something about it.

Yeah you are find out all my frustration I incurred in the IRC chat, You really do just have to "play with it", server.json.
One thing is to make sure that you set your bitcoind RPC details correctly at the end of the server.json file.
The next thing to do is to change all the ports to something different, one-by-one. As I released the server.json file with the original but better commenting, which means its the original that your seeing. On my personal VPS I had to change one of the RPC ports for it to initialise for some reason port 8333 was open and unknown in the ping scan but when I changed it to something like 8338. It finally initialised, after that I started getting connected clients from my miner but pwdb query errors then i knew right away it was MySql database problem so I fiddled around a tid-bit and realised i was connected to my local database on my computer and not the local database on my VPS server. So i fixed those details and then all of a sudden I started getting "RPC not responding from my server" the second I uploaded the correct database details. Well after much frustration I realised that push pool dosen't properly alert the user that it was a bad user name and password and/or port number. So I typed in the right port number with the right database details and vola... after 18hours I got my pushpoold server to work..

This was my whole experience on pushpool, and what problems was caused by it..... Its the only I go off of because pushpool fails to give out logging messages
full member
Activity: 126
Merit: 100
June 05, 2011, 06:11:13 AM
#80
I don't know, i never had any problems regarding permissions. Even the first ever time i ran pushpool. Some people said it's not safe for pushpool to use the /tmp folder, but why?
newbie
Activity: 17
Merit: 0
June 04, 2011, 09:46:21 PM
#79
Do you have mysql or any other database engine running? It's mandatory, also, bitcoinD should be running prior to launching pushpool

Yeah, mysqld running and bitcoind running as well. How strange, it just exits right after launching pretty much ... I've recompiled it, restarted processes - nothing. What am I missing here?

EDIT: Fixed it. Looks like I had the some issue someone else had, permissions problem. I changed all references of '/tmp' to /home/user1'

Woohoo! That consumed way too much time ... I wish pushpoold had kicked out an error or something about it.
full member
Activity: 126
Merit: 100
June 04, 2011, 09:27:16 PM
#78
Do you have mysql or any other database engine running? It's mandatory, also, bitcoinD should be running prior to launching pushpool
newbie
Activity: 17
Merit: 0
June 04, 2011, 09:22:18 PM
#77
Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:
user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1#

are you sure its quitting and not just running in the background?

No PID, no output to any logs, nothing. I tried using the cfg file example Xenland had posted, along with my own variant, no dice either time. Any ideas?
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 04, 2011, 08:36:41 PM
#76
Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:
user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1#

are you sure its quitting and not just running in the background?

With the -F flag it should never display the last line user1@226776:. Which means it silenctly shutting down but yet again pushpool never tells us why the things it does.... Sad
member
Activity: 61
Merit: 10
June 04, 2011, 07:01:37 PM
#75
Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:
user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1#

are you sure its quitting and not just running in the background?
newbie
Activity: 17
Merit: 0
June 04, 2011, 05:39:41 PM
#74
Any idea why pushpool never reaches the "initializing" stage, but just quits? Nothing at all in the pushpool logfiles ...

Code:
user1@226776:/home/user1/pushpool-0.4.1# ./pushpoold --config=mycfg.json --debug=2 -E -F
[1307223396.497494] Debug output enabled
[1307223396.497798] Forcing local hostname to localhost.localdomain
[1307223396.501021] Listening on host :: port 8336
[1307223396.501114] Listening on host :: port 8337
[1307223396.501184] Listening on host :: port 8339
[1307223396.501242] Listening on host 184.22.250.98 port 8338
user1@226776:/home/user1/pushpool-0.4.1#
legendary
Activity: 1372
Merit: 1007
1davout
June 03, 2011, 10:08:06 PM
#73
Hm, I have the user in the database. Although the query logs are blank, nothing in them.

I can connect to the server's bitcoind directly.. And to the PushPoold. Its like pushpoold wont see bitcoind.
i don't see how you could connect to pushpool with blank query logs
newbie
Activity: 40
Merit: 0
June 03, 2011, 09:43:32 PM
#72
Hm, I have the user in the database. Although the query logs are blank, nothing in them.

I can connect to the server's bitcoind directly.. And to the PushPoold. Its like pushpoold wont see bitcoind.
legendary
Activity: 980
Merit: 1003
I'm not just any shaman, I'm a Sha256man
June 03, 2011, 08:19:31 PM
#71
The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though Tongue).

Am quite lost now..

Your miner has problems connecting to pushpool, check worker credentials when launching, and in DB, check worker query.
Check query logs.

Yeah what he said, make sure you insert a worker to your database, and make sure they match exactly when typing it into your miner
legendary
Activity: 1372
Merit: 1007
1davout
June 03, 2011, 06:03:31 PM
#70
The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though Tongue).

Am quite lost now..

Your miner has problems connecting to pushpool, check worker credentials when launching, and in DB, check worker query.
Check query logs.
newbie
Activity: 40
Merit: 0
June 03, 2011, 05:56:31 PM
#69
So, still havent figured it out... I think that the connection between pushpoold and bitcoind is null.

When I launch pushpoold:
Code:
root@testserver:/home/root/pushpool/sbin# ./pushpoold --debug=2 --stderr --foreground
[1307137799.257380] Debug output enabled
[1307137799.258044] Forcing local hostname to localhost.localdomain
[1307137799.261883] Listening on host :: port 8342
[1307137799.262155] Listening on host :: port 8341
[1307137799.262364] Listening on host :: port 8344
[1307137799.262578] Listening on host xx.xxx.xx.xx port 8338
[1307137799.266777] initialized
[1307137804.486011] client host xxx.xxx.xx.xxx port 58435 connected
[1307137804.493953] client xxx.xxx.xx.xxx ended
[1307137805.852921] client host xxx.xxx.xx.xxx port 58436 connected
[1307137805.858515] client xxx.xxx.xx.xxx ended
[1307137807.207877] client host xxx.xxx.xx.xxx port 58437 connected
[1307137807.212642] client xxx.xxx.xx.xxx ended
[1307137808.567177] client host xxx.xxx.xx.xxx port 58438 connected
[1307137808.572342] client xxx.xxx.xx.xxx ended

The mining client just get's "Problems connecting to bitcoin rpc"

I have run the bitcoin daemon with "./bitcoind -server" with the same config as Wayno (Fixed the incorrect password though Tongue).

Am quite lost now..
member
Activity: 61
Merit: 10
June 03, 2011, 02:53:08 PM
#68
omg thanks u 1 spelling mistake off :\

stupid me :\
legendary
Activity: 1372
Merit: 1007
1davout
June 03, 2011, 02:31:56 PM
#67
401 = wrong credentials

And because I'm nice I'll tell you the problem is in the pushpool config file Smiley
member
Activity: 61
Merit: 10
June 03, 2011, 02:00:08 PM
#66
Code:
JSON protocol request:
{"method": "getwork", "params": [], "id":3}

* 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 'coinz'
> POST / HTTP/1.1
Authorization: Basic Y29pbno6Y2lvbnoxMQ==
Host: 127.0.0.1:8335
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: Fri, 03 Jun 2011 17:58:10 +0000
< Server: bitcoin-json-rpc/0.3.21-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
[1307123890.859317] HTTP request failed: The requested URL returned error: 401

Code:
{
   # 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,
      #proxy is most likely your external ip address if your running a public pool | Public pools WON'T have the following ip addresses: (10.0.0.1, 127.0.0.1, 192.168.1.100, or 192.168.254.254,etc,etc)
      # requests to us | "proxy" should be set to your ip address that people will connect through
      { "port" : 8344, "protocol" : "http-json",
        "proxy" : "110.173.226.1" },

      # binary protocol, localhost-only port 8338
      # host is most likely your localhost address
      { "host" : "110.173.226.1", "port" : 8338, "protocol" : "binary" }
   ],

   # database settings
   "database" : {
      "engine" : "mysql",

      "host" : "localhost",

      "port" : 3306,

      #database name
      "name" : "pushpool",
      #database username
      "username" : "bitcoin",
      #database password
      "password" : "bitcoin11",
      #enable sharelog | to insert share data or sometimes known as "work"
      "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 (?, ?, ?, ?, ?, ?)"

   },

   #uncoment this when you want to use memcached (Recommended for servers over 1.5gb of ram)
   # 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
   #Bitcoind Protocal settings
   #Host were bitcoind can be found on the network
   "rpc.url" : "http://127.0.0.1:8335/",
   #Username & password to connect to bitcoind
   "rpc.user" : "coinz",
   "rpc.pass" : "cionz11",

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

Code:
rpcuser=coinz
rpcpassword=coinz11
rpcport=8335
server=1
gen=0
rpcallowip=*

Code:
./bitcoind -server -deamon
./pushpoold -E -F
Pages:
Jump to: