My BI won't run... Process is "suspended"

[erkme73]

Update: The problem was with my clip storage drive. It WAS completely full and I missed it. Once I made room, BI sprang back to life. Operator error.
------
Over the last week or so I've started getting "restart after unexpected shutdown" crashes several times per day. It's been getting progressively worse.

Today, I noticed that I couldn't log in via UI3. VNCing into the machine (no monitor on the BI PC) I see this:



BIT things the program is running:



My normal CPU is about 60-80%. Webserver is unavailable and BIT is unable to restart the process/service.

Under services, if I try to stop BI service it INSTANTLY goes from running to stopped. Likewise, starting it INSTANTLY goes from stopped to running. In the past, it would spend at least 5-10 seconds "stopping" or "starting". Something is hung.

Unfortunately, restarting the system does nothing. It comes up immediately with the multiple copies of the process showing suspended.

No clue what my next step should be

 

[SouthernYankee]

Is this a clean widows 10 install from Microsoft media creation tool ?
Are your running a virus scanner and have you disabled it on all BI folders?
What version of BI are your running ?
What information is in the BlueIris log file ?
What information is in the Windows event file.
Have you done a power down shutdown followed by boot of the computer, Not a restart,

 

[erkme73]

Is this a clean widows 10 install from Microsoft media creation tool ?
Are your running a virus scanner and have you disabled it on all BI folders?
What version of BI are your running ?
What information is in the BlueIris log file ?
What information is in the Windows event file.
Have you done a power down shutdown followed by boot of the computer, Not a restart,

This was a stock win10 system from Acer. At some point, I wiped it and installed bare bones win10 to de-bloat it, but that was years ago.
No virus scanner other than Windows Defender which I tried my best to neuter, but it still going.
Bi is the most recent version - I just updated it manually last night.
Windows event file - you'd have to let me know what you think would be most helpful from the logs - there's a ton of categories.
BI log file shows normal activity up until about an hour ago - at which point:

3 2/6/2020 12:49:16 PM a207 MOTION
3 2/6/2020 12:49:28 PM a222 MOTION
3 2/6/2020 12:49:38 PM a223 MOTION
3 2/6/2020 12:49:38 PM a227 MOTION
2 2/6/2020 12:49:49 PM a210 Clip: Disk full
2 2/6/2020 12:49:49 PM a222 Clip: Disk full
2 2/6/2020 12:49:50 PM a208 Clip: Disk full
2 2/6/2020 12:49:50 PM a223 Clip: Disk full
2 2/6/2020 12:49:52 PM PTZ-TL Clip: write error 8000003a, undefined
2 2/6/2020 12:49:52 PM a207 Clip: Disk full
2 2/6/2020 12:49:53 PM PTZ-NW Clip: Disk full
2 2/6/2020 12:49:55 PM a227 Clip: Disk full
3 2/6/2020 12:49:56 PM Dahua MOTION
3 2/6/2020 12:49:56 PM a209 MOTION
2 2/6/2020 12:50:00 PM a210 Clip: Disk full
2 2/6/2020 12:50:01 PM Dahua Clip: Disk full
2 2/6/2020 12:50:02 PM PTZ-TL Clip: Disk full
2 2/6/2020 12:50:04 PM a209 Clip: Disk full
2 2/6/2020 12:50:06 PM a227 Clip: Disk full
2 2/6/2020 12:50:07 PM PTZ-NW Clip: Disk full
3 2/6/2020 12:50:08 PM a222 MO


Which is interesting, since the drive it writes to is accessible and has capacity. I cannot change/verify it in BI since I cannot get the console to open.

I did not do a full power shut down - just a restart, but I will do that now.

 

[erkme73]

...Have you done a power down shutdown followed by boot of the computer, Not a restart,

WOW! You nailed it! I power cycled it - true shut down - and when it came up it was happy as a lark. Who'da thunk it. Super grateful. Thanks!

 

[erkme73]

