Search results

Thank you for your help, when I made chown 100000:100000 on whole container filesystem it starting work properly. I must have made a mistake sometime in the past. Regards Matus

Files are readable for root:root /dpool/ROOT/subvol-400-disk-0# l total 90 drwxr-xr-x 2 root root 121 May 13 2022 bin drwxr-xr-x 2 root root 2 Nov 22 2020 boot ...... drwxr-xr-x 11 root root 13 Dec 11 2020 var I am not sure with your last. here is output: ls -al...

Hellou, when I try to backup unprivileged container on zfs I get this error messages: >vzdump 400 --storage syno10 INFO: starting new backup job: vzdump 400 --storage syno10 INFO: Starting Backup of VM 400 (lxc) INFO: Backup started at 2023-06-15 11:54:24 INFO: status = stopped INFO: backup...

Thank ypu. It means, that it is possible to have mix of v6 and v.7 nodes in one cluster. Regards Matus

Hi, I have cluster with 3 nods. Is it possible and safe to upgrade 1. node to v. 7 and migrate to it containers from nodes v. 6.x ? And then do it for other nodes? Or I have to do backups and restores after upgrade?

Hi Tony, I have couple of servers in cluster and my own IP addresses segment. I am using very simple bridged network configuration. When I try to use same conf on server rented from Hetzner with additional IP, virtual host was not able to communicate with outside world. Node network conf...

Hello, I have created ramdrive for proxy cache with this commands: >modprobe brd rd_size=5200000 >pvcreate /dev/ram0 >vgcreate vgramdisk /dev/ram0 >lvcreate -L 4G -n ramstorage vgramdisk >mkfs.ext2 /dev/vgramdisk/ramstorage >mount -o noatime /dev/vgramdisk/ramstorage /mnt/ramstorage Then I...

Above first ls is outside container on node second ls is inside container Problem occurs inside container when user try to use screen utility. When I try to run this as user, I receive error: sudo chmod 0666 /dev/ptmx sudo: no tty present and no askpass program specified After running chmod...

Hi, on one of our nodes in the cluster, appears problem with /dev/ptmx, after one of latest actualisation. Command ls -la /dev/ptmx /dev/pts/ptmx gives on node: crw-rw-rw- 1 root tty 5, 2 Mar 11 12:26 /dev/ptmx c--------- 1 root root 5, 2 Mar 7 15:07 /dev/pts/ptmx and on LXC container...

Thank you for comments. Sorry for my mistake, it is testing environment, therefore old kernel. After couple of restarts it is working well. There is only problem with installing Mellanox utilities. But they are not necessary.

We have problem to install Mellanox card on Proxmox 6 kernel: 4.15.18-24-pve Output of lspci -k: 04:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] Subsystem: Mellanox Technologies MT27710 Family [ConnectX-4 Lx] 04:00.1 Ethernet controller: Mellanox...

I know that running corosync on public IP is not good idea. But it worked for a log time. There is no problem with omping. Now I separate Node1 from cluster. When I try to join it to cluster I received a message: * this host already contains virtual guests Check if node may join a cluster...

PVE 4.15.18-40 here is output from journalctl -u corosync systemctl status corosync: pvecm status: here are views from Node1 and Node3-4 Node 2 (spate) is turn off.

Hello, after restart of one node (4) in my cluster which has 4 nodes, synchronisation stop working on this node. corosync.conf is same on all nodes: output from corosync nodes: Node 1 was restarted and output from systemctl status pve-cluster.service Node 2 is stopped. Could you help...

We have subscriptions (eg pve1c-ec6a8c4f9d) on both servers, but it looks like samba is not installed on alto.

103.cfg: arch: amd64 cores: 4 cpulimit: 4 hostname: web2.xxx.sk memory: 12032 net0: name=eth0,bridge=vmbr0,firewall=1,gw=xxx.xxx.xxx.xxx,hwaddr=4E:AA:F9:19:AA:CD,ip=xxx.xxx.xxx.xxx/24,type=veth onboot: 1 ostype: debian rootfs: zfs-containers:subvol-103-disk-1,size=150G swap: 16384 > zfs list -t...

I tried to migrate zfs LXC container from host with VE 4.4 to host with 5.2 Migration failed with this nessages: .... 20:51:29 26.8G rpool/ROOT/subvol-103-disk-1@__migration__ 20:51:30 26.8G rpool/ROOT/subvol-103-disk-1@__migration__ cannot share 'rpool/ROOT/subvol-103-disk-1': smb add...

Hi, after reboot, everything is OK. Thanks

I have two near identical system. After update/upgrade process kernels are different. Could you help?

Sorry I have one more problem. I again install v. 4.4 from ISO and insert deb http://download.proxmox.com/debian jessie pve-no-subscription in /etc/apt/sources.list apt-get upgrade - fails with error: Processing triggers for pve-manager (4.4-1) ... Job for pvedaemon.service failed. See...