Anyone seen this error before? "FORCE quitting CGadSocket thread"
- Thread starter erkme73
- Start date
it’s got nothing to do with the latest stable version. This has been happening occasionally since some change in the beginning of the year. So it’s not going to help @tech101.
looney2ns
IPCT Contributor
Takes all of 30 seconds to roll back and try what can it harm?
I and many others are not having this problem, why haven't you emailed support if you've been having that problem for such a long time.
tech101
Known around here
Just changed to latest stable build around 1:00pm California local time. After sometime erros came back up again even with stable version which was - 
I will get this over to BI Support and see if we can figure out why this is happening..
Also Now I remember I recently also made a change to most of my camera.. Which was
H A D was set to No I change it to default which should be Intel. I am gonna try to change this to NO and see if this happens again or not
I will get this over to BI Support and see if we can figure out why this is happening..
Also Now I remember I recently also made a change to most of my camera.. Which was
H A D was set to No I change it to default which should be Intel. I am gonna try to change this to NO and see if this happens again or not
Last edited:
tech101
Known around here
I think I found the solution to this issue for me. Hope it can help other. As I thought When I changed the Hardware accelerated decode from No To Default that is when I started seeing all the Socket Thread errors.
I just reverted back to No instead of default about 40 mins ago or 45 now.. And No more errors.. Once I changed the setting back from Default to NO
Which I mentioned above..
I will email Ken in regards to this and let him know. Thank you!
I just reverted back to No instead of default about 40 mins ago or 45 now.. And No more errors.. Once I changed the setting back from Default to NO
Which I mentioned above..
I will email Ken in regards to this and let him know. Thank you!
Last edited:
Turning off hardware acceleration to fix this isn’t really a solution, it’s a pretty essential part of Blue Iris and ideally should be left on. But good to know it has something to do with HA
I don't want to cause more confusion (that usually follows in my wake) so I won't link the thread here, but I ran into a large amount of problems a few months ago as I began my BI adventure. Now, understand that I had a LOT of difficulties and MOST of them I initially blamed on buying the wrong PC, wrong connections, etc. However, as I progressed through the troubleshooting and incredible frustration, ONE of the issues was a recurring "
CGadSocket thread error. Fast forward through my weeks of buying other, better hardware to try to fix the issues only to learn that it turned out to be a brand new but (intermittently) faulty WD Purple 10TB drive that was causing most of my grief. Now, understand that in the process of replacing my entire build, bit-by-bit, I've made too many changes to hardware to pinpoint causation. What IS known fact: my new drive was faulty; and was later replaced under warranty. After I switched to another new drive everything started to work and no more
CGadSocket thread errors. Could be coincidence, NOT definitive, but it's POSSIBLE you're having an intermittent storage write issue.
"
CGadSocket thread error. Fast forward through my weeks of buying other, better hardware to try to fix the issues only to learn that it turned out to be a brand new but (intermittently) faulty WD Purple 10TB drive that was causing most of my grief. Now, understand that in the process of replacing my entire build, bit-by-bit, I've made too many changes to hardware to pinpoint causation. What IS known fact: my new drive was faulty; and was later replaced under warranty. After I switched to another new drive everything started to work and no more
CGadSocket thread errors. Could be coincidence, NOT definitive, but it's POSSIBLE you're having an intermittent storage write issue.
"
tech101
Known around here
I did email blue iris support on this and waiting for their input on this. Sam from blueiris already did look into this on the screenshots I provided not certain why this was happening with HA on.. or set to defualt which is intel.
I have it No for now and no more errors or issue or any missing footage that I know off more than 24 hours... now straight after making that change no errors. I will see if we can get to bottom of the root cause of this I have multiple drives which are all new drives pretty much including Ultrastar and WD purples.. Thank you for all the input Appricieate all your help and input on this,.
I have it No for now and no more errors or issue or any missing footage that I know off more than 24 hours... now straight after making that change no errors. I will see if we can get to bottom of the root cause of this I have multiple drives which are all new drives pretty much including Ultrastar and WD purples.. Thank you for all the input Appricieate all your help and input on this,.
tech101
Known around here
I heard back from Ken with blueiris. So here is what I am gonna try .. As per Ken
I have only seen this recently as the result of a hanging hardware decoding driver. Please try turning hardware decoding OFF for the camera with this issue.
My plan is now to Turn on the Hardware accelerator to default which should be Intel for me one by one and see which camera does it come for.. and keep them off for the camera which makes the sounds like decoding driver to stop or hang.
I have only seen this recently as the result of a hanging hardware decoding driver. Please try turning hardware decoding OFF for the camera with this issue.
My plan is now to Turn on the Hardware accelerator to default which should be Intel for me one by one and see which camera does it come for.. and keep them off for the camera which makes the sounds like decoding driver to stop or hang.
I had the same issues "CGadSocket thread error". My setup (which may not be the same for you) but in my case I use a USB flash-drive to house my Aux folders (Aux 1 thru 7) to record my snapshots. I’ve been doing this for some time without an issue. However in late Dec /early Jan the CGadsocket error appeared and BI would crash. To get around/stop the Socket error I had to move the "Aux folders" to my computer C drive. I should mention that at about the same time just before the error started to appear there was a windows 10 update. I reached out to support and they gave me the similar advise that you received, but that didn't cure the problem.
Solution:
The solution that I found/stumbled on that worked for me was to change the windows USB Root Hub Setting. I found that one (I have three listed) of my USB Root Hub (USB 3.0) setting was "Checked to allow the computer to turn off this device to save power." Since I unchecked this setting, the Socket error has disappeared. I have since moved the Aux folders back to the USB drive and BI has been working error free for the past several weeks.
Hope this helps to solve your problem or anyone else that experience the same error.
(I'm sure you know how to find device setting but:
Device Manger ---> System Devices ----> Universal Serial Bus Controller -----> USB Root Hub (USB 3.0) ------ (Highlight) and right click., scrolled to Properties ,click on Power Management (uncheck power settings).
Save and reboot the computer.
UPDATE: 2/2/21
Well I thought I had a solution/cure but to my dismay last night the CGadSocket thread Error resurfaced and cause BI to stop recording. So the problem is a lot deeper than my solution / fix would suggest.
Last edited:
tech101
Known around here
Interesting. Thank you for sharing this info. For me I have not seen this error as I have some places intel hardware off. And some of them intel hardware on for some cams. I will set these power managment setting as I use USB drive for my recording as well since MY PC case is very small but I have about 8 Drive USB Bay to do this.
Last edited:
Again, not definitive, but my experience with this came back to BI not being able to write maybe even for just a moment, due to either my glitching drive OR a glitching connection. AFTER replacing the new drive with a working new drive, the problem ALMOST disappeared. Then i moved my purple drive from the SATA connected box to a USB3 connected box and I got another cgadsocket error. At that point I swapped towers so that I could put the purple into a permanent SATA bay and all of the errors stopped.
There is something about USB connections that is inherently impermanent.
There is something about USB connections that is inherently impermanent.
IAmATeaf
Known around here
My system has been trouble free for a few months but this morning the cams were all down with no recordings, checked the server and found these, which coincides with when the server stopped recording.
Code:
1 18/03/2021 09:13:45.190 Garden Signal: network retry
1 18/03/2021 09:13:45.191 Patio Signal: network retry
1 18/03/2021 09:13:45.215 Drive1 Signal: network retry
1 18/03/2021 09:13:45.252 Garage Signal: network retry
1 18/03/2021 09:13:45.261 Extension Signal: network retry
1 18/03/2021 09:13:45.276 Drive2 Signal: network retry
2 18/03/2021 09:14:06.865 Garage FORCE quitting CGadSocket thread 18 310 1551876
2 18/03/2021 09:14:06.918 Garden FORCE quitting CGadSocket thread 18 310 1551881
2 18/03/2021 09:14:06.929 Patio FORCE quitting CGadSocket thread 18 310 1551883
2 18/03/2021 09:14:07.007 Extension FORCE quitting CGadSocket thread 18 310 1551880
2 18/03/2021 09:14:07.018 Drive2 FORCE quitting CGadSocket thread 18 310 1551882
2 18/03/2021 09:14:07.044 Drive1 FORCE quitting CGadSocket thread 18 310 1551877
1 18/03/2021 09:14:15.264 Patio Signal: network retry
1 18/03/2021 09:14:15.264 Garden Signal: network retry
1 18/03/2021 09:14:15.286 Drive1 Signal: network retry
1 18/03/2021 09:14:15.320 Garage Signal: network retry
1 18/03/2021 09:14:15.332 Extension Signal: network retry
1 18/03/2021 09:14:15.350 Drive2 Signal: network retrytech101
Known around here
I was having the same issue. Switching from Intel to Intel Beta resolved it for me. Also, on my system, once that error happens (HW VA), it turns the hardware encoding off.
IAmATeaf
Known around here
Doesn’t appear to have disabled HA for me but I’m just looking on the mobile app, will have to logon to the server and check. All my cams are set to use just the normal Intel HA.
tech101
Known around here
I am going to try this Intel Beta, I know for sure on one of my PTZ if I use the sub stream it buffers while tracking. Will see if using Intel Beta resolves this thank you for that tip. I was able to get around that problem by not using sub stream for that camera. But for the Socker error I did Turn off HA so will be interesting what Intel beta does for those cams.
A quick way to see what each camera is using for HW encoder is with the camera tab in the status window of the console. I = Intel. I2 = Intel Beta. A "-" means it's off. If yours is like mine, when the error occurs, some (if not all) of the cameras will automatically turn HW to off.
tech101
Known around here
Also One of my issue is for this one cam when I use Sub Stream for some reason that camera recording specially while that ptz is tracking starts having buffering issue and I try the sub stream turned it back on and still it buffers.
What is bizzare is once I take off the sub stream no issues.
What is bizzare is once I take off the sub stream no issues.