regards, redshark1802
Topic: Pushpool - Tech Support - page 21. (Read 135173 times)
try apt-get install memcached
regards, redshark1802
regards, redshark1802
yep, sudo apt-get
ok, i installed it, but checking for memcached... no
configure: error: "could not find memcached binary"
pool@pool-virtual-machine:~/libmemcached-0.50$ make
make: *** No targets specified and no makefile found. Stop.
and just to confirm it's installed:
pool@pool-virtual-machine:~/libmemcached-0.50$ sudo apt-get install libmemcached-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libmemcached-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
yep, sudo apt-get
A few requirements were missing from the original post try this:
sudo aptitude install libmemcached-dev
then try ./configure
again
aptitude?sudo aptitude install libmemcached-dev
then try ./configure
again
apt-get right?
A few requirements were missing from the original post try this:
sudo aptitude install libmemcached-dev
then try ./configure
again
sudo aptitude install libmemcached-dev
then try ./configure
again
linux noob here.
installed a fresh copy of ubuntu desktop on VMware. Jansson was installed successfully, but i can't get libmemcached to install.
i got an error when using ./configure, and make does not work.
installed a fresh copy of ubuntu desktop on VMware. Jansson was installed successfully, but i can't get libmemcached to install.
i got an error when using ./configure, and make does not work.
Code:
configure: error: "could not find memcached binary"
pool@pool-virtual-machine:~/libmemcached-0.50$ make
make: *** No targets specified and no makefile found. Stop.
pool@pool-virtual-machine:~/libmemcached-0.50$ make
make: *** No targets specified and no makefile found. Stop.
here is my server.json, I removed password data etc. I closed 8332 and 8333 as you suggested
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" : "myexternalstaticip" },
# 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" : "mysql",
"host" : "localhost",
"port" : 3306,
#database name
"name" : "xxxxx",
#database username
"username" : "xxxx",
#database password
"password" : "xxxxxxxx",
#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:8332/",
#Username & password to connect to bitcoind
"rpc.user": "xxxxxx",
"rpc.pass" : "xxxxxxxr",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}
# 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" : "myexternalstaticip" },
# 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" : "mysql",
"host" : "localhost",
"port" : 3306,
#database name
"name" : "xxxxx",
#database username
"username" : "xxxx",
#database password
"password" : "xxxxxxxx",
#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:8332/",
#Username & password to connect to bitcoind
"rpc.user": "xxxxxx",
"rpc.pass" : "xxxxxxxr",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}
everything looks good, are you sure pushpoold is still running?
ps aux | grep pushpoold
regards, redshark1802
here is my server.json, I removed password data etc. I closed 8332 and 8333 as you suggested
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" : "myexternalstaticip" },
# 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" : "mysql",
"host" : "localhost",
"port" : 3306,
#database name
"name" : "xxxxx",
#database username
"username" : "xxxx",
#database password
"password" : "xxxxxxxx",
#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:8332/",
#Username & password to connect to bitcoind
"rpc.user": "xxxxxx",
"rpc.pass" : "xxxxxxxr",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}
# 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" : "myexternalstaticip" },
# 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" : "mysql",
"host" : "localhost",
"port" : 3306,
#database name
"name" : "xxxxx",
#database username
"username" : "xxxx",
#database password
"password" : "xxxxxxxx",
#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:8332/",
#Username & password to connect to bitcoind
"rpc.user": "xxxxxx",
"rpc.pass" : "xxxxxxxr",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}
It seems pushpool is not listening on any ports for me.
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
You should only connect to *:8347 with your miner.
Did you nmap on the localhost or the remote and what parameters did you use?
Try "nmap -sS -p 1-6000 -v
I nmaped from the remote. I now get 8332 and 8333 as open ports, but none of the pushpool ports (if using -p 1-9000).
Please post your server.json config, preferable on pastebin.com and I recommend closing 8332 and 8333 via iptables.
For an standard iptables installation type:
iptables -A INPUT -p tcp --dport 8332 -j DROP
iptables -A INPUT -p tcp --dport 8333 -j DROP
regards, redshark1802
It seems pushpool is not listening on any ports for me.
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
You should only connect to *:8347 with your miner.
Did you nmap on the localhost or the remote and what parameters did you use?
Try "nmap -sS -p 1-6000 -v
I nmaped from the remote. I now get 8332 and 8333 as open ports, but none of the pushpool ports (if using -p 1-9000).
It seems pushpool is not listening on any ports for me.
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
You should only connect to *:8347 with your miner.
Did you nmap on the localhost or the remote and what parameters did you use?
Try "nmap -sS -p 1-6000 -v
It seems pushpool is not listening on any ports for me.
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
I get this:
"[1308747727.006541] Listening on host :: port 8347
[1308747727.006620] Listening on host :: port 8344
[1308747727.007214] Listening on host 127.0.0.1 port 8338
"
Where it says "host ;;" I had actually entered an ip adress in the config file.
According to nmap none of those ports is actually open and beeing listened on.
What am I doing wrong?
Thanks i already had that version, the problem was that the pid was not removed properly.
Do you have a valid for an actual block?
regards, redshark1802
Do you have a valid for an actual block?
regards, redshark1802
Hello,
could someone please give me the share(solution) hash for an actual block that was found.
And one other question: why is pushpoold quiting/not starting without any errors?
I have the latest pushpool version.
regards, redshark1802
the newest pushpool has a bug where output dosen't display. There's a fix for it on the previous page and an easy delete greather than sign then replace it with a less then sign or somthing like that. could someone please give me the share(solution) hash for an actual block that was found.
And one other question: why is pushpoold quiting/not starting without any errors?
I have the latest pushpool version.
regards, redshark1802
Hello,
could someone please give me the share(solution) hash for an actual block that was found.
And one other question: why is pushpoold quiting/not starting without any errors?
I have the latest pushpool version.
regards, redshark1802
could someone please give me the share(solution) hash for an actual block that was found.
And one other question: why is pushpoold quiting/not starting without any errors?
I have the latest pushpool version.
regards, redshark1802
All my BTC are at mtgox right now :-(
Thanks Xenland! I found the problem. When I entered my ip-adress I accidentally deleted the closing ". Its working now :-)
Yep yep, Do you have any spare change for my programming addiction... I have to pay electricity costs too ya know 
!@! lol
Thanks Xenland! I found the problem. When I entered my ip-adress I accidentally deleted the closing ". Its working now :-)
This is because when starting pushpool you need to specify the path to the config.
Quote
pushpoold --config=/mypath/to/config/somefile.json
oh...I thought it was something simple as that. thanks ;-)
Finally I had time to try it. Still not working...but it seems it can at least find the file...because if I enter a WRONG path I get "config file: no such file or directory" instead of "JSON parse failed".
I copy and pasted the code for server.json thats posted at the start of this thread. Then I added my data. Where can I download a working server.json?
This is because when starting pushpool you need to specify the path to the config.
Quote
pushpoold --config=/mypath/to/config/somefile.json
oh...I thought it was something simple as that. thanks ;-)
Finally I had time to try it. Still not working...but it seems it can at least find the file...because if I enter a WRONG path I get "config file: no such file or directory" instead of "JSON parse failed".
I copy and pasted the code for server.json thats posted at the start of this thread. Then I added my data. Where can I download a working server.json?
Jump to: