Search results

And addional info for community: Sometimes pvesr stuck (for a one day or more) in SYNCING state: 2420-0 Yes local/pve1 2022-01-10_16:07:26 pending 7.537101 0 SYNCING but container is working normally. On lsof -p pvesr_pid you can see...

Small update (forgot to inform about this, it may be useful for community): /sys/fs/cgroup/freezer/lxc/XYZ# echo THAWED > freezer.state help to unfreeze pvesr and container (if it stuck in FREEZING state) and kill (or stop) them. It`s a bug, bug, bug.

Small updates: https://github.com/lxc/lxc/issues/3578 https://bugzilla.proxmox.com/show_bug.cgi?id=3117

osmos, "zfs list | grep 103" showing legacy mount point?

Hello everyone! When i was running some tests with privileged container (based on old centos distribution) - i`m find that cpulimit doesn`t work if i use chrt command. I think that it`s correct, but cannot find proper way to deal with this (CAP_SYS_NICE give all capabilities). Can anyone know -...

We try to use kernel 5.3.18-3 and issue is persist. Then process in container read or write file to nfs share (via bind mount) and pvesr enabled for container replication - sometimes container is stuck (freeze) forever. Soft mount of NFS share to host - not helps. Stack trace and ps faxo...

We investigate this issue and find by: ls -lh /proc/PROC_ID/fd that some processes on container (that stuck in 'FREEZING') accessing to folder on NFS share. NFS share is mounted to container as folder: lxc.mount.entry: /mnt/pve/NAS_records/1013 var/spool/XYZ none bind,create=dir 0 0 NFS...

kweevuss are you use storage replication in your configuration?

Hello, all. After upgrade one node of our cluster (3 nodes, 2 of them is pve 6.2, replication hangs from 6.2 to 6.2: pve2->pve1) - we seen that replication regulary hangs on different containers and only reboot whole node is helps. Before upgrade - all working fine in this configuration. pvesr...

Recompile without BUILD NATIVE helps.

Hello. We have updated one of our server in cluster from pve5 to pve6 and found several problems. One of them: After we migrate our PBX container (Asterisk, FreePBX) to pve6 it`s doesn`t start with: traps: asterisk[47551] trap invalid opcode ip:81f0e19 sp:ffed1cd0 error:0 in...

We try to change /lib/systemd/system/pve-cluster.service: change Before=corosync.service to After=corosync.service and It works (as workaround after reboot).

Many thanks for answer! Yes, we try to step-by-step upgrade of our 3 nodes to 6. One node is upgraded to 6. Cluster is quorate: root@pve1:/etc/pve# pvecm status Cluster information ------------------- Name: aaa Config Version: 16 Transport: knet Secure auth: on...

Recently we upgrade 5.4 to 6.1 and replace ifupdown to ifupdown2. After changes - pvestatd and pve-firewall doesn`t start after reboot, logs showing only - timeout. If 'systemctl start pvestatd' invoked by hands - service starts. Can someone help us - find the right direction to debug this ...

+1 to Maeg. Anyone found root cause of this and solution? We found this on the lab with 2xLXC (Debian and CentOS).

I think that we found the root cause of this issue. It`s lxc-freeze command, that issued by pvesr and it work as expected - container is freezing. I don't have enough time now to find the reason of this and need to do some tests (replication is off - as my colleagues said), and read the docs...

We separate the cluster network (move to dedicated nic), cluster is fine, problem (issue) is persist and nothing was changed as expected. We will try to profile the components by strace and perf, debug corosync, lxcfs(fuse) and update glibc in container.

It`s not an argument for network engineer, activity from corosync (bidirectional!) is approx (without DSCP and CoS values): 400packets*162bytes = 64800 bytes in 120 ms. For 1 second rate is 5.2 Mbit/s. And additional network interface needed for 5Mbit/s traffic? We will try to setup dedicated...

Many thanks for answer, gosha. Then internal traffic in 3 nodes cluster (without shared storage and replication) with 2 containers up to 10 Mbps (on Gigabit network) it`is not necessary, i think (we observe this issue in 2 nodes cluster with 1 container). Or you can describe why this network...

Hi all. We found some interesting thing, that container freeze for 1.2 sec then network activity from corosync started (unicast udp 5404->5405 between cluster members) and unfreeze after them ended (and rtp traffic burst detected). Any help would be appreciated.