[BUG] No failure detection even at highest settings

[charredchar]

Note
Most of the times, an issue you may potentially run into is not a bug. Instead, it is related to configurations, such as firewall rules, incompatible docker version, reverse proxy setups, etc.

If you are not sure, please don't open a bug report here. Instead, you can get the issue solved much faster by seeking help in our support forum: https://obico.io/discord.

Proceed to opening a bug report only if you are sure it is a defect in the code given a correct configuration.

I attempted to join the Discord server but I get an "Unable to accept invite" error.
I am not sure if it is a configuration issue or not but I had it working in the past but now it is not working.

Describe the bug
Running a print I knew would have a failure to see if Obico would properly alert me and to tune the sensitivity. But it didn't show any signs of finding a failure.

Screenshots

Hosting environment (please complete the following information):

• OS: Ubuntu 20.04.6 LTS on a Hyper-V VM
• Version: I can't actually find where this is listed?
• Hardware: 2x Intel Xeon E5-2650 v2, 192GBs of RAM, 40GB SSD

Additional context
I had the server functioning successfully some time last year before I had to shut it down for a move. After the move I had also redone my printer config after some changes to the printer and needed to re-add it to Obico. Everything appears to be functional, the WebUI says it is watching but it never marked this print as a failure or even any signs of it being suspicious like I've seen it do in the past.

While this doesn't tell me the version...

$ git checkout release
Already on 'release'
Your branch is up to date with 'origin/release'.

[kennethjiang]

I just tested the link https://obico.io/discord with a new discord account and it worked for me. Can you try it again or post a screenshot for the discord error here? Discord is quite important as I don't respond to github issues that quickly.

For now, you can try docker compose logs -f to see if there are errors to debug more.

[charredchar]

I just tested the link obico.io/discord with a new discord account and it worked for me. Can you try it again or post a screenshot for the discord error here? Discord is quite important as I don't respond to github issues that quickly.

I've noticed a lot of support is requested to move to Discord. I've tried to connect a few times but still get this error.

For now, you can try docker compose logs -f to see if there are errors to debug more.

compose log.txt

This is an output from my Putty console, the only thing edited was removing my auth_token.

[kennethjiang]

There are a lot of errors in your log file. it seems that the db is somehow corrupt. maybe you should erase everything and start over.

[charredchar]

I was afraid something like that might be the case... It'll take me a little time to reinstall, I'll probably just do a new VM to be safe (as you can tell by the name the current one is pretty old) and report back if I have any of the same issues.

Is there a way to test failure detection that doesn't involve a real print? I'm not a huge fan of trying to force a print to fail. lol And contrary to the first post I rarely have failures which is why I went a little bit before noticing it wasn't catching them. heh

[kennethjiang]

I was afraid something like that might be the case... It'll take me a little time to reinstall, I'll probably just do a new VM to be safe (as you can tell by the name the current one is pretty old) and report back if I have any of the same issues.

Is there a way to test failure detection that doesn't involve a real print? I'm not a huge fan of trying to force a print to fail. lol And contrary to the first post I rarely have failures which is why I went a little bit before noticing it wasn't catching them. heh

The only way that I'm aware of is to use the virtual printer in octoprint to simulate a print.