WOW! You nailed it! I power cycled it - true shut down - and when it came up it was happy as a lark. Who'da thunk it. Super grateful. Thanks!

I jinkxed it. I assumed it was working since BIT showed server green. But alas, still no go. I've started a dialog with Ken and we're exchanging emails right now. If/when I get this resolved I'll post the solution.

 

[SouthernYankee]

If you can get it up Need a screen shot of
1) Blue iris status clip storage

If still up ... then screen shots of
2) Blue iris settings clips and archiving tab , for the NEW folder, stored folder, alerts folder. (three screen shots)
3) Blue Isis status Cameras
3) on two of the camera properties the record tab.

Describe the hardware on the BI PC
CPU
Memory
Disks.

 

[erkme73]

If you can get it up Need a screen shot of
1) Blue iris status clip storage

If still up ... then screen shots of
2) Blue iris settings clips and archiving tab , for the NEW folder, stored folder, alerts folder. (three screen shots)
3) Blue Isis status Cameras
3) on two of the camera properties the record tab.

Describe the hardware on the BI PC
CPU
Memory
Disks.

Those opportunities are gone. BI will not start at all so I cannot get to any of the options/stat pages. Ken is using Teamviewer, but suspects there is something wrong with my OS. It has been hokey for quite some time (well before the BI5 update)... I may just bite the bullet this weekend and wipe it clean and start over. I just hope whatever funk is screwing with the operation of BI doesn't hitch a ride with the registry export/backup of BI. I DO NOT want to rebuild BI. That would take FOREVER.

PC is i7-4970, 16GB ram, 256GB SSD for OS/BI DB, and 6TB internal drive for clip storage, as well as a 8TB NAS for backup/alternate clip storage.

 

[bp2008]

Do you have any older backups of your BI configuration, like from 2 weeks ago when it was known to be good? (BI Update Helper creates these automatically)

If so, you could try restoring that. Maybe delete the Perspective Software folder from the registry under HKLM/Software/ first.

 

[erkme73]

Do you have any older backups of your BI configuration, like from 2 weeks ago when it was known to be good? (BI Update Helper creates these automatically)

If so, you could try restoring that. Maybe delete the Perspective Software folder from the registry under HKLM/Software/ first.

I do, actually. But I think I've convinced myself to start with a clean slate on the PC. I'm pretty sure Ken is right that it is unrelated to the BI program. For example, any time I've had to stop the BI service, the PC all but locks up for about 5 min. It eventually returns, but clearly there's some bigger underlying issue. I was hoping that my original post would illicit a bunch of "me too" replies - but if this is really just my system, I think the writing is on the wall.

 

[SouthernYankee]

A complete rebuild is a great idea.

Any idea why you were getting a disk full error.


General storage notes.
1) Do not use time to determine when BI video files are moved or deleted, only use space.
2) If New and stored are on the same disk drive do not used stored, set the size to zero, set the new folder to delete. All it does is waste CPU time and increase the number of disk writes. You can leave the stored folder on the drive just do not use it.
3) never allocate over 95% of the total disk drive to BI.
4) Do not use the C: drive if it is an SSD for video storage.

 

[erkme73]

Great idea, but so not looking forward to it.

Ken clicked around for a bit but ultimately had other engagements. He felt strongly that it wasn't BI. I told him that my intention is to rebuild the PC and start over.

In the process of starting to move things off of the OS drive that I want to backup for the upcoming drive format, I ran into that "disk is full" error. I was certain I checked the destination drive and saw capacity, but apparently, there wasn't.

The problem arose from me having two volumes on the drive - one dedicated for the new clips from BI, the other a quasi file backup. The delete threshold I'd set for BI was initially appropriate, but as the second partition began to grow, it encroached into the drive's overall capacity - making it less than the delete threshold in BI settings. As such, the drive reached capacity and BI didn't know it. That locked it up tight as a drum.

As soon as I cleared off old videos, BI woke up and played nice. I've now added a dedicated 6T drive that will be used exclusively for BI. Doh... As usual, it's a self-inflicted problem.