 Show Posts
|
|
Pages: [1] 2 3 »
|
It looks like you don't own address mentioned That is my wallet address, it is through coinbase is that the issue? Coinbase owns Coinbase addresses. They agree to credit your account and allow withdrawals, but they maintain control of 100% of the bitcoin addresses they use. If you want to sign messages, you have to create a new bitcoin address that you control the private key to. Then, you can sign messages like the Eligius message. Make sure you understand this before you do it, as you will have to manage your BTC address and payments. Also, Elgius uses coinbase (small c) payments, which many exchanges and brokers have trouble with, so I wouldn't use a Coinbase (large c) address with any mining pool. Thanks for your help, I have had this address for a while now and have used it on various pools without any problems. I will just leave the settings as default. Thanks again. |
|
|
|
It looks like you don't own address mentioned That is my wallet address, it is through coinbase is that the issue? |
|
|
|
I hope someone can help
I have a Antminer S2, it has been running fine for the past 2 months, yesterday it just stopped hashing. I reseated all the boards and re loaded the firmware and reset but still nothing. It seems the main board might be faulty, when I start it up the red light and 4 green lights on the main board light up and flicker as it boots up the 4 greens lights go off and all the fans go off, on the display screen it has the IP address and 0GH/s and 0 degrees in the temp. I have emailed Bitmain a few times with photo's and a video of what is happening but haven't heard from them.
Have you replaced the total-crap, underpowered stock 1000w Enermax PSU yet with a more suitable 1200-1300w PSU? If not, you might want to try that first. No still running the stock PSU. I think I fixed the problem, I think it is the heat sensor in the main board, I un-ticked it in the settings page and it is now working. |
|
|
|
|
I hope someone can help
I have a Antminer S2, it has been running fine for the past 2 months, yesterday it just stopped hashing. I reseated all the boards and re loaded the firmware and reset but still nothing. It seems the main board might be faulty, when I start it up the red light and 4 green lights on the main board light up and flicker as it boots up the 4 greens lights go off and all the fans go off, on the display screen it has the IP address and 0GH/s and 0 degrees in the temp. I have emailed Bitmain a few times with photo's and a video of what is happening but haven't heard from them.
|
|
|
|
Thanks for that, is it ready to download and try out? |
|
|
|
|
Any news on an update for S2's I have 2 of them running on p2pool but only get between 750-850GH/s, they seem to start out ok but drop off over time, I don't want to move them to another pool but might have to.
|
|
|
|
I have a question, I have setup 2 nodes one has my S1's hooked to it and the other has my S2's attached to it, they seem to hash a lot better doing it that way. If I have them all on the same node my total hashing power decreases, will the slower hashing of the S1's bring down the S2 hashing rate or does it make no difference? Are there any pros or cons of running 2 nodes?
One node should be able to handle both. There are known problems with S2s working on p2pool. But if you found a way to get it to work, do share.  M Thanks for your feed back, I know of the problem with S2's on p2pool so have just been playing around a bit, when I had them on the one node with the S1's my S2's hashed around 750-850 GH/s when I put them on there own on the second node I'm getting around 950 GH/s not sure if it is a work around as I have only had it running for a day so will test it for a couple of weeks. I have them all running with the same wallet. EDIT: No my S2's have dropped off again back down to 750 -800 GH/s I hope something gets done to fix this soon. |
|
|
|
|
I have a question, I have setup 2 nodes one has my S1's hooked to it and the other has my S2's attached to it, they seem to hash a lot better doing it that way. If I have them all on the same node my total hashing power decreases, will the slower hashing of the S1's bring down the S2 hashing rate or does it make no difference? Are there any pros or cons of running 2 nodes?
|
|
|
|
|
There is an update for the p2pool software, not sure when it came out but I just applied the updates and now my S2's are hashing at the full 1ths.
|
|
|
|
Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot. andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password> 2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty) 2014-06-04 04:53:52.347840 2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to ' http://127.0.0.1:8332/' with username 'xxxxxxx'... 2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection: 2014-06-04 04:53:52.349666 > Traceback (most recent call last): 2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused. 2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection: 2014-06-04 04:53:53.351698 > Traceback (most recent call last): 2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused You have any restrictions on the number of connections allowed to your bitcoind process? Did you try stopping/restarting bitcoind? Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)? Can you telnet into that IP/port successfully? Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now. andmax, are <username> <password> the same you have inside .bitcoin/bitcoin.conf's rpcuser/rpcpassword keys ? spiccioli Yes username and password in bitcoin.conf are the same as on my command line to start p2pool, thanks for your help just want to get it back up and running again as I'm in Australia and no p2pool nodes close by to hook into. |
|
|
|
Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot. andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password> 2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty) 2014-06-04 04:53:52.347840 2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to ' http://127.0.0.1:8332/' with username 'xxxxxxx'... 2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection: 2014-06-04 04:53:52.349666 > Traceback (most recent call last): 2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused. 2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection: 2014-06-04 04:53:53.351698 > Traceback (most recent call last): 2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused You have any restrictions on the number of connections allowed to your bitcoind process? Did you try stopping/restarting bitcoind? Does Ubuntu 14.04 have some kind of built-in security that you need to allow port 8332 traffic (sorry, don't know that distribution well enough)? Can you telnet into that IP/port successfully? Sorry I'm new to Ubuntu, it has been running fine for the last month, I rebooted as there was a Ubuntu update and then I got this error. I have re formatted re-installed Ubuntu, Bitcoin Qt and p2pool so now have a fresh install but still getting this error. How can I see if Ubuntu is blocking port 8332 and if bitcoin is restricting a number of connections. When I first installed it it ran perfectly so not sure why I'm getting this now. |
|
|
|
Can anyone help me I rebooted my p2pool node running on Ubuntu 14.04 and I get this error. Bitcoin Qt is running and up to date. My node has been running fine up until the last reboot. andrew@andrew-Inspiron-530s:~$ python ~/p2pool/run_p2pool.py -n 82.196.8.44:9333 -n 146.185.183.227:9333 <username> <password> 2014-06-04 04:53:52.347693 p2pool (version 13.4-24-gf0eeb48-dirty) 2014-06-04 04:53:52.347840 2014-06-04 04:53:52.347932 Testing bitcoind RPC connection to ' http://127.0.0.1:8332/' with username 'xxxxxxx'... 2014-06-04 04:53:52.349553 > Error while checking Bitcoin connection: 2014-06-04 04:53:52.349666 > Traceback (most recent call last): 2014-06-04 04:53:52.349720 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused. 2014-06-04 04:53:53.351541 > Error while checking Bitcoin connection: 2014-06-04 04:53:53.351698 > Traceback (most recent call last): 2014-06-04 04:53:53.351770 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused |
|
|
|
I have been running my p2pool node successfully on my Ubuntu 14.04 computer, I just did some updates on the computer and restarted it now when I try to restart my p2pool server I get this error, Bitcoin is running and up to date. Can someone please point me in the right direction to get it back running again. 2014-06-03 11:58:59.174760 p2pool (version 13.4-24-gf0eeb48-dirty) 2014-06-03 11:58:59.174903 2014-06-03 11:58:59.174990 Testing bitcoind RPC connection to ' http://127.0.0.1:8332/' with username 'andmax'... 2014-06-03 11:58:59.176566 > Error while checking Bitcoin connection: 2014-06-03 11:58:59.176685 > Traceback (most recent call last): 2014-06-03 11:58:59.176738 > Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused. |
|
|
|
I've just got a few S1's and are mining on my node, what does the update fix? |
|
|
|
I have just received my new Ant S1's trying to connect them to my node on the local network I have setup the following 3 pools
Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333
but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.
I'm a relative P2Pool noob myself running an S1 and was able to get it going without too much difficulty. Had a couple of minor IP addressing issues myself, but fully operator error. I'm about 10 days ahead of you on this so will offer my "noob" experience. You say you were mining for awhile with U1s...were those mining to the same local p2pool node at 192.168.1.20? You mention dhcp...I'm assuming the machine you're running your node on is configured to use 192.168.1.20 as a static address rather than getting dhcp leases? That was one of my early problems...I'd assumed my machine was using a static (as I try to avoid DHCP as a rule on LANs) and I tried a bunch of other things before it occured to me that dynamic ip addressing was the issue. Since you can ping 192.168.1.20 but the ant doesn't see the pool its a possibility that you're pinging a different machine thats not running the p2pool and your bitcoind (or qt). Lastly, your bitcoind is running and fully synced? In addition to a screenshot of your S! config screen a shot of your P2Pool window would be helpful as well good luck Thanks everyone for your help, Yes my node is setup with static ip 192.168.1.20. I received an email from Bitmain yesterday saying that the order you put the pools in on the config page isn't necessarily the order they connect at, the S1 will connect to the pool that responds the quickest, whether that is correct or not I don't know but I just removed Eclipse from my list and it connected up to my node fine, still doesn't show up my mates node as alive in the list on the miner status page as his node is my backup node in "Pool 2" but it is working now, thanks for all your help. EDIT: I figured out the problem, there needs to be a password in the password section for each pool, even though you don't need a password to join a p2pool node the software needs something in there to work. Hope this helps someone else. Thanks everyone |
|
|
|
I have just received my new Ant S1's trying to connect them to my node on the local network I have setup the following 3 pools
Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333
but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.
I use: http://192.168.0.194:9332so, try putting the http:// in front of it. M No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client sounds like a routing problem? What happens if you put http://192.168.1.20:9332 in your browser? M I get my node webpage. I have been mining with Antminer U1's for a few months now without a problem I can ping 192.168.1.20 from the network/diagnostics tab on the Ant S1 and it finds it It won't connect to any p2pools I've tried a few and no connection, my mate had the same problem with his S1's in Houston Texas, will only connect to mining pools, so there must be a setting within the S1 that needs fixing |
|
|
|
I have just received my new Ant S1's trying to connect them to my node on the local network I have setup the following 3 pools
Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333
but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.
I use: http://192.168.0.194:9332so, try putting the http:// in front of it. M No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client |
|
|
|
|
I have just received my new Ant S1's trying to connect them to my node on the local network I have setup the following 3 pools
Pool 1 192.168.1.20:9332
Pool 2 100.166.178.107:9332
pool 3 us2.eclipsemc.com:3333
but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.
|
|
|
|
If anyone is thinking of buying a Antminer S2 from Bitmain in the next couple of weeks I have a couple of US$400 off vouchers I can donate, you need an account with Bitmain so I can transfer them over. Andrew  |
|
|
|
|
