Hi, im running cgminer ( w scrypt) and i have setup my config file this way expecting it to connect to a different pool when my first one disconnects for whatever reason but it is not launching the second one.
I have noticed only once when i launched miner for first time it auto connected to second one and then back to first one shortly after
Is there something additional needed in config or is this not possible ?
{
"pools" : [
{
"url" : "pool1",
"user" : "username",
"pass" : "password"
},
{
"url" : "pool2",
"user" : "username",
"pass" : "password"
}
]
Yes, there should be more lines than that in your config.
1) While cgminer is running, press "p" to open up the pools menu and then press "s" to select a pool management strategy.
2) After changing the strategy, press any key to get back to the main cgminer screen.
3) From the main cgminer screen, press "s" to open up the settings menu, then "w" to write a correctly formatted config file.
4) If you are under a sub menu, press any key again to get back to the main cgminer screen.
5) press "q" to quit cgminer
6) Look in the new config file. Assuming you're on cgminer 3.8.3 or newer, you should see that your config file looks much more like this:
{
"pools" : [
{
"quota" : "200;stratum+tcp://primary_pool_used_for_mining",
"user" : "username",
"pass" : "whatever"
},
{
"quota" : "1;stratum+tcp://secondary_pool_used_for_failover",
"user" : "username",
"pass" : "whatever"
}
]
,
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "120",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"no-submit-stale" : true,
"queue" : "3",
"scan-time" : "60",
"shares" : "0",
"load-balance" : true,
"kernel-path" : "/usr/lib/cgminer"
}
That's basically what mine looks like because I use "load balance" mode instead of failover.
This example config always does SOME work on the failover pool, but does most of the work (
attempting up to 200 times as much work) on the primary pool. Whenever the primary pool is unavailable, the quota setting on the primary pool is no longer important, and instead the secondary pool will get 100% of the mining.
Either way, I'm pretty sure the answer is:
"yes, you should probably have more lines than that in your cgminer.conf if it's not corrupt"
