BenthamFoucault
n3wb
Hi,
I'm running Blue Iris as a service on a computer which is turned on at a slightly unpredictable time of day each day. In our use case, we're using Blue Iris to interactively monitor camera feeds from the internals of a machine; it's not a surveillance system. When the cameras are needed the system is turned on, and when we aren't using them, the whole system is turned off. So I can't schedule a particular time of day when the Blue Iris server will always be turned on but the cameras will not be in use. While Blue Iris is running we do continuous recording.
We've been having issues with frequent corruption of the Blue Iris DB, which results in Blue Iris overflowing its allocated recording storage space, because it loses track of files that were already written to disk but where the corresponding DB records haven't been flushed to disk. I think the root cause of the DB corruption is that the PC sometimes is turned off by just cutting power rather than being properly shut down. Obviously that's bad for more reasons than Blue Iris alone, and I'm working on improving that situation, but right now it's not easy for me to guarantee that it always gets a proper shutdown. I accept that it's not reasonable to expect Blue Iris to avoid DB corruption under these circumstances; I don't think there's a Blue Iris bug.
But, regardless, because we're encountering DB corruption more often than we'd like, we want Blue Iris to do a database repair every time the service starts up. We would prefer to add a few minutes of startup delay to the system, rather than have to schedule the repair at a time of day where we would otherwise want uninterrupted operation & recording.
Is there a way to do this? E.g. via settings or scriptable command line instructions, or an API? I currently have 5.7.5.6 installed, but can upgrade if it will help.
I'm running Blue Iris as a service on a computer which is turned on at a slightly unpredictable time of day each day. In our use case, we're using Blue Iris to interactively monitor camera feeds from the internals of a machine; it's not a surveillance system. When the cameras are needed the system is turned on, and when we aren't using them, the whole system is turned off. So I can't schedule a particular time of day when the Blue Iris server will always be turned on but the cameras will not be in use. While Blue Iris is running we do continuous recording.
We've been having issues with frequent corruption of the Blue Iris DB, which results in Blue Iris overflowing its allocated recording storage space, because it loses track of files that were already written to disk but where the corresponding DB records haven't been flushed to disk. I think the root cause of the DB corruption is that the PC sometimes is turned off by just cutting power rather than being properly shut down. Obviously that's bad for more reasons than Blue Iris alone, and I'm working on improving that situation, but right now it's not easy for me to guarantee that it always gets a proper shutdown. I accept that it's not reasonable to expect Blue Iris to avoid DB corruption under these circumstances; I don't think there's a Blue Iris bug.
But, regardless, because we're encountering DB corruption more often than we'd like, we want Blue Iris to do a database repair every time the service starts up. We would prefer to add a few minutes of startup delay to the system, rather than have to schedule the repair at a time of day where we would otherwise want uninterrupted operation & recording.
Is there a way to do this? E.g. via settings or scriptable command line instructions, or an API? I currently have 5.7.5.6 installed, but can upgrade if it will help.
Last edited:
