Are you sure it is not dying right away after it comes up? I had a lot of initial issues getting pushpoold to even start up and stay started. Most of the time is was a database issue when pp tried to connect to mysql it was failing and causing pp to stop right away make sure pushpool is started and you should be able to telnet to ur port 8344
Okay I'm trying to figure out what could be stopping pushpool from running. I double checked the database name, username to database, and associated password by logging into mysql via the terminal and then doing a SELECT * FROM pool_worker to see if I could get that far. I did have one suspicion about the port that is used to connect to the database. Is that port a default port if so how could I change it in mysql if I need to? Is the method I used of finding the process ID associated with pushpoold a valid way of checking to see if pushpoold is running? thanks for your help. What version of pushpool are you trying to run? v0.5 or v0.4.1  If you are using v0.5 try v0.4.1 ... To check to see if pushpool is running, simply type ps aux | grep pushpool and you should notice at least two references to pushpool. (One for the search command you just submit, and one for the running pushpoo program). Also try running pushpool by typing ./pushpool -EI can't seem to get ./pushpool running by simply running /pushpool but if I add the -E then it seems to work great. Okay I am running v0.5. I tried running the command ps aux | grep pushpool and this was the result: bitcoinminer2@ubuntu:~$ ps aux | grep pushpoold
1000 3004 0.0 0.0 13124 1032 pts/3 S+ 15:14 0:00 grep --color=auto pushpoold
this is of course after running: bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$ ./pushpoold -E
bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$ [2011-06-26 23:15:47.680372] Listening on host :: port 8342
[2011-06-26 23:15:47.680703] Listening on host :: port 8341
[2011-06-26 23:15:47.680835] Listening on host :: port 8344
[2011-06-26 23:15:47.680934] Listening on host 127.0.0.1 port 8338
You think it could be the version? what version are you running? Have you had similar problems like this? |
|
|
|
Are you sure it is not dying right away after it comes up? I had a lot of initial issues getting pushpoold to even start up and stay started. Most of the time is was a database issue when pp tried to connect to mysql it was failing and causing pp to stop right away make sure pushpool is started and you should be able to telnet to ur port 8344
Okay I'm trying to figure out what could be stopping pushpool from running. I double checked the database name, username to database, and associated password by logging into mysql via the terminal and then doing a SELECT * FROM pool_worker to see if I could get that far. I did have one suspicion about the port that is used to connect to the database. Is that port a default port if so how could I change it in mysql if I need to? Is the method I used of finding the process ID associated with pushpoold a valid way of checking to see if pushpoold is running? thanks for your help. |
|
|
|
|
Is there any reason that when i run pushpool and I try to find the process that is created by running ps aux | grep pushpoold that it doesn't appear to recognize what I ran? When I try it on bitcoind it finds it as "./bitcoind -server -daemon".
I suspect this could possibly be why I can't find any way to connect my phoenix miner to pushpoold.
Any thoughts anyone?
|
|
|
|
Okay I'm still not able to connect with my phoenix miner using: start /DC:\Phoenix phoenix.exe -u http://NH2LwYuL585o6sgiikAG42sbmAhGwj8Vsd:pass@192.168.1.11:8344/;askrate=10 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 DEVICE=0 FASTLOOP=false I tried to open up port 8344 as follows (still can't get phoenix to connect to bitcoind). Any help? root@ubuntu:/# sudo ufw allow proto tcp from 192.168.1.12 to 192.168.1.13 port 8344
Rule added
root@ubuntu:/# sudo ufw allow proto tcp from 192.168.1.10 to 192.168.1.10 port 8344
Rule added
root@ubuntu:/# sudo ufw --dry-run allow http
*filter
:ufw-user-input - [0:0]
:ufw-user-output - [0:0]
:ufw-user-forward - [0:0]
:ufw-before-logging-input - [0:0]
:ufw-before-logging-output - [0:0]
:ufw-before-logging-forward - [0:0]
:ufw-user-logging-input - [0:0]
:ufw-user-logging-output - [0:0]
:ufw-user-logging-forward - [0:0]
:ufw-after-logging-input - [0:0]
:ufw-after-logging-output - [0:0]
:ufw-after-logging-forward - [0:0]
:ufw-logging-deny - [0:0]
:ufw-logging-allow - [0:0]
:ufw-user-limit - [0:0]
:ufw-user-limit-accept - [0:0]
### RULES ###
### tuple ### allow any 8342 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 8342 -j ACCEPT
-A ufw-user-input -p udp --dport 8342 -j ACCEPT
### tuple ### allow any 8341 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 8341 -j ACCEPT
-A ufw-user-input -p udp --dport 8341 -j ACCEPT
### tuple ### allow any 8344 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 8344 -j ACCEPT
-A ufw-user-input -p udp --dport 8344 -j ACCEPT
### tuple ### allow any 8338 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 8338 -j ACCEPT
-A ufw-user-input -p udp --dport 8338 -j ACCEPT
### tuple ### allow tcp 8344 192.168.1.13 any 192.168.1.12 in
-A ufw-user-input -p tcp -d 192.168.1.13 --dport 8344 -s 192.168.1.12 -j ACCEPT
### tuple ### allow tcp 8344 192.168.1.10 any 192.168.1.10 in
-A ufw-user-input -p tcp -d 192.168.1.10 --dport 8344 -s 192.168.1.10 -j ACCEPT
### tuple ### allow tcp 80 0.0.0.0/0 any 0.0.0.0/0 in
-A ufw-user-input -p tcp --dport 80 -j ACCEPT
### END RULES ###
### LOGGING ###
-A ufw-after-logging-input -j LOG --log-prefix "[UFW BLOCK] " -m limit --limit 3/min --limit-burst 10
-A ufw-after-logging-forward -j LOG --log-prefix "[UFW BLOCK] " -m limit --limit 3/min --limit-burst 10
-I ufw-logging-deny -m state --state INVALID -j RETURN -m limit --limit 3/min --limit-burst 10
-A ufw-logging-deny -j LOG --log-prefix "[UFW BLOCK] " -m limit --limit 3/min --limit-burst 10
-A ufw-logging-allow -j LOG --log-prefix "[UFW ALLOW] " -m limit --limit 3/min --limit-burst 10
### END LOGGING ###
### RATE LIMITING ###
-A ufw-user-limit -m limit --limit 3/minute -j LOG --log-prefix "[UFW LIMIT BLOCK] "
-A ufw-user-limit -j REJECT
-A ufw-user-limit-accept -j ACCEPT
### END RATE LIMITING ###
COMMIT
Rules updated
root@ubuntu:/#
|
|
|
|
Okay I have verified that bitcoind is running and that all blocks have been downloaded. Also I have run : ...on all of the ports at the top of server.json. When I try to test the ports with : ...I get a message saying connection failed/rejected for port <port>. I'm a bit lost at this point. Any help? Also is there any specific setup I would have to ensure with the port used in connecting to my mysql database? When I setup mysql do I have to specify a port or is that the default? Any help is much appreciated... I also tried the following on port 8344 to get it to open: sudo iptables -A INPUT -p tcp --dport 8344 -j ACCEPT I don't this this point really matters but i am connecting in windows 7 with a phoenix miner to ubuntu 11. |
|
|
|
Okay I have verified that bitcoind is running and that all blocks have been downloaded. Also I have run : ...on all of the ports at the top of server.json. When I try to test the ports with : ...I get a message saying connection failed/rejected for port <port>. I'm a bit lost at this point. Any help? Also is there any specific setup I would have to ensure with the port used in connecting to my mysql database? When I setup mysql do I have to specify a port or is that the default? Any help is much appreciated... |
|
|
|
Yes the block chain has been downloaded. Yes it is running. I've run killall -v bitcoind and it kills the process. How do I open 8341 port up? Below is all of my code and commands that I run but I can't seem to understand how to connect my phoenix miner to my server that is running pushpoold. The output that I get from my phoenix miner is Problems connecting to RPC. Am I supposed to connect with the port that is in bitcoin.conf (that wouldn't make sense in setting up a pool though). Server.json {
# 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" : "192.168.1.11" },
# binary protocol, localhost-only port 8339
# 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" : "pushpool",
#database username
"username" : "mysqladmin",
#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" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/pushpoold.pid",
# overrides local hostname detection
"forcehost" : "localhost.localdomain",
"log.requests" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/request.log",
"log.shares" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/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:9098/",
#Username & password to connect to bitcoind
"rpc.user" : "user",
"rpc.pass" : "pass",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}bitcoind.conf rpcuser=user
rpcpassword=pass
rpcport=9098
server=1
gen=0
rpcallowip=* commands memcached -u bitcoinminer2
./bitcoind -server -daemon
./pushpoold -E Output bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$
[2011-06-25 14:35:43.004276] Listening on host :: port 8342
[2011-06-25 14:35:43.004627] Listening on host :: port 8341
[2011-06-25 14:35:43.004749] Listening on host :: port 8344
[2011-06-25 14:35:43.004859] Listening on host 127.0.0.1 port 8338 Phoenix settings start /DC:\Phoenix phoenix.exe -u http://NH2LwYuL585o6sgiikAG42sbmAhGwj8Vsd:pass@192.168.1.11:8338/;askrate=10 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 DEVICE=0 FASTLOOP=false Mysql Commands sudo /etc/init.d/mysql start
mysql -u root -p
use pushpool Mysql Output mysql> SELECT * FROM pool_worker;
+----+------------------+------------------------------------+----------+
| id | associatedUserId | username | password |
+----+------------------+------------------------------------+----------+
| 1 | 0 | NH2LwYuL585o6sgiikAG42sbmAhGwj8Vsd | pass |
+----+------------------+------------------------------------+----------+
1 row in set (0.01 sec)
mysql> SELECT * FROM shares;
Empty set (0.00 sec)
mysql> Has bitcoind downloaded all of the blockchain yet? ./bitcoind getblockcount (should be around 133,297 right now) Is bitcoind running? ps aux | grep bitcoindHave you opened up the ports on your machine so that you can access port 8341 from the external miner? |
|
|
|
Below is all of my code and commands that I run but I can't seem to understand how to connect my phoenix miner to my server that is running pushpoold. The output that I get from my phoenix miner is Problems connecting to RPC. Am I supposed to connect with the port that is in bitcoin.conf (that wouldn't make sense in setting up a pool though). Server.json {
# 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" : "192.168.1.11" },
# binary protocol, localhost-only port 8339
# 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" : "pushpool",
#database username
"username" : "mysqladmin",
#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" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/pushpoold.pid",
# overrides local hostname detection
"forcehost" : "localhost.localdomain",
"log.requests" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/request.log",
"log.shares" : "/home/bitcoinminer2/POOLINSTALL/pushpool-0.5/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:9098/",
#Username & password to connect to bitcoind
"rpc.user" : "user",
"rpc.pass" : "pass",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}bitcoind.conf rpcuser=user
rpcpassword=pass
rpcport=9098
server=1
gen=0
rpcallowip=* commands memcached -u bitcoinminer2
./bitcoind -server -daemon
./pushpoold -E Output bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$
[2011-06-25 14:35:43.004276] Listening on host :: port 8342
[2011-06-25 14:35:43.004627] Listening on host :: port 8341
[2011-06-25 14:35:43.004749] Listening on host :: port 8344
[2011-06-25 14:35:43.004859] Listening on host 127.0.0.1 port 8338 Phoenix settings start /DC:\Phoenix phoenix.exe -u http://NH2LwYuL585o6sgiikAG42sbmAhGwj8Vsd:pass@192.168.1.11:8338/;askrate=10 -k poclbm VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128 DEVICE=0 FASTLOOP=false Mysql Commands sudo /etc/init.d/mysql start
mysql -u root -p
use pushpool Mysql Output mysql> SELECT * FROM pool_worker;
+----+------------------+------------------------------------+----------+
| id | associatedUserId | username | password |
+----+------------------+------------------------------------+----------+
| 1 | 0 | NH2LwYuL585o6sgiikAG42sbmAhGwj8Vsd | pass |
+----+------------------+------------------------------------+----------+
1 row in set (0.01 sec)
mysql> SELECT * FROM shares;
Empty set (0.00 sec)
mysql> |
|
|
|
|
Woo hoo I'm a junior member!
|
|
|
|
bitcoins may have many different uses lets make a list. the ones i've seen floating around these boards are:
1. bit porn
2. buying / selling drugs
3. hiding money from the IRS
4. gambling
5. buying babies on the black market
6. ?
If these are the only things you have seen then I would say you are an average day crackpot! =) |
|
|
|
|
Right now the Federal Reserve and the banks of the world have a monopoly on the commodity known as money/currency.
They can print as much of it as they want.
There needs to be an alternative to the fiat monopoly money system. Bitcoin gives us some hope for that to take place...
|
|
|
|
You can call me BitcoinBabe.  After almost three days and and 21 payouts, pooled mining with bitcoinplus has made me richer by 0.00082194 BTC! Ooh... Bitty!  Is that like the equivalent of less than a penny? |
|
|
|
|
Infancy stage(s). It is trying to determine its market fair value.
There will be volatility and speculators.
Will it go away? If the internet were to completely shut off then yeah. So it's bottom line value is in the electricity to mine bitcoins, the hardware purchased, and the time to maintain it.
There isn't no "value" to bitcoins other than that was us in the free market give it.
|
|
|
|
|
Last I checked the processing power was being used to secure the network not crack passwords. Keep in mind we each have the ability to turn off our computers at will and stop hashing. So i'm not sure what logic this post was based on.
|
|
|
|
Seeing as how I'm a gentleman, I'll send you a couple bitcents for tits.
She'll give you BTC tits not the real thing. |
|
|
|
|
Yes this is spam. How do we know he isnt the owner/operator of that site he posted?
|
|
|
|
|
Is this Tips as in Tips that help you learn or Tips as in Tips that you give a bus boy or stripper?
I hope it is the latter. Would be nice to get some BTC tips around here. Address below =)
|
|
|
|
|
This may sound sarcastic but if you had taken your post above and broken it up into 50 different pieces and posted them, you would likely be a junior member.
Just a thought...
|
|
|
|
|
Show Posts
