New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
5ba9-2271-442a-748c
9d5f-1da6-4588-7cfd
c316-4aa5-5402-d7e7
eb68-aab0-9b29-02a8
Interesting, i don't think i have 50 posts yet
Regarding the mount issues, I got a plausible workaround.
Most of the servers are already using the LTS branch for stability reasons.
Which means its bug fix only, so rarely getting any updates, however, these updates are applied automatically.
There seems to be issues, when they are applied, there is a small chance, under specific circumstances these can cause those mounting issues.
It does not affect any running containers nor does it seem to affect any data.
However, if this bug appears, you likely see it when you want to delete the container or reinstall it.
So you can't do it, because LXD is unable to unmount the container.
According to the developers, its possible to unmount the container by hand, however this method is not working reliability.
The only known working fix, would be rebooting the system.
I don't expect any fix soon, since the developers can't even reproduce that bug, but suggest where the issue may be.
Means, we will need to reboot the system now and then, to keep LXC/LXD up to date.
I will announce these reboots a few days ahead, containers will be started automatically, so as long your application is in auto start should be not a problem.
I expect a reboot to happen every few months, the downtime will not be more than a few minutes.
The Kernel will still be live patched as usually.
Currently I know the following nodes are affected and will be rebooted Tuesday 05.10.21 23:00 CET:
Dronten
Antwerp
Other nodes are not affected, as of now.
The bug should disappear, once we do the updates manually.
However, due to the recent breaking LXD update into the LTS branch, you need to boot your container by hand, after this maintenance. Auto start of some containers is not possible, but by starting it manually, a fix will be applied, you just need to do this once.
If you created the container recently, you are not affected by this.
Yeah, perhaps just don't use Ubuntu? Debian with a wrapper in go/bash would probably work a lot better, or you know, proxmox
Live patching can cause overhead and performance loss after a lot of times.
Debian has no lxd package, nor is debian officially supported by lxd.
Some people had plans to make a package for debian, but apparently this looks like it has been ditched.
LXD offers a full rest api, so I didn't see the point why you would write your own wrapper and proxmox uses a ubuntu kernel + ubuntu packages but its not using lxd which maybe explains why proxmox isn't affected by it.
I never have seen such issues yet.
No, it's debian.
Please google, Proxmox 7 uses the Ubuntu 21.04 Kernel.
Even if it says Debian, its not longer pure debian anymore after installing proxmox.
Debian 10 official kernel is version 4.x
Proxmox 6.x for Debian 10 using Ubuntu based kernel version 5.x
Yeah, okay, I already build my own kernel, so, I will just do a quick upgrade to it (it's v4), but damn, I was not aware of that, properly
Edit: stupid fucking idea; brought down all LXC containers because v4 is missing a bunch of features that apparmour/cgroup need
Fck annoying WAF cloudflare, I unable to paste any result.
@jbiloh, help them out please.
How?
Adjusting the WAF rules. They're way too strict.
Maybe remove the detection for backticks and dashes? They are required for markdown, but trip the WAF every time.
You don't have a LowEndTalk Premium Pass™, do you?
LET premium pass won't do jackshit, you need a platinum LET members card + Costco card for WAF to stop detecting you
About a week ago I had adjusted the settings on the waf and bot detect system to be more lax and by doing so we were able to @Neoon's system to work through cf. I am worried about making it even more relaxed but I am open to suggestions.
ed1a-21dd-5857-1261
Patch Notes:
added Almalinux 8.4
added Support for static IPv6 configuration (CentOS/Almalinux/Rockylinux)
If static IPv6 configuration is needed, it will be configured automatically
changed HAProxy entries will now be checked if they resolve and point to the Node
If the abuses remain on the same level, we keep the 3 months, will see.
Also, the inactivity system will now start stopping contains in the next week, which exceed the 60 days.
1 Week additional grace period, until the system will stop these containers.
Afterwards we will patch the system to delete containers that have been stopped for 1 week after exceeding the 60 days of inactivity.
You can anytime add your email to get notifications, 30, 14, 7 and 1 day(s) alerts will be send before the system will stop your container.
SSH Login is enough, to mark the container as active.
I mean this account is not conform with the rule .
Your website is broken for me.
I need more information, can't debug this, since apparently the CDN fails to deliver the css and js files.
Did you tried turning it off and on again?
d709-e0fc-f780-4a23
EDIT: Thanks @Neoon! BTW, I really like that panel's visual aesthetic - very playful.
Yes, i closed the tab and opened it again and it's the same!
Then do it again, press F12 and F5.
Show us why the browser fails to load these files.
If you getting blocked or anything else.
50 posts or does reply count? I don't think I'll ever come up 50 topics...
No!
Patch Notes:
added Termination after 67 Days of inactivity
Your container will get stopped after 60 days of inactivity, plus 7 days grace period, where you can log in and start the container again, if you wish to continue using it. After 7 days (67 days), your container will be terminated by the system.
So even if you don't subscribe to the notifications and forgot about it, with working monitoring, you should take notice.
removed SSH activity check
Please log in to the Portal instead, once logged in your account will be marked as active.