Search results

  1. U

    Feature request: Reboot required

    Thank you for the reply. If the kernel packages are updated to provide the standard Debian/Ubuntu /var/run/reboot-required.pkgs or /var/run/reboot-required, then that would be nice too. I use the needs-restarting and needs-restart tools in CentOS. I was unaware of a similar tool in Debian...
  2. U

    pvestatd: storage 'wxyz' is not online

    Proxmox 5.1. I found an older thread addressing this issue. I see these error messages a lot in the Proxmox /var/log/syslog. I am using an NFS storage location. First item is an enhancement request --- could the actual error message please be updated? Consider revising the text string "is not...
  3. U

    Windows XP vzdump failures

    Thank you for the quick reply. :) I did not install this specific system and I am feeling inept about the actual file location. I found /dev/pve/vm-223-disk-1 but there is no file extension. The conf file indicates 60 GB is allocated but I found no such files of that size. I ran an internal...
  4. U

    Windows XP vzdump failures

    I have a legacy Windows XP KVM running on Proxmox. The KVM system has been running for a long time. Recently the respective vzdump started failing. The cron job uses stop mode. As this is a legacy system we do not tinker with anything in the KVM. Have there been any Proxmox updates that could...
  5. U

    Feature request: Reboot required

    Certain Proxmox packages do not notify administrators of a required reboot. For example, the kernel, glibc, libc6, systemd. Likely there are other packages but those come to mind. With Debian and Ubuntu, such packages create /var/run/reboot-required.pkgs or /var/run/reboot-required. Those files...
  6. U

    [SOLVED] The system has no more ptys.

    Thank you Wolfgang. I tested lxc-pve_3.0.0-3. The test container correctly bind mounted /dev/pts with gid=5. With that mount option, the original expect script works too. Note: On the Proxmox host, /dev/ptmx has root:tty ownership. On the guest the ownership is root:root. I don't know if the...
  7. U

    [SOLVED] The system has no more ptys.

    Thank you for replying and confirming! In this one instance I am using the non-subscription repo, which I realize is, nominally, a testing point for the subscription repo, but I am surprised a *.0 package was pushed so shortly after release from upstream. The upstream 3.0.0 version was released...
  8. U

    [SOLVED] The system has no more ptys.

    With some digging I narrowed the cause to the lxc-pve-3.0.0 package from March 30. Reverting to lxc-pve-2.1.1 resolves the issue. With lxc-pve-3.0.0 the containers do not inherit gid=5. With lxc-pve-2.1.1 the containers inherit gid=5, which seems correct to me. The jump from lxc 2.1.1 to 3.0.0...
  9. U

    Export running VM as backup

    Basic approach: * Configure an external storage device to export some NFS shares. * Configure Proxmox to use that external storage location. * In /etc/pve/vzdump.cron create a cron job: 02 00 * * * root vzdump 101 --quiet 1 --mode snapshot --storage ${name of external storage} If desired...
  10. U

    [SOLVED] The system has no more ptys.

    Greetings, I am running Proxmox 5.1 fully updated with a CentOS 7 container, fully updated. I have a shell script in the CentOS container that uses the expect command. Up until about a month ago the script ran just fine. Today the script failed with: The system has no more ptys. Digging a...