BAMT jumping between pools when 1st pool fails

[chungenhung]

Per the BAMT wiki page
https://github.com/aaronwolfe/Big-A-Miner-Thing/wiki/Using-bamt

So basically, if you want to mostly mine at the first pool in your file, but fail over to another pool if #1 is down, then try to go back to #1 every so often... put this in your pools file:

http://u:p@mymainpool.com http://u:p@mybackuppool.com,10,60

I have it set up as:

Code:

http://u:p@pool1.com:8332/
http://u:p@pool2.com:8332/,10,60
http://u:p@pool3.com:8332/,10,60
http://u:p@pool4.com:8332/,10,60

It was suppose to go to pool2, work 10 shares, check pool1. If pool1 still down, keep working on pool2. It should only drop down to pool3 if pool1 and pool2 are down.

However, my observation shows that when pool1 fails, it will go to pool2, work for 10 shares, switch to pool3, work for 10 shares, switch to pool4, work for 10 shares, switch to pool2, and the cycle goes on and on. Why is it dropping to pool3 even when pool2 is available?


Any ideas?

[gnar1ta$]

What's your hashrate? Your also telling it to switch if it doesn't find a share in 60 seconds.  I think your syntax is wrong also try

Code:

http://u:p@pool2.com:8332,10,60

[chungenhung]

hashrate is normal, around 300MH/s for me.
The syntax on the example file is

Code:

http://yourmom:thiswontwork@pool.bitclockers.com:8332/
http://yourmom:sogetyourown@pool2.bitclockers.com:8332/
http://yourmom:please@deepbit.net:8332/

[gnar1ta$]

Get rid of the last / before comma and change to 120 or 90 instead of 60. Luck and pool connection can jump you over 60 seconds. What's the timeout set at in bamt.conf?

[chungenhung]

Get rid of the last / before comma and change to 120 or 90 instead of 60. Luck and pool connection can jump you over 60 seconds. What's the timeout set at in bamt.conf?

timeout is set to 180 (default) in bamt.conf

[gnar1ta$]

Code:

http://u:p@pool1.com:8332/
http://u:p@pool2.com:8332/,10,60
http://u:p@pool3.com:8332/,10,60
http://u:p@pool4.com:8332/,10,60

So with this your backup pools time out 3 times faster than your primary. 60 is a bit aggressive for 300 Mhash. It sounds like its timing out and failing forward instead of checking back to primary. Try just ,10 so you don't override the bamt.conf timeout.