Search results

Hi, I have a strange behaviour on Proxmox 5: all of a sudden, the pct command is not responding. Doesn't matter which parameter I use. I've tried pct enter VMID, no response. When instead using lxc-attach -n VMID works. Does anyone know what shall I do to get pct command to respond again? Any...

Hi fireon, Thanks for this - pretty useful and have just tried it - works pretty well. Nevertheless, 2 issues I have so far: --------------------------------- 1) Apt-get Whenever I want to run apt-get update, I keep getting "Could not resolve 'apt-cacher.osit.cc'". Even if the connection to...

Shouldn't this parameter be set @proxmox install when the root system is on ZFS -> meaning that the install wizard should ask the user for this parameter? Just a thought as this can be ignored by many admin and lead to stability issue.

Had same issue - reducing ram within VMs is the way to stabilize Proxmox. Thank you for the tips.

Just to mention that this works perfectly with failover IP @ online.net as well. THANKS You just need to make sure that the same MAC address is being used for any failover IP that should be used by the container, and that the MAC address of eth0 on the container is also set to the same MAC address.

After reboot of the proxmox host, the resource usage within the pve admin UI is back...

Found my issue for the firewall parameters: centos 7.4 update re-enabled firewalld which was creating additional rules within the container. I disabled it and all good now with the firewall: systemctl stop firewalld systemctl disable firewalld BUT, I still can't see resource usage within the...

Hi, I'm using Proxmox VE 4.4-1. Recently, one of my LXC container stopped showing values within the pve admin interface. CPU usage, memory usage & swap usage are always showing 0%... even do the LXC container is running and using CPU, memory & swap! On top of that, I've realised that the...

Finally found the fix - and it was not related to proxmox or lxc! Thanks to https://github.com/systemd/systemd/issues/1961 Therefore, I just have to clean regularly systemd sessions within the LXC container with a script running on a daily basis: #!/bin/sh find /run/systemd/system -name...

Hey, thx for this! Tried to set the below within the /etc/pve/lxc/<CTID>.conf file of the container having docker: lxc.aa_profile: unconfined lxc.cgroup.devices.allow: b 7:* rwm lxc.cgroup.devices.allow: c 10:237 rwm I don't get the Error response from daemon: ApplyLayer exit status 1 stdout...

I've tried both below lines in /etc/pve/lxc/<CTID>.conf lxc.kmsg: 0 lxc.autodev: 1 It didn't help. Actually, I realise that systemd use 100% CPU and gets stuck when updating packages via yum. This only happens after the container has been running for a couple of days. It doesn't happen just...

Recently found this post: https://daniele.vigano.me/blog/2015/03/fedora-21-lxc-systemd-journald-at-100/ Shall I then add the below line to /etc/pve/lxc/<CTID>.conf file? Or within another config file? And then reboot? lxc.kmsg: 0 Thx for the feedback. Do you think the below is also required...

Hi, I've setup an LXC container (no protection, not unprivileged) with Centos 7 on proxmox 4.4-1/eb2d6f1e. Randonmly, from time to time, systemd is using 100% of the CPU. This creates major timeouts for all services running on this LXC container. The only way to get around this is to restart...

Fabian, thanks again for your help! Much appreciated. Restarting pvedaemon solved the issue!

Hi Fabian, Thx for the feedback - it's definitely not an issue on the client side as it doesn't work as well from other browsers and computers, via VPN or not. Then could you point out which wrong files could have been modified that would bring this error? As explained, these are the modified...

I found this post: https://forum.proxmox.com/threads/continuing-issues-with-pveproxy-and-pve-ssl-key.29886/ Then I tried the below (after following "Revert to default configuration" https://pve.proxmox.com/wiki/HTTPS_....x_and_newer)#Revert_to_default_configuration) : These 4 match (note...

Hi, I've followed the below article to add a COMODO certificate to Proxmox: https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#CAs_other_than_Let.27s_Encrypt So basically, I updated the 2 files related to my only node: /etc/pve/nodes/<node>/pveproxy-ssl.pem...

Have a workaround so far: - created a script checking the openvpn log - each time a connection from a client ip is successful, it adds the client public IP to an ipset with a timeout - this timeout is used on a iptables rule that allow connection to the web gui tcp 8006 via the public host ip...

Re-opened topic - again getting a blank page after a couple of reboots

Hi, I'm using Proxmox 4.4-1. I've closed the access to the web gui through the public IP of my proxmox server via a firewall rule. Then I added a vmbr1 with a internal IP network (10.2.2.0/24). I access this network via OpenVPN (specific network 172.26.230.0/20). The firewall rules are setup...