Same error, different problem: somehow the host's /dev/pts got remounted ro, only when starting a CT did it popup til later I tried creating a new screen window 'read-only filesystem'. Chased it down to /dev/pts being ro, did a mount -o remount etc.
So there are many causes to this error...
Aha rereading your answer it seems you did answer, apologies, but it wasnt immediately clear.
"As pve-cluster doesn't depend on a specific version this is fine" was the key part.
bump. This question was not answered. Seems key since many utilities are using fuse3 and dont want to pull the fuse package rug out from under pve-cluster et al.
Install 7.x and upgrade. However I think 7.x removed the HOLD-ALT-TO-HIGHLIGHT-KEY-TO-CHOOSE-BUTTON for keyboard only -- my servers dont have a lot of USB (which are user periferals..) - 2 USB slots: 1 for USB key and one for keyboard. Should be able to install with only keyboard! These are...
Even this on my ancient monitor is causing problems, likely because it's picking a 1280x900 or something mode. "Mode out of range".
Thrashing about trying to figure an X-based solution here (or go to 7.x install and upgrade apparently?)
EDIT: Solution - had a 6.2 usb key and little patience to...
I am not sure if i should care that it's using 60% of a core on a 54 core/ht box, but it still seems egregious.
I can try to tune it but Im nervous Ill cause it to explode with even worse usage or otherwise hobble the box (which has a few vms and lots of ct's)
I have 256GB ram, and while the...
The problem is that debian 10 and even 11 include the deprecated ISRG X3 root key which has been expired - and a default certbot install will use that CA. (Or you have not generated legitimate keys and are using snakeoil.pem still).
You need to install an updated certbot via install instrux on...
Better is to just put this all into the /etc/network/interfaces file:
auto eth1
iface eth1 inet static
address 192.168.55.2
netmask 255.255.255.0
gateway 192.168.55.1
scope link
The scope link is retained by proxmox when it recreates the file - but I assume on...
Course it does - you are flushing your caches away and increasing the reads from the disks dramatically. Much slower than reading from cache - response times will be slower, and in fact, you could run into head thrash on the disk reading and writing a whole lot at the same time, etc. Your system...
Updating the kernel as we did so long ago probably wont fix it since things have moved far forward in 4 years. You have another issue. You need to find a new related thread, or start a new one, as it's unrelated to this specific issue at that time.
interesting. Dont think I've had that problem, so far every time it's been tmpfs with journald. tmpfs ram shows up as 'buffers' for some reason (since its disk related i guess? though flushing buffers of course wont solve it! thus I feel it's misreported in the wrong column and sent me goose...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.