Title: Stratum Connection Interrupted Post by: The Goat Master on May 24, 2013, 09:56:18 PM My stratum connection to a pool keeps getting "interrupted" according to my cgminer.
I'm running a 64-bit version of Windows 7. thanks! Title: Re: Stratum Connection Interrupted Post by: computerparts on May 26, 2013, 12:58:28 AM Sounds like your goat got forked.
Title: Re: Stratum Connection Interrupted Post by: bitcoinreactor on August 13, 2013, 09:23:05 AM My stratum connection to a pool keeps getting "interrupted" according to my cgminer. I'm running a 64-bit version of Windows 7. thanks! i ran into that kind of problem when rewriting my own pool engine. It appears miners expects "mining.notify" notifications at various minimum intervals before considering a pool as dead, interrupting connection. for example, cgminer 3.3.3 source code include the following comment: Quote /* The protocol specifies that notify messages should be sent * every minute so if we fail to receive any for 90 seconds we * assume the connection has been dropped and treat this pool * as dead */ my rewritten pool now notifies miners at 45 seconds interval (without asking them to discard previous jobs in this case). If you're running into that "stratum connection to pool xx interrupted" problem, there are chances the chosen pool just waits for new transactions or new blocks before notifying miners. (i must admit i was first doing the same thing, as i could not see any minimum notification delay in specifications) Title: Re: Stratum Connection Interrupted Post by: The Goat Master on September 03, 2013, 10:28:34 PM My stratum connection to a pool keeps getting "interrupted" according to my cgminer. I'm running a 64-bit version of Windows 7. thanks! i ran into that kind of problem when rewriting my own pool engine. It appears miners expects "mining.notify" notifications at various minimum intervals before considering a pool as dead, interrupting connection. for example, cgminer 3.3.3 source code include the following comment: Quote /* The protocol specifies that notify messages should be sent * every minute so if we fail to receive any for 90 seconds we * assume the connection has been dropped and treat this pool * as dead */ my rewritten pool now notifies miners at 45 seconds interval (without asking them to discard previous jobs in this case). If you're running into that "stratum connection to pool xx interrupted" problem, there are chances the chosen pool just waits for new transactions or new blocks before notifying miners. (i must admit i was first doing the same thing, as i could not see any minimum notification delay in specifications) Thank you! |