After the latest update the system becomes unresponsive after some time. It looks like the amount of file descriptors rapidly rises at one point and then the system starts to hang.
Swap seems to be going crazy too
Does it disconnect from your computer and router as well?
What you posted is interesting to me because I was experiencing system hangs a while ago. Not so much recently. But I have Netdata tracking everything remotely so if I experience it again I’ll check out the swap.
What did you mean by “file descriptors” though? Which value are you using to measure that?
It completely locks up. No connection to router or PC anymore.
What did you do to resolve it?
File descriptors is measure of opened but not yet closed write operations as I understand it. So that would mean some program is trying to write/or just opening writes without writing and swamping the system. This is also measures in Netdata. You can search for it.
Looks like a bug tbh.
Same here,the system crashes after a while, it needs a urgent update or downgrade it to the previuos version,btw anyone knows how to do it go back to 1.3.1?
I have a different problem. My drive, which is connected via USB, sometimes disappears or gets unmounted. I didn’t have this issue in the previous version.
A complete lockup + disconnect is basically what I was experiencing.
Eventually the Zima team sent me a replacement Cube, which seemed to stop most of the crashes. But after that I still experienced the same issue when using ZeroTier to connect to the Cube, and also when using virtual machines, which is what makes me think it’s a RAM issue.
The only thing I’ve done to resolve it is hard resets when it crashes, and avoid ZeroTier and ZVM… Not really a solution. I’ve just been hoping it gets worked out eventually.
I understand the frustration you’re experiencing with your USB drive occasionally disappearing or getting unmounted. We’ve identified this issue and are actively working on a solution. A new version that addresses this problem will be released in the coming days. We appreciate your patience and apologize for the inconvenience caused. If you have any further questions or need immediate assistance, please don’t hesitate to reach out.
We have some initial ideas about the issue you’re experiencing, but we need to confirm them to pinpoint the exact cause. To help us investigate and resolve this as quickly as possible, could you please send us your remote ID, ZimaOS account credentials, and any relevant details? You can share this information directly via private message or email us at link@icewhale.org . We’ll use this to verify the issue and work on a fix. Thank you for your patience and cooperation!
Thanks for caring and trying to solve this problem with the latest version 1.3.2 at this moment my Zimacube its off since i can not rely with it. Im checking regulary this community hoping to hear about a fix tha will solve this massive failure of CasaOS version