Search results

  1. M

    [SOLVED] Imported CT doesn't start: Failed to mount "/dev/pts/8" onto "/dev/console"

    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...
  2. M

    Ran out of disk space getting input/output error

    Had same issue, did a systemctl restart pve-cluster and it cleared up.
  3. M

    sshfs on proxmox VE8

    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.
  4. M

    sshfs on proxmox VE8

    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.
  5. M

    Open file limits on unprivileged LXC

    Yep breaks everything. This instruction is wrong and dangerous. (PVE 7.1 here)
  6. M

    Lessen Scrub Impact on ZFS Storage

    so then how to reduce impact?
  7. M

    [SOLVED] Proxmox VE Screen out of range

    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...
  8. M

    [SOLVED] Proxmox VE Screen out of range

    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...
  9. M

    [SOLVED] lxc-start fails! --> unsupported debian version '9.1'

    Missing my point, it should be <14 then not <=13. :P
  10. M

    [SOLVED] lxc-start fails! --> unsupported debian version '9.1'

    ongoing. oddly, it's <=12, which means '12.0' would qualify, but 12.1 and 12.2 wont. shouldnt it be <=12.9999 or just <13?
  11. M

    ksm still high cpu usage

    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...
  12. M

    Many SSL_accept error

    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...
  13. M

    Force LXC CT to use secondary IP for all outbound connections? (how to force scope LINK?)

    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...
  14. M

    NO_PUBKEY DD4BA3917E23BF59 error

    Where to get and how to add the proxmox enterprise and no-sub gpg keys?
  15. M

    Apparmor in privileged container

    no answer from prox staff yet?
  16. M

    LXC container and running Docker

    search the forums, already asked: https://forum.proxmox.com/threads/apparmor-in-privileged-container.107989/
  17. M

    LXC and tvheadend - Continuity counter error

    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...
  18. M

    [SOLVED] pct start failed after apparmor update

    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.
  19. M

    LXC and tvheadend - Continuity counter error

    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...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!