PVEProxy is usually error

[itvietnam]

Hi,

We have this error, this usually come after running backup on our PVE.

root@hv101:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-08-22 00:03:17 +07; 2 weeks 0 days ago
  Process: 40194 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
  Process: 19635 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
  Process: 40240 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
 Main PID: 40267 (pveproxy)
    Tasks: 4 (limit: 9830)
   Memory: 238.7M
      CPU: 2d 4h 52min 36.309s
   CGroup: /system.slice/pveproxy.service
           ├─18124 pveproxy worker
           ├─21589 pveproxy worker
           ├─29534 pveproxy worker
           └─40267 pveproxy

Sep 05 07:12:21 hv101 pveproxy[2789]: failed to accept connection: Too many open files
Sep 05 07:12:21 hv101 pveproxy[29533]: ipcc_send_rec[1] failed: Too many open files
Sep 05 07:12:21 hv101 pveproxy[29533]: ipcc_send_rec[2] failed: Too many open files
Sep 05 07:12:21 hv101 pveproxy[29533]: ipcc_send_rec[3] failed: Too many open files
Sep 05 07:12:21 hv101 pveproxy[40267]: worker 2789 finished
Sep 05 07:12:21 hv101 pveproxy[40267]: starting 1 worker(s)
Sep 05 07:12:21 hv101 pveproxy[40267]: worker 29534 started
Sep 05 07:12:21 hv101 pveproxy[29533]: got inotify poll request in wrong process - disabling inotify
Sep 05 07:12:25 hv101 pveproxy[29533]: worker exit
Sep 05 07:12:34 hv101 pveproxy[29534]: Clearing outdated entries from certificate cache
root@hv101:~#

We have to manual fix this problem by restart pveproxy.

Our current version:

root@hv101:~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve)
pve-manager: 5.2-3 (running version: 5.2-3/785ba980)
pve-kernel-4.15: 5.2-3
pve-kernel-4.13: 5.1-45
pve-kernel-4.15.17-3-pve: 4.15.17-13
pve-kernel-4.13.16-3-pve: 4.13.16-49
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-34
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
openvswitch-switch: 2.7.0-2
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-12
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9
root@hv101:~#

And pvestatd status:

May we know how to fix this permanent?

 

[Stoiko Ivanov]

There was a bugfix for a similar problem https://bugzilla.proxmox.com/show_bug.cgi?id=1843
The problem should be fixed with pve-cluster >= 5.0-29

please upgrade to the latest versions.

Would be grateful to hear if it fixes your problem!

 

[itvietnam]

proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve)

we use this newest version already bro.

 

[Stoiko Ivanov]

The `proxmox-ve` meta package has not been upgraded.
However some packages from PVE have newer versions.
Check with `apt update`
upgrade with `apt full-upgrade`