Olares instance keeps stopping and requires manual restart; orphaned resources persist after app deletion

[abidals]

Hello Olares Team,

I am writing to report an ongoing issue with my Olares instance. The keeps stopping unexpectedly, and I am forced to restart it manually every few days.

Additionally, I noticed that even after deleting the experimental created app in Olares Studio, some resources (such as services and namespaces) are still running in the background. I have attached screenshots showing the remaining resources (e.g., wger-dev-abidal namespace with Configmaps and Service accounts) despite the app being deleted.

I suspect these leftover resources might be related to the instability, but I am not entirely sure. This issue has been persisting for about a month now.

Could you please investigate this and let me know how to resolve it?

Best regards,
Abidal A.

[pengpeng]

@abidals Could you please collect the system logs using olares-cli logs the next time you encounter this issue, and send them to hi@olares.com? This would help us investigate and identify the root cause.

There can be many possible causes for this issue. Therefore, we may need the logs to confirm the actual root cause.

Starting from version 1.12.6, we will gradually enhance the skill capabilities of olares-cli, with the goal of enabling local issue diagnosis as soon as possible.

We also plan to release a ticket system in 1.12.7 to help users report and manage issues more easily.

[abidals]

Thank you,

I've send you the logs via email with a downloadable link.

[eball]

Hi @abidals

Based on the logs you provided, it appears that prior to the most recent reboot, all processes on your device were unable to write logs properly. From our experience, this symptom usually points to a potential hard drive failure.

To troubleshoot this, we recommend logging into the device locally and keeping the session active. When the issue recurs, please refrain from rebooting immediately. Instead, check this active local session for any error messages, or run the dmesg command to see if there are any hardware-related error logs.

[abidals]

Thank you,

Is there a guide on how to do what you recommended?

My System:
PC: MINISFORUM AI X1 Pro
CPU: AMD Ryzen™ AI 9 HX 370 processor
RAM: 96GB (48GB loaned to VGA VRAM)
Olares Version: 1.12.5

[eball]

You can run a quick test first:

1. Connect the device to a monitor and a keyboard.
2. Open the system Terminal.
3. Run sudo dmesg -T -w to wait for hardware log output.
4. Use Olares normally. If it stops responding, check the screen for log outputs to see what went wrong.