WriteBlueAlert no no bitmap 0 - new error

E

erkme73

BIT Beta Team
Nov 9, 2014
1,570
1,486
I woke up this AM to a bunch of notifications for the subject error. I rebooted the server in hopes it might clear it up, but no luck. It seems to really only happen on one camera, though I have found it on my "a206" as well.

I'm running 5.5.1.7 (10/11/21) - so I assume this is a result of the latest update. I've sent an email to Ken, and will probably just roll back for now.



Line 422252: 2 10/12/2021 6:22:00.612 AM a206 WriteBlueAlert no bitmap 0
Line 422606: 2 10/12/2021 6:40:03.241 AM a118 WriteBlueAlert no bitmap 0
Line 422637: 2 10/12/2021 6:40:58.119 AM a118 WriteBlueAlert no bitmap 0
Line 422665: 2 10/12/2021 6:41:58.422 AM a118 WriteBlueAlert no bitmap 0
Line 422683: 2 10/12/2021 6:42:58.834 AM a118 WriteBlueAlert no bitmap 0
Line 422711: 2 10/12/2021 6:44:00.772 AM a118 WriteBlueAlert no bitmap 0
Line 422722: 2 10/12/2021 6:45:01.832 AM a118 WriteBlueAlert no bitmap 0
Line 422733: 2 10/12/2021 6:45:44.093 AM a118 WriteBlueAlert no bitmap 0
Line 422759: 2 10/12/2021 6:46:51.134 AM a118 WriteBlueAlert no bitmap 0
Line 422781: 2 10/12/2021 6:47:52.211 AM a118 WriteBlueAlert no bitmap 0
Line 422805: 2 10/12/2021 6:48:52.633 AM a118 WriteBlueAlert no bitmap 0


Anyone else seeing this?

ETA - just downgraded to 5.5.1.6. So far no such error. Will update here as I learn more.
 
  • Like
Reactions: TonyR
I updated to .7 last night and had a disaster. It kept spiking the CPU and memory resulting in the service crashing about every two minutes. I managed to get into the console, finally, and am back at 5.4.9.18 now. I'll take it back up to 5.5.1.6 later today. There is something wrong with .7 from my perspective.
 
Last edited:
  • Like
Reactions: TonyR, erkme73 and looney2ns
I got a response back from support:

This could be an indication you are using dual streams, get you have no pre-trigger buffer, or your key frame rate is too low.

I have worked-around this for 5.5.1.8 however.
Click to expand...
 
  • Like
Reactions: sebastiantombs
I just updated to .8 and it went fine. Whatever the problem(s) were with .7 seem to be corrected. That would explain the fast turnaround from .7 to .8 Stuff happens.
 
I'm getting this error very sporadic as well...running 5.5.1.13 I don't use substreams and no pre-triggers on the cams getting errors. My I-frames have always been the same as before. This error came with the 5.5.1.x updates.

Screenshot 2021-10-19 101121.jpg
 
  • Like
Reactions: erkme73
Tinman said:
I'm getting this error very sporadic as well...running 5.5.1.13 I don't use substreams and no pre-triggers on the cams getting errors. My I-frames have always been the same as before. This error came with the 5.5.1.x updates.

View attachment 105487
Click to expand...
Interesting. My problems have not returned since the latest updates. I wonder if there's something unique about your hardware. Have you tried sending an email to support?
 
erkme73 said:
Interesting. My problems have not returned since the latest updates. I wonder if there's something unique about your hardware. Have you tried sending an email to support?
Click to expand...

Not yet....still trying to see if I can reproduce error, but will if I can pin it down. This seems to only apply to 3 cams that I have triggered by a external device which executes a .bat file to trigger the 3 cams. But I can run the .bat file and have for years with no errors ?? It at least does not crash system, but is annoying as it shows up as a critical error. These cams also run in their own profile 2 and only then do I get this error. I'll try to explain, I have 3 cams within my shop that do not record during shop open hours (profile 2) I have them set with no motion detection so I don't get recordings of me all day. But I do have a door switch that will trigger the 3 cams every time someone enters or leaves and then they do a 60 sec recording. During closed hours they go to profile 1 which then they use normal motion detection. ALL of my other cams are continuous recording and do not produce this error.
 
My errors came off of two cameras every few minutes. While I do have some externally triggered cams, neither of the two problematic cameras have them.
 
  • Like
Reactions: Tinman
erkme73 said:
My errors came off of two cameras every few minutes. While I do have some externally triggered cams, neither of the two problematic cameras have them.
Click to expand...
I went ahead and sent support the same info I posted. I agree, doesn't seem to be related to external triggers. It can go for hours and then just pop up :)
 
I am also getting the same error , on 5.5.1.15, it appears on different cameras but mostly when more than 2 (or 3) cameras triggered at the same time.
It also looks like when this happens alert is not saved to alert window, and no mark on timeline is created.
 
Mine have gone away since 5.5.1.16 and now running 5.5.1.18 and no errors. But I did go into all of my cameras reporting that error and double checked my settings. I did have the box checked for "pre-trigger video buffer" and then 0.0 sec. as I use to use those and had just changed the value to 0.0 but forgot to uncheck box. NOT sure if that has anything to do with it, but so far no more errors. Also my error was happening only during Profile 2 was active, so you need to check settings according to that time.
 
You must log in or register to reply here.
Top Bottom