Replies: 1 comment
-
|
problem was ip4forward and a cron to enable it running every 10 minutes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Since I don't know if its the VM it's in or something else, fishing for anyone experiencing the same issue.
Found out few weeks back that it had stopped updating automatically, run the manual upgrade and now it fixed the automatic updates.
Around the same time, every 12 hours everything would stop for about ~10 minutes (monitoring with uptime kuma on another VM).
Few updates later, some days I there's no problem (only less than a minute offline), others still got 1/2 times of those ~10 minutes everything off.
Some command found that the server is generating over 500gb of logs everyday, so it rotates like crazy and I can't get more than some dozen minutes of logs.
Logging in at those times, DNS resolution, connection, containers... all functional. But still couldn't connect to any service or to coolify itself.
While it might be something with the setup, since it seems it started on updates and changes how much it affects from update to update, I'm also considering it to be related to it.
Running in a SUSE Linux Enterprise Server 15 SP6, currently at last version.
Beta Was this translation helpful? Give feedback.
All reactions