Search results

  1. S

    Proxmox 6 on home NAS - SLOOOWWWW

    I decided to test Proxmox 6 on my home PC where I installed 4 HD (8Tb) that I setup with RAIDZ1. From the start the speed of the raid set was just terrible but I managed to speed it up somewhat by using "zfs set sync=disabled rpool". Now I'm testing other methods to speed up the setup. Maybe...
  2. S

    Debian 10 template

    I use SSH over VPN. I'm pretty sure Byobu is the key to finding out what is really going on.
  3. S

    Debian 10 template

    Same problem with Proxmox 6 & Debian 10 template. (Tested on 2 different Hardware.) Byobu keeps "leaking" all over the place. It's easy to test. Just install Byobu on Debian 10 LXC template type "byobu" and then do "ls -ahl /" and "cat /etc/gai.conf". Byobu just uses tmux or screen as a...
  4. S

    ZFS type does not allow backup storage

    You were right. If you wan't to backup to ZFS, you propably need to create a storage "directory" first.
  5. S

    No IPv4 on LXC

    Reverse proxy sounds interesting. I have to look in to that, maybe you can point me in the right direction, but I'm still wondering if it's possible to run a LXC container without IPv4?
  6. S

    No IPv4 on LXC

    I might as well use 127.0.0.1/8 if it comes to that. I would prefer not to use ANY IPv4 address.
  7. S

    No IPv4 on LXC

    I'm running out of IPv4 addresses and was wondering what is the recommended way to configure only IPv6 address on LXC container?
  8. S

    Debian 10 template

    Yes. Something somewhere is leaking. It's not just with Debian 10. I'm getting this on a Proxmox 5 host that has hardly any load at all with containers that have zero load: Sep 04 05:41:19 pve12a kernel: Memory cgroup out of memory: Kill process 13694 (systemd-journal) score 279 or sacrifice...
  9. S

    cannot restore LXC from LZO and GZ

    Run in to this problem when the LXC container had a snap-shot. Unfortunately backup did not give any error message. Delete snap-shots and try again.
  10. S

    Debian 10 template

    Maybe I'm barking the wrong tree... Maybe the problem was not with Debian 10 template but rather with Webmin that I used to manage Bind. https://www.cvedetails.com/vulnerability-list/vendor_id-358/Webmin.html
  11. S

    Debian 10 template

    I'm assuming by "it" you mean MySQL/MariaDB? I know enabling nesting in options will enable MySQL to run. I'm mostly referring to memory and stability issues with the new template.
  12. S

    Debian 10 template

    F.Y.I Same thing with Debian 9 template that I upgraded to Debian 10. Conclusion: It's not the kernel and it's not the layer 1 option used in Debian 10 template until MySQL fix comes along because the Bind server does not have any need for nesting=1 option so I did not use it there? Anyway...
  13. S

    DHCP6 template

    So not really out-of-the-box then. DHCP on IPv4 was easy to implement on WAN but DHCP6 is a real pain.
  14. S

    Debian 10 template

    I'm going to take Debian 9 template and see how it upgrades to 10.
  15. S

    Debian 10 template

    Looks like I have to rebuild those 2 Bind servers with Debian 9 template. 10 is clearly not safe to use with Proxmox 5.
  16. S

    Debian 10 template

    Noticed something else odd about Debian 10 LXC template. It's the only template that somehow leaks text all over when using terminal and especially when using byobu. Here is an example of two "normal" commands that only Debian 10 container mixes up. cat /etc/bind/named.conf.options and... ls...
  17. S

    Debian 10 template

    It's definitely the KVM host. It killed named/Bind again but it's odd because on Proxmox side it shows plenty of memory.
  18. S

    Debian 10 template

    I thought of that and tried it but that hung. Had to kill the screen in byobu. When I tried Management/Console on Proxmox I got the time out error. Timed out after 60 seconds.
  19. S

    Debian 10 template

    Could this be a result of Host level "KSM sharing" on "KVM clients"? That is the only way I can make sense of the KVM client running out of memory without actually showing it on the Graphs.
  20. S

    Debian 10 template

    On the Client side it looks even better. Client view of KVM: