BI after an unexpected power outage... stuck at 100% CPU

1

105437

BIT Beta Team
Jun 8, 2015
2,160
1,052
When the power goes out unexpectedly, I have issues with BI when the power comes back on and the PC starts up. Once the PC is up, BI Tools launches and then "sees" that BI is not running so it launches BI. Once BI comes up, CPU is pegged at 100% and the Status Bar shows the Alert, Red X and Database Rebuild icon. I'm not sure how to proceed next.
 
I suggest:

1) Buy and install a UPS on your BI server after step #10.
2) Disable BIT on startup so it won't start BI.
3) Close BIT
4) Close BI
5) Go to BI's "db" folder and delete the entire folder.
6) Launch BI, it should rebuild the "db" folder.
7) If BI CPU % is back to norm, re-config BIT as it was before to open BI
8) Close BIT
9) Close BI
10) Restart BI server....how is it now?
 
TonyR said:
I suggest:

1) Buy and install a UPS on your BI server after step #10.
2) Disable BIT on startup so it won't start BI.
3) Close BIT
4) Close BI
5) Go to BI's "db" folder and delete the entire folder.
6) Launch BI, it should rebuild the "db" folder.
7) If BI CPU % is back to norm, re-config BIT as it was before to open BI
8) Close BIT
9) Close BI
10) Restart BI server....how is it now?
Click to expand...
So what is a typical size for clips.dat with 25 4 or 5 mega pixel cameras averaging 10 FPS and all running H264 or H265? I'm currently at 30G which doesn't seem excessive to me.
Thanks!
 
Teeauu said:
So what is a typical size for clips.dat with 25 4 or 5 mega pixel cameras averaging 10 FPS and all running H264 or H265? I'm currently at 30G which doesn't seem excessive to me.
Thanks!
Click to expand...
Mine is currently 1.2GB... 9 2MP cameras running 15 FPS, H264.
 
TonyR said:
I suggest:

1) Buy and install a UPS on your BI server after step #10.
2) Disable BIT on startup so it won't start BI.
3) Close BIT
4) Close BI
5) Go to BI's "db" folder and delete the entire folder.
6) Launch BI, it should rebuild the "db" folder.
7) If BI CPU % is back to norm, re-config BIT as it was before to open BI
8) Close BIT
9) Close BI
10) Restart BI server....how is it now?
Click to expand...

Thanks for the reply. Next time I'll try steps 5 and 6. The rebuild finally finished last night and things returned to normal.
 
105437 said:
Mine is currently 1.2GB... 9 2MP cameras running 15 FPS, H264.
Click to expand...
I deleted my db folder, rebooted and let it rebuild which took about 18 hours. But I now have 1.53 GB folder, so thank you all.
 
Teeauu said:
I deleted my db folder, rebooted and let it rebuild which took about 18 hours. But I now have 1.53 GB folder, so thank you all.
Click to expand...
That is a very long to to rebuild. When the database is rebuilding there is not recording happening. You must hundreds of thousands of small files and/or the db folder is on a patter drive rather than a fast ssd.
 
fenderman said:
That is a very long to to rebuild. When the database is rebuilding there is not recording happening. You must hundreds of thousands of small files and/or the db folder is on a patter drive rather than a fast ssd.
Click to expand...
No, actually the c:\blueiris folder is on an Evo 860, after 24 hours it moves to slower drives.
 
3746 in c:\blueiris\new, 2 to 11meg each. 1825 500kish files in c:\blueiris\alerts
Creating a new file for every trigger.
 
New folder should not be on the SSD, it should go to another spinning harddrive that is a surveillance rated drive.
Use combine cut to make bigger files. Set it such as 1hr, 4mb size.
No need to use the "alerts" folder, set it to 0 allocation and turn off save as high resolution jpgs.
 
  • Like
Reactions: Teeauu
looney2ns said:
New folder should not be on the SSD, it should go to another spinning harddrive that is a surveillance rated drive.
Use combine cut to make bigger files. Set it such as 1hr, 4mb size.
No need to use the "alerts" folder, set it to 0 allocation and turn off save as high resolution jpgs.
Click to expand...
Thank you for the advice.
 
  • Like
Reactions: looney2ns
You must log in or register to reply here.
Top Bottom