-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'should always be an unindexed sample' panic #113
Comments
I can think of two potentially-relevant changes in Moonfire NVR itself between the two versions:
I would first try building without the It'd also be helpful to compare to logs from the old version, if you still have any around. In particular, I'd like to see the old log's match of the following new log lines, so we know what's changed on ffmpeg's side.
|
I also just noticed this error:
That's definitely a bug in Moonfire NVR itself. Could you set the environment variable it mentions to get some more info? |
Having been running for 1.5 hours with " RUST_BACKTRACE=1", spotted a few tracebacks. Current web interface has all four cameras showing, one with an infinity entry, otherwise all look normal. 1.5 hours of log at: https://pastebin.com/9KCUEagm |
Here's a log file representing 19 hours. It is just the log file, with ANSI, color codes, and continues from the previous log file I posted in #113 (comment) https://drive.google.com/file/d/1D9ZRn6aWfbuLqFca-gozmMuwO7d5JB-4/view?usp=sharing The current state of the web interface is that 2 cameras (this time garage_east & garage_west) have not content. The Reolink client display all four cameras and the Reolink cached events have files from all four cameras; there is no indication from the 307 cached files for March 10th (8+ hours) to suggest a failure. If you think you have identified what may be causing the problem and want to try pushing a change into a development version, I can clone such and build and run to test. Or I can patch my existing instance:
|
Haven't figured this out yet, but if you run the latest version the error messages will be prettier. 🤷♂️ I'm going to look more today. |
Sorry, I'm slow on being mindful to pick-up your latest builds; thank you for the hint. To that end I performed the following:
and I have launched a new session:
|
No worries; I was just making fun of myself for fixing the cosmetic stuff before the bug. Those changes shouldn't be necessary to figure out what's going on. I'll let you know if I do need you to pick up logging changes for htat. |
The problem has to be here: moonfire-nvr/server/db/writer.rs Line 662 in ed52152
The comment above says we must restore the invariant on all exit paths, but I missed one. If the offset from the previous pts doesn't fit in a |
e66a88a should fix this. |
This issue is being opened just as a placeholder for the moment.
History
I installed Moonfire-nvr in June, 2020, on a new clean RaspberryPi 4 purchased just for this software. My set-up included 8 TBs of disk space to hold the feeds of 4 Reolink cameras at high resolutions, e.g. 1920x1080, at high frame rates, e.g. 27+ frames/second. The performance went extremely well. Occasionally, some hiccups and I would restart one or more cameras.
I then upgraded Moonfire-nvr and probably performed several other upgrades to my Raspberry Pi environment. Since then, I have had intermittent problems with one or more cameras' feeds not being preserved and the web interface having little, if anything for some cameras. It did not seem camera specific; however, I have not fully analyzed the matter.
This issue is being opened to start tracking my investigation as to what the problem may be. I opened yesterday Issue #112 to document what I was doing to capture and preserve colorized logs. Scott's comments therein note that he does not colorize output, so the colorized output is coming from ffmpeg.
Current
Here is an example of my web interface showing two cameras (garage_west & Peck_west) down:
Here is a link to a 14 MB HTML formatted log preserving the coloration: https://drive.google.com/file/d/1UrQgLzgetLfCT8681uOOO9u1a_gGGKjU/view?usp=sharing
I have not reviewed the logs carefully, I just wanted to open this issue to set up a place where I can share my findings and our react to suggestions and other comments. Scott had mentioned recreating the ffmpeg command directly in a console against one of the cameras and see if the problems repeat themselves. I want to try building Moonfire-nvr in a Gentoo-based VM where I have more control over my environment and see if the same results occur there as in the RaspberryPi. I'm suspecting the problem I am facing is not necessarily related to Moonfire-nvr and is a problem with dependencies. Since RaspberryPi is a suggested platform for running this software, it merits further investigation.
The text was updated successfully, but these errors were encountered: