-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
😂 Got it, thank you all. Waiting for the next time the issue occurs.
-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
Still have problem. Is anything wrong? I config syslog server but can not get logs. tower-diagnostics-20230815-1839.zip
-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
Alright, already config syslog server.
-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
The issue still happened even after upgrading to the latest version. tower-diagnostics-20230814-0954.zip
-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
Alright, I've already rebooted it, let's monitor it for a while.
-
Containers expectedly shut down, VMs freeze, only a restart can solve the problem. v6.12.2
The Docker container unexpectedly shuts down two days after startup, and the virtual machine (VM) freezes, only a restart can solve the problem. When I started a container, i got a 403 error. And VM log show "failed to write entry". Prior to upgrading to v6.12.2, I managed a ZFS pool named 'pool'. However, after the upgrade, I renamed it to 'ssd'. I am suspecting that this issue might be due to some hidden configurations still using the old 'pool' name. tower-diagnostics-20230809-1159.zip
five-year-ticket1336
Members
-
Joined
-
Last visited