Bitcoin Forum
April 24, 2024, 11:28:23 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: CGminer autoreconnect to primary?  (Read 778 times)
Ladukas (OP)
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile WWW
February 06, 2014, 05:28:51 PM
 #1

Hey guys.

Is there any simple solution how to make cgminer reconnect to primary pool from fail-over pool if primary is up again? Let's say, primary pool failed, back-up pool is used. Does cgminer check whether primary is online and does it switch the pool back?

Thanks!

You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713958103
Hero Member
*
Offline Offline

Posts: 1713958103

View Profile Personal Message (Offline)

Ignore
1713958103
Reply with quote  #2

1713958103
Report to moderator
-ck
Legendary
*
Offline Offline

Activity: 4088
Merit: 1631


Ruu \o/


View Profile WWW
February 06, 2014, 10:05:41 PM
 #2

Yes it's supposed to go back in failover mode.

Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel
2% Fee Solo mining at solo.ckpool.org
-ck
Ladukas (OP)
Member
**
Offline Offline

Activity: 70
Merit: 10


View Profile WWW
February 07, 2014, 06:54:25 AM
 #3

Yes it's supposed to go back in failover mode.

Hi, thanks for your reply.

Are you talking about --failover-only or the pools which I list in config file? Is there any way to put failover-only into config file or the only way is to put this command into the .bat file?

Cheers.

HellDiverUK
Hero Member
*****
Offline Offline

Activity: 1246
Merit: 501



View Profile
February 07, 2014, 08:55:41 AM
 #4

Yes it's supposed to go back in failover mode.

Yes, it is, isn't it?  Except quite often it never does, it just sits thee like a twat mining on the backup pool.

I see the same problem on 3.11.0 on Linux and on the dodgy patched 3.11.0 for the HEX16A2 on OpenWRT.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!