A few days ago I woke up to a custom Pushover notification from my new Powershell script BI_logfile_wdog.ps1 ***.
I tried opening the Blue Iris Android app, and it could not connect (unresponsive webserver).
After rebooting my Blue Iris server, I inspected the Blue Iris logfile and found the entries mentioned in the notification.
This was the very first one (of 394!):
This being the first time I had ever observed this entry, I searched the forum for info.
While I could find the error mentioned in old posts, none provided an explanation. So I emailed Ken.
I'm posting Ken's reply so others might find it on searching.
So far, I've not had a recurrence. Further investigation showed the error was accompanied by a major memory leak.
*** Here's a screenshot of the custom Pushover notification:
Here's a screenshot of the accompanying memory leak:
I remotely rebooted the server at 3:44a (using my MSNSwitch)
I tried opening the Blue Iris Android app, and it could not connect (unresponsive webserver).
After rebooting my Blue Iris server, I inspected the Blue Iris logfile and found the entries mentioned in the notification.
This was the very first one (of 394!):
2,10/25/2024 11:00:20.174 PM,App,live.sem stuck
This being the first time I had ever observed this entry, I searched the forum for info.
While I could find the error mentioned in old posts, none provided an explanation. So I emailed Ken.
I'm posting Ken's reply so others might find it on searching.
First, this is a bad sign ... something in the frame pipeline is stuck and this will eventually cause system instability.
I have seen this with come hardware decoding incompatibility ... maybe try fewer/no cameras through hardware decoding as an initial test.
This is also a good time to double check all security software exemptions for the BlueIris.exe.
So far, I've not had a recurrence. Further investigation showed the error was accompanied by a major memory leak.
*** Here's a screenshot of the custom Pushover notification:
Here's a screenshot of the accompanying memory leak:
I remotely rebooted the server at 3:44a (using my MSNSwitch)
Last edited: