You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
We have just had some weird issue with our Oura deployment. It was running reliably for months and months, no issues for a long time, just behaving well during this whole time, but now we had some hick-up on restart.
After some automatic OS update, it was started in daemon mode (as expected):
oura daemon --config config.toml
This command was logged. So we are sure that the binary was actually started.
But Oura did not start properly in this particular case. The executable was running, but it did not log anything. It did not crash. The binary just kept on running while not doing anything. If there is some issue on startup, then it should crash, so it would restart automatically. But it was just running and not doing anything.
We are still running Oura v1.8.3. There might be some improvements in newer version and we also need to upgrade soon, due to the hard-fork, but I wanted to report this issue.
Earlier we also had some somewhat similar problems, where the retry logic on startup was not working as expected. But in the case we could see some logs at last. In that case Oura was starting, something has failed and this initial failure was not properly handled. It got stuck in a similar stage, running but not doing anything. But now there were no logs.
We have: RUST_LOG='info' - so the debug logs won't appear.
Problem:
We have just had some weird issue with our Oura deployment. It was running reliably for months and months, no issues for a long time, just behaving well during this whole time, but now we had some hick-up on restart.
After some automatic OS update, it was started in daemon mode (as expected):
This command was logged. So we are sure that the binary was actually started.
But Oura did not start properly in this particular case. The executable was running, but it did not log anything. It did not crash. The binary just kept on running while not doing anything. If there is some issue on startup, then it should crash, so it would restart automatically. But it was just running and not doing anything.
We are still running Oura v1.8.3. There might be some improvements in newer version and we also need to upgrade soon, due to the hard-fork, but I wanted to report this issue.
Earlier we also had some somewhat similar problems, where the retry logic on startup was not working as expected. But in the case we could see some logs at last. In that case Oura was starting, something has failed and this initial failure was not properly handled. It got stuck in a similar stage, running but not doing anything. But now there were no logs.
We have:
RUST_LOG='info'
- so the debug logs won't appear.Resources:
The text was updated successfully, but these errors were encountered: