Search results

Seems its related to another post someone else posted earlier today. I found the below: --------------------------------------- I noticed this was mount read only on the problem node: devpts on /dev/pts type devpts (ro,nosuid,noexec,relatime,mode=600,ptmxmode=000) whereas this is rw on a...

I noticed this was mount read only on the problem node: devpts on /dev/pts type devpts (ro,nosuid,noexec,relatime,mode=600,ptmxmode=000) whereas this is rw on a node working fine: devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

ooo I get exact same issue. Been struggling with this one. mesg: change /dev/pts/4 mode failed: Read-only file system Really not sure what is the cause. Thought I was alone :)

We migrated some OpenVZ containers to LXC Proxmox 5.2.2 and now it does not seem to be able to SSH Server refused to allocate pty stdin: is not a tty We already tried removing or commenting out a line from /etc/rc.sysinit #/sbin/start_udev Does not seem to work. Any ideas?

I am starting to think its overprovisioning. I moved some LARGE 800GB vps off that server to new one and it seems to be better. Could I be right? Its never reached 90% of disksuage though always at 2.2T of 5.4T

root@vz-cpt-1:~# pveversion -v proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve) pve-manager: 5.2-2 (running version: 5.2-2/b1d1c7f4) pve-kernel-4.15: 5.2-3 pve-kernel-4.15.17-3-pve: 4.15.17-13 pve-kernel-4.15.17-2-pve: 4.15.17-10 pve-kernel-4.15.17-1-pve: 4.15.17-9 corosync: 2.4.2-pve5 criu...

We always install using proxmox iso with lvm and ext4 and 50GB root and specify swap. The rest is all default. Space is only half used.

root@vz-cpt-1:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-aotz-- 5.30t 45.40 7.66 root pve -wi-ao---- 50.00g swap pve...

We have an issue we cannot figure out. Currently the issue that when we run snapshots on lxc containers the backups are successful but then if someone stops any ct and tries to start it it will not start and gives a read only filesystem error. We then reboot and all vps servers comr up again...

Seems related to https://github.com/lxc/lxc/issues/1841 Any help? We use LVM thin with HW RAID 10 Seems like it starts after backups to our NFS server.

Damn I'm silly :( I decided to update another node to latest version and reboot. Then ran LXC backups and poof. Same thing occurred few minutes later. Very weird. Gonna move some VPS off to another while I try and fix this issue.

root@vz-cpt-1:~# lxc-start -n 107 -F -l DEBUG -o /tmp/lxc-ID.log lxc-start: 107: cgroups/cgfsng.c: create_path_for_hierarchy: 1752 Path "/sys/fs/cgroup/freezer//lxc/107" already existed...

Syslog empty and it happened on new node aswell Think its the new kernel as that is all we changed was updating the servers.

How did you fix this?

Hi guys We have many nodes but one new one with some VMs on are now having issues with read only file system. It works fine for a day or two but when a new VPS is created it all of a sudden goes into read only mode until we reboot the server. Then all is well till the next VPS is created...

Hi I made a backup of a openvz vps where load was usually 2.5 or less constantly for months on proxmox 3.4 I then reinstalled the server using proxmox 5.2 and used cpulimit to limit the cpu similar to openvz using 8. I now notice however that load is at 26.00+ constantly after restoring it as...

How do I request this to be implemented? Is there a Feature request page?

I seem to have similar issue after it loads swap and then does LVM section - I however use LVM where it gets stuck. Not sure if its a similar issue but I am having some major trouble with 5.2 aswell with booting...

Ok well I guess I aint gonna reboot for while let me rather use Kernelcare from Cloudlinux then. Much safer.= to load kernels

Just noticed load go to 2000 and then rebooted Node and now got this error. I did fully update the server yesterday but did not reboot till now.