Failures on New Install #265
Replies: 4 comments 10 replies
-
Hi, @jacobabehm -- thanks for installing BirdNET-Pi! I'm sorry it seems you've installed a lemon, so to speak. I'm sure we'll get to the bottom of this and figure out a way to prevent it from happening. The second failure was addressed recently so I'm hopeful that we won't see this again for too many others (it only went unfixed for 4-6 hours), and you're correct that it is only a failure about the presence of The first failure, however, is more concerning, as I don't know how to explain it at all. It came from I'm not sure what is easiest for you to edit the file, (
to this
You won't need to restart any services manually for that change to take effect (unless it is hung as it seems could be the case). There might be some context for the logs at that point which could explain why My best, |
Beta Was this translation helpful? Give feedback.
-
Just failed again:
Thanks, @jacobabehm I think @ehpersonal38 may have identified the issue. I have access to another test system which I will be going through today and testing the new fix. I will keep you up to date with that. I hope you'll stick around while we get this figured out, as I do think the system itself is worth the trouble |
Beta Was this translation helpful? Give feedback.
-
Have reinstalleed BirdNET Pi a few times, even on different microSD cards but get the following only after a few minutes to an hour 18:56:46--- sig, rate = librosa.load(path, sr=sample_rate, mono=True, res_type='kaiser_fast') Any idea of how to resolve this please? |
Beta Was this translation helpful? Give feedback.
-
I have an install that's been running for a few days. Every few hours, it hangs on an error. The following from log is a successful connection followed by a failure:
Also, I was getting a different failure after the most recent upgrade:
I think this failure only occurred when there was a new results to write. If the job complete with "DONE! WROTE 0 RESULTS", no failure. There was no "apprise.txt" file, so I created one. The jobs now seem to complete fine with the above exception. Nothing is ever written to "apprise.txt".
Any idea what's going on?
Beta Was this translation helpful? Give feedback.
All reactions