Can I as for really working and stable Monero mining pools ?
monerohash.com is stable and the op is great. though I dunno what continent you're on.
Topic: [XMR] Monero Mining - page 17. (Read 264875 times)
monerohash.com is stable and the op is great. though I dunno what continent you're on.
Can I as for really working and stable Monero mining pools ?
monerohash.com is stable and the op is great. though I dunno what continent you're on.
Can I as for really working and stable Monero mining pools ?
I was running a private pool fine with the new code... so its not the new code. Its something with your configuration. For the record, i've been using both sammy_007s branch and zone's.
It helps to know that the new code for monerod works well since that will narrow my troubleshooting. So now it looks like node is the problem. I didn't change config.json (below). Does this look ok to you? What other settings should I check?
config.json (wallet addr changed)
Code:
{
"coin": "Monero",
"symbol": "XMR",
"logging": {
"files": {
"level": "info",
"directory": "logs",
"flushInterval": 5
},
"console": {
"level": "info",
"colors": true
}
},
"poolServer": {
"enabled": true,
"clusterForks": "auto",
"poolAddress": "4mymonerowalletaddress4mymonerowalletaddress4mymonerowalletaddress4mymonerowalletaddress",
"blockRefreshInterval": 1000,
"minerTimeout": 900,
"ports": [
{
"port": 3333,
"difficulty": 100,
"desc": "Low end hardware"
}
],
"varDiff": {
"minDiff": 2,
"maxDiff": 120000,
"targetTime": 100,
"retargetTime": 30,
"variancePercent": 30,
"maxJump": 100
},
"shareTrust": {
"enabled": true,
"min": 10,
"stepDown": 3,
"threshold": 10,
"penalty": 30
},
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 25,
"checkThreshold": 30
}
},
"payments": {
"enabled": false,
"interval": 600,
"maxAddresses": 50,
"mixin": 3,
"transferFee": 50000000,
"minPayment": 1000000000,
"maxTransactionAmount": 0,
"denomination": 1000000000
},
"blockUnlocker": {
"enabled": true,
"interval": 30,
"depth": 10,
"poolFee": 0.0,
"devDonation": 0.0,
"coreDevDonation": 0.0
},
"api": {
"enabled": true,
"hashrateWindow": 600,
"updateInterval": 15,
"port": 8117,
"blocks": 30,
"payments": 30,
"password": "xxxx"
},
"daemon": {
"host": "127.0.0.1",
"port": 18081
},
"wallet": {
"host": "127.0.0.1",
"port": 8082
},
"redis": {
"host": "127.0.0.1",
"port": 6379
},
"monitoring": {
"daemon": {
"checkInterval": 60,
"rpcMethod": "getblockcount"
},
"wallet": {
"checkInterval": 60,
"rpcMethod": "getbalance"
}
},
"charts": {
"pool": {
"hashrate": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"workers": {
"enabled": true,
"updateInterval": 60,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"difficulty": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"price": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
},
"profit": {
"enabled": true,
"updateInterval": 1800,
"stepInterval": 10800,
"maximumPeriod": 604800
}
},
"user": {
"hashrate": {
"enabled": true,
"updateInterval": 180,
"stepInterval": 1800,
"maximumPeriod": 86400
},
"payments": {
"enabled": false
}
}
}
}I had been running a private Monero pool using zone117x (https://github.com/zone117x/node-cryptonote-pool) for the pool server and 0.8.8.6 monerod on Ubuntu 14.04. Then I pulled the latest Monero from github about a month ago to replace the 0.8.8.6 monerod. Now none of my mining computers can connect to the pool (all on a wireless LAN, no problems before). Did anyone else experience this? How can it be fixed?
No apparent problems when starting node:
No apparent problems when starting node:
Code:
sudo node init.js
snp code
ed to connect to 10.0.0.25 port 3333: Connection refused
[2015-10-29 23:27:41] ...retry after 10 seconds
I was running a private pool fine with the new code... so its not the new code. Its something with your configuration. For the record, i've been using both sammy_007s branch and zone's.
I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.
Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.
He may have been more interested in security functions than price action though.
Even though Satosh did not think botnet is bad for bitcoin, I think botnet is bad for Monero. One reason for the low and dropping price of Monero is that the existence of botnet on Monero network. Botnet is too large proportion of Monero hashing power. If they want to evil things to Monero, then Monero is in trouble.
Botnet or botnets? It seems to me that the motivation of botnets is the same as virtually any miner which is greed. I say virtually because some miners mine in order to obtain coins without going through an exchange and some mine to support the network. Greed is ofc the prime motivating factor for any coin including Satoshi's.
I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.
Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.
He may have been more interested in security functions than price action though.
Even though Satosh did not think botnet is bad for bitcoin, I think botnet is bad for Monero. One reason for the low and dropping price of Monero is that the existence of botnet on Monero network. Botnet is too large proportion of Monero hashing power. If they want to evil things to Monero, then Monero is in trouble.
I had been running a private Monero pool using zone117x (https://github.com/zone117x/node-cryptonote-pool) for the pool server and 0.8.8.6 monerod on Ubuntu 14.04. Then I pulled the latest Monero from github about a month ago to replace the 0.8.8.6 monerod. Now none of my mining computers can connect to the pool (all on a wireless LAN, no problems before). Did anyone else experience this? How can it be fixed?
No apparent problems when starting node:
Miner can't connect to pool:
No apparent problems when starting node:
Code:
sudo node init.js
[sudo] password for mike:
2015-10-29 23:29:03 [master] Pool spawned on 2 thread(s)
2015-10-29 23:29:04 [unlocker] Started
2015-10-29 23:29:04 [charts] Started
2015-10-29 23:29:04 [chartsDataCollector] Started
2015-10-29 23:29:04 [unlocker] No blocks candidates in redis
2015-10-29 23:29:04 [charts] Started
2015-10-29 23:29:04 [api] API started & listening on port 8117
2015-10-29 23:29:04 [api] Stat collection finished: 41 ms redis, 48 ms daemon
2015-10-29 23:29:04 [api] Broadcasting to 0 visitors and 0 address lookups
2015-10-29 23:29:04 [pool] (Thread 2) New block to mine at height 803840 w/ difficulty of 673327508
2015-10-29 23:29:04 [pool] (Thread 1) New block to mine at height 803840 w/ difficulty of 673327508
2015-10-29 23:29:04 [pool] (Thread 2) Started server listening on port 3333
2015-10-29 23:29:04 [pool] (Thread 1) Started server listening on port 3333
Miner can't connect to pool:
Code:
sudo ./minerd -a cryptonight -o stratum+tcp://10.0.0.25:3333 -u 4moneroaddressthisismymonerowalletaddressthisismymonerowalletaddressthisismymonerowalletaddress -p x -t 3
[sudo] password for mike:
[2015-10-29 23:27:41] Using JSON-RPC 2.0
[2015-10-29 23:27:41] Starting Stratum on stratum+tcp://10.0.0.25:3333
[2015-10-29 23:27:41] 3 miner threads started, using 'cryptonight' algorithm.
[2015-10-29 23:27:41] Stratum connection failed: Failed to connect to 10.0.0.25 port 3333: Connection refused
[2015-10-29 23:27:41] ...retry after 10 seconds
I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.
Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.
He may have been more interested in security functions than price action though.
it just so happens that I have one machine with the 33x and one with the 35x
fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)
3 hash/s seems to small to make a real difference IMO.
Have you tested it for at least 24 hours ?
yeah. literally, my 750 tis get 247 h/s on newer stuff, and 250 on old stuff
fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)
3 hash/s seems to small to make a real difference IMO.
Have you tested it for at least 24 hours ?
Anyone mining XMR with a nVidia GPU on Windows 10? It was working great for me (using tsiv's miner) on previous drivers but when I upgraded to 355.78 I keep getting "result for nonce does not validate" error messages while mining. Now obviously the smart thing to do is roll back drivers which I've done and it works again, but, does anyone have any insight as to why this is happening? I'm not running overclocked on my GPU, it's properly cooled and seems to be an issue with the drivers and nothing more. Perhaps it's a driver/Win10 incompatibility. Is everyone still using tsiv's miner on Windows? It was last updated over a year ago so if anyone can recommend me another nVidia GPU miner to try and see if that fixes my problem, that would be great!
Just an FYI for everyone... I've updated to 358.78 and it seems the validate errors are gone. I'll keep an eye on it but whatever changes nVidia made they've either fixed or reverted.
fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)
Anyone mining XMR with a nVidia GPU on Windows 10? It was working great for me (using tsiv's miner) on previous drivers but when I upgraded to 355.78 I keep getting "result for nonce does not validate" error messages while mining. Now obviously the smart thing to do is roll back drivers which I've done and it works again, but, does anyone have any insight as to why this is happening? I'm not running overclocked on my GPU, it's properly cooled and seems to be an issue with the drivers and nothing more. Perhaps it's a driver/Win10 incompatibility. Is everyone still using tsiv's miner on Windows? It was last updated over a year ago so if anyone can recommend me another nVidia GPU miner to try and see if that fixes my problem, that would be great!
Just an FYI for everyone... I've updated to 358.78 and it seems the validate errors are gone. I'll keep an eye on it but whatever changes nVidia made they've either fixed or reverted.
for reference. This was on the ccminer sp_ thread, and on the bounties thread
https://bitcointalksearch.org/topic/m.11778630
How much are you pulling at the wall in watts running these 3 GTX 970's ?
Can you tell me what your average hash rate is with this card? I'm guessing 320-360 KH/s
Monero Miners:
There's an effort to fund djm34 to work on the nvidia mining software
https://forum.getmonero.org/8/funding-required/2355/improved-nvidia-mining-software
As detailed in the post and in my discussion with djm34, one of the primary goals of his work is to increase the hashrate of the nvidia cards (why a 970 only gets ~400 is frustrating, when a 750 gets 250). Secondary goals are a lot of general software improvements - this first milestone was created in lieu of a "downpayment", designed so that even if djm34 can't get the hashrate to increase, he can still get paid for his work, and the monero mining community receives something for their money (improved GPU miner, for instance with the ability to solo mine - something that is crucial for continued decentralization of Monero).
Only 1500 more xmr to go!
There's an effort to fund djm34 to work on the nvidia mining software
https://forum.getmonero.org/8/funding-required/2355/improved-nvidia-mining-software
As detailed in the post and in my discussion with djm34, one of the primary goals of his work is to increase the hashrate of the nvidia cards (why a 970 only gets ~400 is frustrating, when a 750 gets 250). Secondary goals are a lot of general software improvements - this first milestone was created in lieu of a "downpayment", designed so that even if djm34 can't get the hashrate to increase, he can still get paid for his work, and the monero mining community receives something for their money (improved GPU miner, for instance with the ability to solo mine - something that is crucial for continued decentralization of Monero).
Only 1500 more xmr to go!
Anyone mining XMR with a nVidia GPU on Windows 10? It was working great for me (using tsiv's miner) on previous drivers but when I upgraded to 355.78 I keep getting "result for nonce does not validate" error messages while mining. Now obviously the smart thing to do is roll back drivers which I've done and it works again, but, does anyone have any insight as to why this is happening? I'm not running overclocked on my GPU, it's properly cooled and seems to be an issue with the drivers and nothing more. Perhaps it's a driver/Win10 incompatibility. Is everyone still using tsiv's miner on Windows? It was last updated over a year ago so if anyone can recommend me another nVidia GPU miner to try and see if that fixes my problem, that would be great!
Just curious: how do I know if it was my miner that found a block on a pool?
It will report it in the console you are running it
Just curious: how do I know if it was my miner that found a block on a pool?
Monero mining on nvidia maxwell hardware. I'm posting this again here because this is where it should be.
I assume you're talking about tsivs miner. I've found you have to end up having all of the below nonsense for it to work - probably some library dependency. So I could post my binary, but i've copied binaries from one linux box to another and it didn't work (forget why), so I just ended up following these from start to finish.
step 0: set up your miner box to run headless via SSH. This is the best way. You might be able to pull off using your video card and mining at the same time, but I wouldn't recommend it.
First, install an nvidia driver. I've found 331 works the best for a 750 ti.
http://www.noobslab.com/2014/12/use-nvidia-graphics-drivers-in.html
Then, go through this nightmare to install the CUDA nonsense. Start at Step 4, stop at step 30.
https://d3adbra1n.wordpress.com/2014/05/03/cuda-miner-installation-on-a-fresh-ubuntu-14-04-lts/
Tip: when the long ass agreement thing pops up, you can hit ctrl-c to skip straight to typing accept. I didn't know this for a long time and would just put a weight on my down arrow to scroll through the thing. Or whatever the scroll was.
When you get to step 30, do this instead:
that'll plop it in /ccminer-cryptonight/
then pick it up from step 35.
A reboot is required to get your video driver working (from my experience).
The, you can paste in the command line provided by the pool website, for example
I assume you're talking about tsivs miner. I've found you have to end up having all of the below nonsense for it to work - probably some library dependency. So I could post my binary, but i've copied binaries from one linux box to another and it didn't work (forget why), so I just ended up following these from start to finish.
step 0: set up your miner box to run headless via SSH. This is the best way. You might be able to pull off using your video card and mining at the same time, but I wouldn't recommend it.
First, install an nvidia driver. I've found 331 works the best for a 750 ti.
http://www.noobslab.com/2014/12/use-nvidia-graphics-drivers-in.html
Then, go through this nightmare to install the CUDA nonsense. Start at Step 4, stop at step 30.
https://d3adbra1n.wordpress.com/2014/05/03/cuda-miner-installation-on-a-fresh-ubuntu-14-04-lts/
Tip: when the long ass agreement thing pops up, you can hit ctrl-c to skip straight to typing accept. I didn't know this for a long time and would just put a weight on my down arrow to scroll through the thing. Or whatever the scroll was.
When you get to step 30, do this instead:
Code:
git clone git://github.com/tsiv/ccminer-cryptonight
that'll plop it in /ccminer-cryptonight/
then pick it up from step 35.
A reboot is required to get your video driver working (from my experience).
The, you can paste in the command line provided by the pool website, for example
Code:
./ccminer -o stratum+tcp://monerohash.com:3333 -u YOUR_WALLET_ADDRESS -p x
Jump to: