Recent content by Kan

My experience tells me we never can be sure all will work as attended, especially in a bulk process. That's why I didn't use pve6to7 script to avoid a potential breakdown of all my containers in the same time. I preferred to opt for only 1 potential failure and I was right. To me the support...

Finally is there a solution to make a CentOS 7 container working on PVE7 ? I migrated my CT from a PVE6 and nothing works ! It'll be pleasant if the PVE warns before finishing migration !

Hello, I need your opinion please. I have a 5 nodes pve6 cluster. Each node has his own independent storage. I want my nodes upgraded to pve7. I don't want to have temporaly 2 clusters : moving vm by backup/restore results on too long downtime. I don't want to use pve6to7 script on a...

The line 63 is in bold below : if [ -z "${CONSOLETYPE:-}" ]; then if [ -c "/dev/stderr" -a -r "/dev/stderr" ]; then CONSOLETYPE="$(/sbin/consoletype < /dev/stderr 2>/dev/null)" else CONSOLETYPE="serial" fi # stat /dev/stderr Fichier : « /dev/stderr » -> «...

ip r returns same thing that other CT that works correctly. Something is broken in the CT and I can't repair it. All errors I get when I run basic commands like below make me hopeless. I thought maybe rights on a directory had to be corrected somewhere... I have to resign to lose the 2 CT :( #...

Well I can ping only the gateway and other ip in the same vlan.

# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever...

The CT is unreachable (no ssh, no ping, not a firewall problem). When I restart network I get : # service network restart /etc/init.d/functions: ligne63: /dev/stderr: Permission non accordée /etc/init.d/functions: line 63: /dev/stderr: Permission denied Restarting network (via systemctl)...

When I start the CT with debug I can see problem with cgroups. But I have no idea how to fix it. lxc-start 100 20220330094646.174 DEBUG conf - conf.c:idmaptool_on_path_and_privileged:2741 - The binary "/usr/bin/newuidmap" does have the setuid bit set lxc-start 100 20220330094646.174 DEBUG...

At the begining the CT was on a PVE3. The CT has been backupped and restored on this PVE6. All worked fine for the 3 CT until a few days for the 2 CentOS 7. The error with venet0 has been fixed (maybe due to multi add/delete eth). But the main problem is how to fix all the errors "Failed to...

The container starts but no network. And restarting services returns permission error I didn't have before. Example with httpd : # service httpd restart /etc/init.d/functions: ligne63: /dev/stderr: Permission non accordée Redirecting to /bin/systemctl restart httpd.service Restarting network...

I added "nesting" with CT off. Then I started and rebooted CT but no change.

Unfortunatly this did not fix the problem. Still same errors in /var/log/messages and no service works... :( The strangest is the problem seems to occur on the 2 CentOS7 CT in the same time (90% sure). And why didn't it affect the debian CT ?

Ok and how can I turn on "nesting" please ?

Not sure that's what you requested... # cat /etc/pve/local/lxc/100.conf arch: amd64 cpulimit: 1 cpuunits: 1024 hostname: vm.xxxxxxx memory: 4096 net0: name=eth0,bridge=vmbr0,gw=123.123.123.254,hwaddr=8E:E2:49:BF:6B:05,ip=123.123.123.15/24,type=veth ostype: centos rootfs...