I've noticed a problem with bitHopper on one of my mining rigs; the problem doesn't seem to affect the others.
It seems to ONLY mine on my backup pool, eligius.
I have other pools configured as the "mine" role, but none of them are chosen.
I just briefly saw it choose one pool for 7 shares, then it jumped right back to Eligius.
I thought maybe it had to do with the share counts (and reject counts) so I stopped it, blew away the stats.db, and restarted it.
Again it is only mining on Eligius.
The code is identical to my other rigs, and those rigs have identical cfg files which define identical pools.
It's the same version of git code too, so the algorithms they're using are the same too.
Can anyone offer a suggestion on why one rig is choosing my "backup" pool while the other rigs are properly hopping between my "mine" pools?
I think you might find all pools are above the jump off point. When there are no other suitable pools bitHopper defaults to XXPPS type pool until a better pool is found.