5.7.2 - March 22, 2023 - Identifying and resolving storage errors and pitfalls

[fenderman]

5.7.2 - March 22, 2023
This update is all about identifying and resolving storage errors and pitfalls. In addition to
overallocation, additional storage issues are now identified and reported.

If a drive is offline, over allocated, or another issue is present, this information is
prominently displayed at the bottom of the clips list in a new DB status window. You may
display this window manually with a right-click menu option. However, the window may
not be dismissed until any issues are resolved.

The software tracks the aggregate MB/s being recorded to each drive. When files are
MOVED from one drive to another, this rate is also calculated. When doing continuous
recording and archiving files to a NAS, you will want to make sure the recording rate does
not exceed the rate at which may be moved.

 

[Flintstone61]

That sure sounds like an update worth having.

 

[wittaj]

That sure sounds like an update worth having.

Test it out for us and report back LOL.

But yeah it does sound like a great feature.

 

[spammenotinoz]

This update is great, it reported my Large DB size may impact performance and Slow Index Times.
Fixed my AV exclusions and Slow Index Times are resolved, so now onto the DB size.
This is great information, especially seeing the rates for each drive.

 

[wittaj]

This update is great, it reported my Large DB size may impact performance and Slow Index Times.
Fixed my AV exclusions and Slow Index Times are resolved, so now onto the DB size.
This is great information, especially seeing the rates for each drive.
View attachment 157717View attachment 157718

This will be awesome for those using USB external drives that may prove whether they can actually keep up. Some have claimed they work no problem and others have had problems. I tried it once as an experiment and after 25 minutes only sending it two 2MP camera feeds it started choking.

 

[samplenhold]

This update is great, it reported my Large DB size may impact performance and Slow Index Times.
Fixed my AV exclusions and Slow Index Times are resolved, so now onto the DB size.
This is great information, especially seeing the rates for each drive.

Does it tell you how to solve the DB size problem?

 

[Vettester]

Does it tell you how to solve the DB size problem?

Not that I seen, but I ran a database compact/repair and the error message went away.

 

[Flintstone61]

So when I first updated to 5.7.2 it showed the first pic.
Then as it processed it's maintenance task, it began showing a 19474 Millisecond ( 19 seconds) " Slow DB access" msg.
So then I right clicked the box, and chose, "Compact/Repair"
and now it's showing what I assume is a reasonable DB access time, since the red lettering has gone away.

 

[elefant_man]

Since upgrading to 5.7.2.1 my UI3 drop down menu on the left is now displaying object object. Not sure if this is related to the upgrade or if it's something else that can be resolved. I've attached a screenshot of what I mean.

 

[gwminor48]

Since upgrading to 5.7.2.1 my UI3 drop down menu on the left is now displaying object object. Not sure if this is related to the upgrade or if it's something else that can be resolved. I've attached a screenshot of what I mean.
View attachment 157936

Blue Iris UI3

Thanks. What is Pushover, and where do I get the API and the docs for it?

www.ipcamtalk.com

 

[erkme73]

Noticing the "Large DB may impact performance" warning tonight, I found this thread. I ran the compact/repair function and it did resolve the red error, but after closing and reopening the console (my BI is running as a service), the error returned:


Interestingly, the "index" time quadrupled. Not quite sure where to go from here, or whether the red error is significant.



My db drive is a 1 TB SSD (OS drive). And my clip storage is an internal spinny 18TB.

 

[wittaj]

BI can get unstable after 200,000 clips (looks like now called clips) It used to say that in the BI help file, then disappeared for awhile, and I guess now makes it way here.

You must have something set up causing a lot of clips like taking lots of hi res images or something. I used to do that and was over 200,000 but blew them out and now under 10,000 with more a little more storage than you have.

 

[Tinman]

Just for comparison here is my status. I am running 5.7.2.2 and it appears he has added a few more stats. This suggests that there is a issue of having too much storage. How long do you really need to keep clips ?

 

[Flintstone61]

Funny, I saw your post and decided to try 5.7.2.2.
Now the little window of info has disappeared.

 

[Tinman]

Funny, I saw your post and decided to try 5.7.2.2.
Now the little window of info has disappeared.

Right click on clips and select status.

 

[Flintstone61]

Ok ...So I took the 5.7.2.3 update, and it's back>

 

[Tinman]

Does anyone know or want to take a guess what these values represent? At first I thought newest/oldest clip age, but that isn't fitting my scenario.

 

[Vettester]

Does anyone know or want to take a guess what these values represent?

Not sure, but I'm not seeing an oldest value. I'm running the latest release (5.7.2.3).

 

[Flintstone61]

I'm seeing this.

 

[erkme73]

FWIW, with .2.3 I get "access to IP ADDRESS is denied". Made sure it wasn't blocking IP in webserver. No issues. I backed down to .2.2 and full functionality is restored. Something got borked with .2.3 for webserver access.

ETA: Reinstalled .2.3 and sure enough it goes back to showing this:



Happens for both LAN and WAN addresses. Guess this is what we get for bleeding edge tech.