I plugged the miners into a cheap 10port switch and voila! they al started hashing at full speed accept shares no disconnects or lost shares 
Topic: cgminer "stratum connection to pool 0 interrupted" issue (Read 42417 times)
Also getting lost shares stratum not connecting to pool etc. after checking everything network card internet etc I turned out to be my usb switch I plugged the miners into a cheap 10port switch and voila! they al started hashing at full speed accept shares no disconnects or lost shares
I plugged the miners into a cheap 10port switch and voila! they al started hashing at full speed accept shares no disconnects or lost shares 
There appears to be some bug in the firmware/software/hardware combination that is SP30/31 and static IP addresses. I don't have one so can only offer advice generically, but using DHCP fixes the issue.
Thank you Con!
Interesting the fact that this only happens with static IP ... its definitively not a Firewall thing ....
Interesting the fact that this only happens with static IP ... its definitively not a Firewall thing ....
Check your firewall/gateway. It might not like you running a static ip address unless you add it to address reservation.
Hello, I am running a SP30 and I have this issue .. the miner simple does not mine and is always giving the following messages
Stratum connection to pool 0 interrupted.
Lost X shares due to stratum disconnect on pool 0
Stratum from pool 0 requested work restart
Any ideas?
PS: This behavior is only true if the machine uses a static IP address ... with DHCP it works fine
Stratum connection to pool 0 interrupted.
Lost X shares due to stratum disconnect on pool 0
Stratum from pool 0 requested work restart
Any ideas?
PS: This behavior is only true if the machine uses a static IP address ... with DHCP it works fine
The fork of my miner uses the original stratum code I wrote for cgminer which used libcurl to set up the stratum socket connection. When this problem originally occurred, it would crash in libcurl. After tons of debugging I had so many crashes due to libcurl bugs that I decided to abandon using libcurl and just use raw socket code for all stratum code. That fixed the crashes (on both linux and windows) but on windows for some reason a socket just hangs up and never returns without any meaningful failure that should normally happen instead. That's why this bug manifests in two different ways. Older versions of cgminer would also crash during this interruption if you read back through this thread. However so many other crashes were fixed by abandoning libcurl that it was worth it. It's worth noting that improvements to this code keep going in and as recently as 3.3.2 another stratum disconnect issue was fixed, so if you're on an older version I highly recommend upgrading to 3.3.4 (the latest).
Actually, the BFGMiner crash (now fixed) was in entirely independent code that never appeared in cgminer.Nor can cgminer's former crashes be blamed on libcurl.
I found the bug in the stratum code, fixed it, and even offered it to you for cgminer.
You chose to ignore it.
The only reason switching to raw sockets fixed cgminer was because you removed the offending code in the process.
BFGMiner 3.2.0 has the stratum crashes fixed while still using libcurl so it's proxy-friendly.
3.34 has finally fixed this pesky issue?
thanks for all the hard work btw
thanks for all the hard work btw
The fork of my miner uses the original stratum code I wrote for cgminer which used libcurl to set up the stratum socket connection. When this problem originally occurred, it would crash in libcurl. After tons of debugging I had so many crashes due to libcurl bugs that I decided to abandon using libcurl and just use raw socket code for all stratum code. That fixed the crashes (on both linux and windows) but on windows for some reason a socket just hangs up and never returns without any meaningful failure that should normally happen instead. That's why this bug manifests in two different ways. Older versions of cgminer would also crash during this interruption if you read back through this thread. However so many other crashes were fixed by abandoning libcurl that it was worth it. It's worth noting that improvements to this code keep going in and as recently as 3.3.2 another stratum disconnect issue was fixed, so if you're on an older version I highly recommend upgrading to 3.3.4 (the latest).
I get this issue too in cgminer, but it occurs differently in bfgminer. Instead of hanging, it causes a miner software crash (it'll just close in latest revision. if debug log is on you will see some hex codes and dll files in the log).
theres definitely something in common between the two that prevent a connection recovery.
Incidentally, if I don't use stratum and I use getwork instead, crashes/hangs never happen and if a connection is interrupted, it recovers gracefully.
theres definitely something in common between the two that prevent a connection recovery.
Incidentally, if I don't use stratum and I use getwork instead, crashes/hangs never happen and if a connection is interrupted, it recovers gracefully.
I had a couple of my cgminers go offline with the message "stratum connection to pool 0 interrupted", a third however, which was mining on the same pool did not disconnect and kept running fine. I noticed it an hour later... 
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
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 */
* 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)
I have always had these messages (regularly) for the backup / block detection pools on my computers that solo mine:
Computer 1: Desktop PC, Vista 64 bit, 4x GPU, cgminer 3.3.0
Computer 2: Samsung Netbook, Win 7 32 bit, Block erupter USB's, cgminer 3.1.1
Each with:
3 stratum pools URLs,
1 LP pool URL
I have always assumed the errors were related to high network traffic or the fact all the pools have 250+ ms pings (because of my location). Cgminer never crashes or hangs though..
Computer 1: Desktop PC, Vista 64 bit, 4x GPU, cgminer 3.3.0
Computer 2: Samsung Netbook, Win 7 32 bit, Block erupter USB's, cgminer 3.1.1
Each with:
3 stratum pools URLs,
1 LP pool URL
I have always assumed the errors were related to high network traffic or the fact all the pools have 250+ ms pings (because of my location). Cgminer never crashes or hangs though..
I am also getting the "stratum connection to pool 0 interrupted" hang issue with 3.3.1 and windows 7
Have to close the command window and start a fresh one.
Have to close the command window and start a fresh one.
Today It seems I got connectivity problems with long poll. At least when I came home I've noticed there is something about no connection and caching the results. And cgminer wasn't hashing for several hours.
I did not set backup pool, so maybe thus cgminer wasn't able to recover.
Something is wrong with cgminer not recovering still.
I did not set backup pool, so maybe thus cgminer wasn't able to recover.
Something is wrong with cgminer not recovering still.
I completely missed that option. I am setting it now and hope that works.
What sucks is that cgwatcher doesn't catch this. Often I will head to bed at like 1am and wake up in the morning to see that the last activity in cgminer is interrupted at 1:45am.
Have you tried the 'restart cgminer if shares haven't changed in 10 minutes'? Works for me--at least in the context you've described, at a high level. Good luck...
Same problem and same solution as you.
Using cgminer 3.3.1 on Windows 7 x64. "Lost xx shares due to stratum disconnect" and cgminer never recovers from it. Note, that only happens sometimes, at other times it will go to the failover pool.
Cgwatcher fails at monitoring the drop in hash rate (the cgminer window still shows the last value before the disconnect), however "restart cgminer if shares haven't changed in x minutes" works just fine.
What sucks is that cgwatcher doesn't catch this. Often I will head to bed at like 1am and wake up in the morning to see that the last activity in cgminer is interrupted at 1:45am.
Have you tried the 'restart cgminer if shares haven't changed in 10 minutes'? Works for me--at least in the context you've described, at a high level. Good luck...
What sucks is that cgwatcher doesn't catch this. Often I will head to bed at like 1am and wake up in the morning to see that the last activity in cgminer is interrupted at 1:45am. You can still ping it, you can still vnc into it. Not sure how I can detect there is a problem other than a managed pool that emails you when it hasn't received shares in awhile.
It happens to me sometimes with rigs on the same network. It will say "... interrupted" and never reconnect but other miners are fine and never disconnected in the first place so the pool isn't the issue. Sometimes it reconnects but lately it hasn't.
Good summary of what I'm experiencing. I'd only add that two win7 rigs on the same hub as a linux rig, the win7s puke often. The linux rig is a rock.
It happens to me sometimes with rigs on the same network. It will say "... interrupted" and never reconnect but other miners are fine and never disconnected in the first place so the pool isn't the issue. Sometimes it reconnects but lately it hasn't.
Trying to figure out how to get around this atm...
Trying to figure out how to get around this atm...
I haven't found cgminer dead in the water for some time now, but cgwatcher has restarted one rig a couple times a day due to 'no new shares submitted for x minutes'. I can't say if that's stratum interrupt, or some other issue, but I don't care with cgwatcher babysitting.
Thanks for the updated software, ck!
Thanks for the updated software, ck!
thats why it is a good idea to throw in an extra network card & cheap hub then split it off,
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
The fact connection interrupts is not a problem itself. The problem is that cgminer never recovers after interruption for us.
Yup im still having same problem in every version of cgminer, ya cgminer never recovers after it got interrupted stratum, so no matter failOver setting i set, it never be recover
thats why it is a good idea to throw in an extra network card & cheap hub then split it off,
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
The fact connection interrupts is not a problem itself. The problem is that cgminer never recovers after interruption for us.
thats why it is a good idea to throw in an extra network card & cheap hub then split it off,
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
or re-direct the miner traffic via WIFI to a separate hub......, keeping the big traffic on a switch.
Personally I also keep a mobile phone on standby with a bluetooth network redirector setup in the controlling SBC, should it loose connectivity via cable/WIFI....
I upgraded to 3.3.0 and was still getting stratum connection interrupted messages on all 3 pools.
On the same home network my miner is hooked, I was running a large file copy (50+ GB) to the NAS that was hogging network bandwidth. Once that completed, the stratum interrupted errors disappeared.
On the same home network my miner is hooked, I was running a large file copy (50+ GB) to the NAS that was hogging network bandwidth. Once that completed, the stratum interrupted errors disappeared.
Seems to still be an issue. I upgraded all 6 of my miners to 3.2.2 last night and this morning 2 of them were hung with the last entry being "lost xx shares due to stratum disconnect". I am using BTCGuild.
I believe I may have found the cause for this issue at long last and I have put generic fixes into cgminer 3.2.2 which was released yesterday that should hopefully address them.
same here
i have the same problem as u guys here.. keep getting stratum connection interupted error, ive tried cgminer 3.2.1, 3.1.0, 3.1.1... they giving me same problem.
Thank you! Will report if problem still persists.
Latest cgminer version is 3.2.1. Stratum changes went into 3.2.0.
Now problem became even more "funnier". I switched backup LP pool with Stratum pool. So main pool is LP one. Now cgminer hangs when backup pool reports about new block!
Have this annoying problem. Updated to 3.1.1 - nothing changes, I still get stratum connection to pool 0 interrupted with cgminer becoming unresponsive after that.
May the cause be that I have non-stratum backup pool?
May the cause be that I have non-stratum backup pool?
Thanks for the info. It looks like CGWatcher should do the trick. Also good to know I'm not the only one with frequent upsets.
My final answer (for windows) is using CGWatcher: http://manotechnology.blogspot.com/p/cgwatcher.html
CGWatcher coupled with failover configurations in cgminer, will handle stratum disconnections, sick cards, drivers restarting, shares not being submitted, mhs decreases, and more. Configure windows to start cgwatcher on startup, save cgminer settings to default conf, configure cgwatcher to start cgminer automatically when cgwatcher starts, check all montior boxes (except restart based on hours, and except start/stop by schedule, and let 'er rip.
Cgminer poops out due to sick cards and network issues on my windows rigs, and cgwatcher restarts cgminer automatically. My worst rig restarts cgminer about four times a day. My best rig restarts cgminer about once every two days.
CGWatcher coupled with failover configurations in cgminer, will handle stratum disconnections, sick cards, drivers restarting, shares not being submitted, mhs decreases, and more. Configure windows to start cgwatcher on startup, save cgminer settings to default conf, configure cgwatcher to start cgminer automatically when cgwatcher starts, check all montior boxes (except restart based on hours, and except start/stop by schedule, and let 'er rip.
Cgminer poops out due to sick cards and network issues on my windows rigs, and cgwatcher restarts cgminer automatically. My worst rig restarts cgminer about four times a day. My best rig restarts cgminer about once every two days.
I had a couple of my cgminers go offline with the message "stratum connection to pool 0 interrupted", a third however, which was mining on the same pool did not disconnect and kept running fine. I noticed it an hour later...
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
I've had the same experiences. I've got 2 rigs mining at separate locations. One is a single 7970 running 3.1.0 and the other is running 2 7970's with 3.1.1. The rig running 3.1.1 seems to drop out more often - about twice a day. Is it a stability issue? I'm running the single card rig stock (69 degrees C), the other rig is running both cards @ 1000MHz core, 925MHz RAM, 70 degrees C. Is this issue because the cards are throwing garbage at cgminer, or a network connection is flakey, or something else? They always seem to drop out at the worst times - like 5 minutes after I go to bed...
If no one has a solution to the cgminer issue, does anyone have a good way of alerting you if a miner stops submitting shares?
I'm using 7970s too, with stock voltage. cgminer does the overclocking just fine, and I suppose it would do the voltage if the voltage wasn't locked on my gigabytes. I wonder if TRIXX might install in Linux with mono/wine? I'll try and post back.
To unlock the voltage, I'm considering updating the bios on the cards per this post: https://bitcointalk.org/index.php?topic=186624.40
But for now, I just want the miners to keep working through the night.
To unlock the voltage, I'm considering updating the bios on the cards per this post: https://bitcointalk.org/index.php?topic=186624.40
But for now, I just want the miners to keep working through the night.
I'd love to move back to Linux, but I'm running 7970's.
I rely on Sapphire Trixx to overclock and undervolt. If the cg team could reverse engineer the undocumented calls Trixx was making I'd be laughing.
Actually, we don't need to rely on cgminer, an external tool would suffice - as Trixx does now. I'm surprised no one has put a bounty up for a linux tool for 7970 over/under clocking/volting.
I rely on Sapphire Trixx to overclock and undervolt. If the cg team could reverse engineer the undocumented calls Trixx was making I'd be laughing.
Actually, we don't need to rely on cgminer, an external tool would suffice - as Trixx does now. I'm surprised no one has put a bounty up for a linux tool for 7970 over/under clocking/volting.
I've concluded that Windows 7 Professional simply sucks. I'm using cgminer 3.0.0 on Linux Mint, and it has been running for four days without issue. My winblows machines are unreliable with cgminer 3.1.1, and have died many times in the same four days.
My ISP briefly cuts internet access almost every night around 1:30am, and cgminer doesn't like how winblows recovers. It's just a hiccup for linux. The bitminter client does better than cgminer on winblows when recovering from the interruption, but bitminter is not half the miner that cgminer is.
I'll be converting my winblows to linux. So far, that's the only solution I'm able to come up with.
Thanks for the great tool and support, ckolivas.
My ISP briefly cuts internet access almost every night around 1:30am, and cgminer doesn't like how winblows recovers. It's just a hiccup for linux. The bitminter client does better than cgminer on winblows when recovering from the interruption, but bitminter is not half the miner that cgminer is.
I'll be converting my winblows to linux. So far, that's the only solution I'm able to come up with.
Thanks for the great tool and support, ckolivas.
Unusual error this time
cgminer then locks up and becomes unresponsive.
Code:
[2013-05-14 21:58:12] Accepted 969b1ee1 Diff 1/1 GPU 0 pool 0
[2013-05-14 21:58:12] Accepted 45d1ec5e Diff 3/1 GPU 1 pool 0
[2013-05-14 21:58:32] Rejected untracked stratum share from pool 0
[2013-05-14 21:58:32] Stratum connection to pool 0 interrupted
[2013-05-14 21:58:32] Lost 3 shares due to stratum disconnect on pool 0
[2013-05-14 21:58:35] Pool 0 stratum+tcp://mint.bitminter.com:3333 not respondi
ng!
[2013-05-14 21:58:35] Switching to pool 1 http://eu-stratum.btcguild.com:3333
[2013-05-14 21:58:44] Accepted 8278ebf9 Diff 1/1 GPU 1 pool 1
[2013-05-14 21:58:45] Accepted 8c0d0cde Diff 1/1 GPU 0 pool 1
[2013-05-14 21:58:46] Accepted 696623af Diff 2/1 GPU 1 pool 1
[2013-05-14 21:58:47] Accepted 66f2639c Diff 2/1 GPU 1 pool 1
[2013-05-14 21:58:54] Accepted 5157abb5 Diff 3/1 GPU 0 pool 1
[2013-05-14 21:58:58] Accepted ac0c27bd Diff 1/1 GPU 0 pool 1
[2013-05-14 21:59:00] Accepted 720c6ced Diff 2/1 GPU 0 pool 1
[2013-05-14 21:59:04] Accepted 47585654 Diff 3/1 GPU 1 pool 1
[2013-05-14 21:59:11] Accepted 234186c8 Diff 7/1 GPU 0 pool 1
[2013-05-14 21:59:19] Accepted a6247f67 Diff 1/1 GPU 1 pool 1
[2013-05-14 21:59:19] Accepted c7b6a451 Diff 1/1 GPU 0 pool 1
[2013-05-14 21:59:23] Accepted af94570d Diff 1/1 GPU 0 pool 1
[2013-05-14 21:59:23] Accepted f210e859 Diff 1/1 GPU 1 pool 1
[2013-05-14 21:59:27] Accepted 51ebafe3 Diff 3/1 GPU 0 pool 1
[2013-05-14 21:59:27] Accepted 2f90b4f6 Diff 5/1 GPU 1 pool 1
[2013-05-14 21:59:28] Accepted b97cdd01 Diff 1/1 GPU 1 pool 1
[2013-05-14 21:59:32] Pool 0 stratum+tcp://mint.bitminter.com:3333 alive
[2013-05-14 21:59:32] Switching to pool 0 stratum+tcp://mint.bitminter.com:3333
[2013-05-14 21:59:35] Accepted e164766a Diff 1/1 GPU 0 pool 1
[2013-05-14 21:59:37] pool 0 JSON stratum auth failed: [
24,
"Unauthorized",
null
]
cgminer then locks up and becomes unresponsive.
All OK, except I had round-robin set, and I would have expected cgminer to roll back to the primary pool at some time? Perhaps round robin is only for the failover pools and does not include the primary pool?
ROUND ROBIN:
This strategy only moves from one pool to the next when the current one falls
idle and makes no attempt to move otherwise.
I too watched cgminer rollover to my 50btc backup when bitminter went down. (urls removed)
All OK, except I had round-robin set, and I would have expected cgminer to roll back to the primary pool at some time? Perhaps round robin is only for the failover pools and does not include the primary pool?
Unfortunately, one card went 'sick', with cgminer throwing "Error -6", and continued to log this repeatedly every minute for 15 minutes until I restarted. I don't know if it's the card, or the error is code related. I restarted cgminer and the sick card sprang right into action. I include it here in case ckolivas might find it useful.
Thanks
Code:
[2013-05-14 04:55:51] Accepted d995938b Diff 1/1 GPU 1 pool 0
[2013-05-14 04:57:23] Stratum connection to pool 0 interrupted
[2013-05-14 04:57:23] Lost 33 shares due to stratum disconnect on pool 0
[2013-05-14 04:58:23] Pool 0 stratum+tcp://{bitminterurl} not responding!
[2013-05-14 04:58:23] Switching to pool 1 stratum+tcp://{50btcurl}
[2013-05-14 04:58:38] Accepted c2f6966a Diff 1/1 GPU 1 pool 1
All OK, except I had round-robin set, and I would have expected cgminer to roll back to the primary pool at some time? Perhaps round robin is only for the failover pools and does not include the primary pool?
Unfortunately, one card went 'sick', with cgminer throwing "Error -6", and continued to log this repeatedly every minute for 15 minutes until I restarted. I don't know if it's the card, or the error is code related. I restarted cgminer and the sick card sprang right into action. I include it here in case ckolivas might find it useful.
Code:
[2013-05-14 06:23:30] Accepted 2000c7dc Diff 7/1 GPU 1 pool 1
[2013-05-14 06:23:40] GPU0: Idle for more than 60 seconds, declaring SICK!
[2013-05-14 06:23:40] GPU0: Attempting to restart
[2013-05-14 06:23:40] Thread 0 still exists, killing it off
[2013-05-14 06:23:40] Thread 1 still exists, killing it off
[2013-05-14 06:23:40] Error -6: Creating Command Queue. (clCreateCommandQueue)
[2013-05-14 06:23:40] Failed to reinit GPU thread 0
Thanks
Try the newer release, and try disabling hotplug if your keyboard is having issues too (--hotplug 0)
Thanks, been running the latest release since it was posted and it seems to be coping much better with stratum disruption. I've seen things fail over from Bitminter to BTCGuild and back again. Previous releases just hung.Oh, dear - definite improvement but still not quite stable. Bitminter's just gone down and this time cgminer didn't make it over to BTCguild in one piece.
Code:
Rejected untracked stratum share from pool 0
Stratum connection to pool 0 interrupted
Lost 3 shares due to stratum disconnect on pool 0
Pool 0 stratum+tcp://mint.bitminter.com:3333 not responding!
Switching to pool 1 http://eu-stratum.btcguild.com:3333
BTC guild shows cgminer as submitting one successful share, then submits every 9-10seconds which are classified Reject (other). Cgminer's UI has hung at this point and GPUs have cooled down, fans reduced.
The UI which has hung still says connected to mint.bitminter runnning at full tilt, which it's clearly not.
Code:
Edit: rather worryingly when restarting cgminer I discovered the GPU's weren't cool at all!
- it was just the fans that had throttled back.
On startup one of my GPUs was running 6 degrees over its target temperature.
On restarting it failed over to btcguild correctly as bitminter was still down or being DoS'd.
Shortly after reconnected back over to Bitminter when it detected a stratum connection.
FYI: CK's wallets (both BTC and LTC) are in the readme's of his cgminer packages. Scrypt readme for LTC, readme for BTC.
I had some initial issues with the 3.1.1 as recommended, but am diagnosing personal network issues. I'll report back in a couple days, too.
I had some initial issues with the 3.1.1 as recommended, but am diagnosing personal network issues. I'll report back in a couple days, too.
Will do. Posting report after a day or two testing
>24 hrs, works like charm
great work m8.Will send some LTC your way. Keep up the good work
EDIT: ckolivas post LTC Adress please
Try the newer release, and try disabling hotplug if your keyboard is having issues too (--hotplug 0)
Thanks, been running the latest release since it was posted and it seems to be coping much better with stratum disruption. I've seen things fail over from Bitminter to BTCGuild and back again. Previous releases just hung.Try the newer release, and try disabling hotplug if your keyboard is having issues too (--hotplug 0)
Thanks, been running the latest release since it was posted and it seems to be coping much better with stratum disruption. I've seen things fail over from Bitminter to BTCGuild and back again. Previous releases just hung.Did get a windows bluescreen earlier today, but I'll see how that goes it's quite possibly nothing to do with cgminer.
Thanks again ckolivas!
Will do. Posting report after a day or two testing
Try the newer release, and try disabling hotplug if your keyboard is having issues too (--hotplug 0)
I'm still struggling with "Stratum interrupted" issue. On windows, using CGMINER 3.1, I've updated the network card drivers to the latest, rewired all network connections, and have tried using a local stratum proxy. My windows machines still fail at different times, throwing one "stratum interrupted" line in the log, and then cgminer does nothing. I've seen others with multiple "stratum interrupted" lines in their logs, but mine throws one then seems to freeze. CGMINER does not accept keyboard commands at this point.
In contrast, my linux rig, which is hooked up to the same network, manages to keep connected.
Is there a cgminer parameter I can try to make it reconnect? Or at least make it's failover configuration work? I believe I have the failover config correct, but it doesn't trigger with "stratum interrupted". I might try going back to an older version of cgminer.
Thanks
In contrast, my linux rig, which is hooked up to the same network, manages to keep connected.
Is there a cgminer parameter I can try to make it reconnect? Or at least make it's failover configuration work? I believe I have the failover config correct, but it doesn't trigger with "stratum interrupted". I might try going back to an older version of cgminer.
Thanks
What I have noticed. Before I run cgminer all Internet connections are good can surf web etc.
Soon as I start cgminer few seconds after boot it receives a work order from pool. Cgminer starts to work it and THAT'S the point where all my Internet connection is disabled. (Can't even load a web page even though my Internet network is perfectly connected still) (all other computers on same wifi can still surf web no problems)
Once cgminer finishes work it CANNOT send it back to pool (due to no Internet connection) then cgminer gives message
Stratum connection to pool 0 Interrupted
Lost 1 share due to stratum disconnect on pool 0
Then I think cgminer auto restarts and that's the point where Internet is restored and therefore it retrieves a new work order from pool and once it starts working on it bam same thing and over and over and over..
I don't know what to do. It's not the pool (I have tried many)
Any suggestions . ? Running latest cgminer with 12.8 drivers for vid card
Soon as I start cgminer few seconds after boot it receives a work order from pool. Cgminer starts to work it and THAT'S the point where all my Internet connection is disabled. (Can't even load a web page even though my Internet network is perfectly connected still) (all other computers on same wifi can still surf web no problems)
Once cgminer finishes work it CANNOT send it back to pool (due to no Internet connection) then cgminer gives message
Stratum connection to pool 0 Interrupted
Lost 1 share due to stratum disconnect on pool 0
Then I think cgminer auto restarts and that's the point where Internet is restored and therefore it retrieves a new work order from pool and once it starts working on it bam same thing and over and over and over..
I don't know what to do. It's not the pool (I have tried many)
Any suggestions . ? Running latest cgminer with 12.8 drivers for vid card
Im using Guiminer (tried cgminer same thing happens) My internet works fine BUT as SOON as I start to try and mine it litterally cuts my internet connection off. Cant load a webpage, nada. I see Guiminer hashing away but no shares get accepted , no stales nada (no communication with pool I suppose since internet cuts)
Still searching for answer with this problem (I cant mine) no answers although.
I updated everything too and it has worked before and now all the sudden this . So Im at a loss as to the cause
Still searching for answer with this problem (I cant mine) no answers although.
I updated everything too and it has worked before and now all the sudden this . So Im at a loss as to the cause
I'm on LTC now, same thing happening, so it's not pool related as I can see...
I was mining primarily on Slush when mine kept disconnecting, not sure if that had something to do with it or not.
Happening to me too! Ringing 7850 card. Soon as I start to mine my Internet connection goes bad . Can't even surf web
Possibly, still no resolution here
Ran stable for 36hrs before locking up this time.
Haven't gotten around to setting up a local stratum proxy yet, but have switched pools to BTC guild temporarily to see if that's any more stable.
Ran stable for 36hrs before locking up this time.
Haven't gotten around to setting up a local stratum proxy yet, but have switched pools to BTC guild temporarily to see if that's any more stable.
So did anyone found solution for this issue? I see that most of us are on Bitminter and using multiple 7970 cards?
Could this be 7970 specific problem?
Could this be 7970 specific problem?
Same issue here.
2x 7970 cgminer get stuck when connection is lost...
2x 7970 cgminer get stuck when connection is lost...
I'm getting this, too. Running 3.1 on windows, and 3.0 on linux. Of three rigs, 1 windows and 1 linux both went "pool 0 interrupted" and ceased mining. The third rig kept on mining. Neither of the two that "interrupted" failed over.
I'll try setting up a local stratum proxy, but I'm not convinced it will help.
Thanks CK, cgminer is a terrific tool. The new release is packed with updates!
I'll try setting up a local stratum proxy, but I'm not convinced it will help.
Thanks CK, cgminer is a terrific tool. The new release is packed with updates!
Exact same problem here. Win 7 x64 Was on cgminer 2.11.4, just tried 3.1.0.
Mining with x2 7970s - CG miner seems to lockup, doesn't hash and won't take keyboard input. Always reports a stratum connection interrupted before going down.
Had this problem a few times earlier this month. Then has been stable for 14 days or so. Now last couple of days its 4-5 hours max, then it hangs.
Mining at Bitminter pool with a failover pool set to BTCGuild. It never fails over, it hangs before. after saying stratum interrupted and then lost shares. A restart of cgminer restores everything working again (till next time).
I suspect the problem trigger is instability in the stratum connection as it has happened each time Bitminter restart or goes down. I'm contemplating setting up a local stratum proxy to try to circumvent the problem until this is fixed.
Mining with x2 7970s - CG miner seems to lockup, doesn't hash and won't take keyboard input. Always reports a stratum connection interrupted before going down.
Had this problem a few times earlier this month. Then has been stable for 14 days or so. Now last couple of days its 4-5 hours max, then it hangs.
Mining at Bitminter pool with a failover pool set to BTCGuild. It never fails over, it hangs before. after saying stratum interrupted and then lost shares. A restart of cgminer restores everything working again (till next time).
I suspect the problem trigger is instability in the stratum connection as it has happened each time Bitminter restart or goes down. I'm contemplating setting up a local stratum proxy to try to circumvent the problem until this is fixed.
Got hit again by this pool disconnection message. Hashing has stopped and my pool info confirms this. I mine from a remote location, so this is really painful. It has happened now on three out of the four machines that I mine on.
I don't think it's a network card issue. I'd switched to BitMinter for a while and was using their java app, and didn't have any connection problems at all during that time.
I'm in a Win 7 x64 environment with the latest version of cgminer if that helps.
I don't think it's a network card issue. I'd switched to BitMinter for a while and was using their java app, and didn't have any connection problems at all during that time.
I'm in a Win 7 x64 environment with the latest version of cgminer if that helps.
I suppose that could be it. The problem is its consistently losing connection on only this machine, with these newer versions of cgminer. No other miners connected to the same pool have the issue, so its hard to see how its a pool specific issue. The pool is still up according to every other miner connected. Also when this error occurs, the failover never takes over either ( in cgminer.conf)....
Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
How often are you talking about? If it's still hashing away, then it HAS reconnected. That message doesn't mean it has lost the connection forever. However if no shares are being returned at that stage, that's because cgminer only reports the response from the pool, not when you actually send them, so my guess is there's some lossiness in your connection. Ironically new cgminer versions do it "the right way" and expose problems that older versions pretended never happened. I had one user who tracked a somewhat related issue to a bad network card/connection and upgrading the driver fixed it.Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
Network card might be a place to check, I'll see if I can find some updated drivers. I'm on the same network as my other miners so the outbound/inbound connectivity is good (35mbit/10mbit). But to answer your question, no it never reconnects and fails to continue hashing, and the pools show that as well.
When I received this message, the miner had stopped and was no longer hashing. However, after updating to the newer version and making sure I have a failover pool specified, I haven't had any more problems (knock on wood).
Thanks for all of your work on cgminer ckolivas.
Thanks for all of your work on cgminer ckolivas.
I suppose that could be it. The problem is its consistently losing connection on only this machine, with these newer versions of cgminer. No other miners connected to the same pool have the issue, so its hard to see how its a pool specific issue. The pool is still up according to every other miner connected. Also when this error occurs, the failover never takes over either ( in cgminer.conf)....
Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
How often are you talking about? If it's still hashing away, then it HAS reconnected. That message doesn't mean it has lost the connection forever. However if no shares are being returned at that stage, that's because cgminer only reports the response from the pool, not when you actually send them, so my guess is there's some lossiness in your connection. Ironically new cgminer versions do it "the right way" and expose problems that older versions pretended never happened. I had one user who tracked a somewhat related issue to a bad network card/connection and upgrading the driver fixed it. Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
I suppose that could be it. The problem is its consistently losing connection on only this machine, with these newer versions of cgminer. No other miners connected to the same pool have the issue, so its hard to see how its a pool specific issue. The pool is still up according to every other miner connected. Also when this error occurs, the failover never takes over either ( in cgminer.conf)....
Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
Oh and to clarify, its not reconnecting which is the issue, both the miner and the pool show there are no more shares being submitted. It could very well be coinotron, its just strange its only happening on this one new miner. And not trying to failover at least when it does happen...
You know it's the pool dropping out, right? It also reconnects straight away so unless it's happening often and you see the message about shares being lost due to disconnect, it's not hurting. The newer versions just were more reliable in setting up connections (in windows, as linux didn't have the issue that was improved in 3.0.1).
Ran 3.01 last night, unfortunately still had the same issue. after about 5 hours. I'm gonna try reverting back to 2.11.0, my miners that still use that version haven't had the issue...
Thanks for the reminder to update to the latest, I was using 2.11.4.
Didn't know 3.0+ was out CK, will give it a go!
Try cgminer 3.0.1+
Seen this a bunch lately on 2.11.4.... its very strange behavior, haven't found a fix yet....
Did you check with your pool op? Were your failover pools/servers online?
It would help to know what version
I had a couple of my cgminers go offline with the message "stratum connection to pool 0 interrupted", a third however, which was mining on the same pool did not disconnect and kept running fine. I noticed it an hour later...
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
I have a failover set up on another pool, but for some reason that did not kick in on either machine.
Has anyone had this issue come up and have you found any solutions? I thought having a failover set up would have prevented my miners frm shutting down...
Thanks for any advice anyone can offer.
Jump to: