May 06 05:00:06 proxmox pveproxy[15128]: got inotify poll request in wrong process

[Spirog]

Journal :

May 05 23:04:38 proxmox pveproxy[2283]: worker 22662 started
May 05 23:51:56 proxmox pveproxy[2283]: worker 13262 finished
May 05 23:51:56 proxmox pveproxy[2283]: starting 1 worker(s)
May 05 23:51:56 proxmox pveproxy[2283]: worker 31598 started
May 05 23:51:59 proxmox pveproxy[31597]: got inotify poll request in wrong process - di>
May 06 00:00:01 proxmox systemd[1]: Reloading PVE API Proxy Server.
May 06 00:00:02 proxmox pveproxy[33065]: send HUP to 2283
May 06 00:00:02 proxmox pveproxy[2283]: received signal HUP
May 06 00:00:02 proxmox pveproxy[2283]: server closing
May 06 00:00:02 proxmox pveproxy[2283]: server shutdown (restart)
May 06 00:00:02 proxmox systemd[1]: Reloaded PVE API Proxy Server.
May 06 00:00:09 proxmox pveproxy[31598]: worker exit
May 06 00:00:09 proxmox pveproxy[18780]: worker exit
May 06 00:00:11 proxmox pveproxy[33156]: worker exit
May 06 03:53:55 proxmox pveproxy[31597]: worker exit
May 06 03:54:10 proxmox systemd[1]: Stopping PVE API Proxy Server...
May 06 03:54:13 proxmox systemd[1]: pveproxy.service: Succeeded.
May 06 03:54:13 proxmox systemd[1]: Stopped PVE API Proxy Server.
May 06 03:54:13 proxmox systemd[1]: pveproxy.service: Consumed 2min 8.538s CPU time.
-- Boot 29f77e2fab5d4d9bbb0d0bb7dc3c9868 --
May 06 03:57:02 proxmox systemd[1]: Starting PVE API Proxy Server...
May 06 03:57:03 proxmox pveproxy[2281]: Using '/etc/pve/local/pveproxy-ssl.pem' as cert>
May 06 03:57:03 proxmox pveproxy[2284]: starting server
May 06 03:57:03 proxmox pveproxy[2284]: starting 3 worker(s)
May 06 03:57:03 proxmox pveproxy[2284]: worker 2285 started
May 06 03:57:03 proxmox pveproxy[2284]: worker 2286 started
May 06 03:57:03 proxmox pveproxy[2284]: worker 2287 started
May 06 03:57:03 proxmox systemd[1]: Started PVE API Proxy Server.
May 06 04:18:51 proxmox pveproxy[2285]: worker exit
May 06 04:18:51 proxmox pveproxy[2284]: worker 2285 finished
May 06 04:18:51 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 04:18:51 proxmox pveproxy[2284]: worker 7560 started
May 06 04:34:41 proxmox pveproxy[2287]: worker exit
May 06 04:34:41 proxmox pveproxy[2284]: worker 2287 finished
May 06 04:34:41 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 04:34:41 proxmox pveproxy[2284]: worker 10373 started
May 06 05:00:05 proxmox pveproxy[2284]: worker 7560 finished
May 06 05:00:05 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 05:00:05 proxmox pveproxy[2284]: worker 15129 started
May 06 05:00:06 proxmox pveproxy[15128]: got inotify poll request in wrong process - di>

root@proxmox:~# systemctl status pveproxy

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enab>
     Active: active (running) since Fri 2022-05-06 03:57:03 CDT; 1h 20min ago
    Process: 2275 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status>
    Process: 2281 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
   Main PID: 2284 (pveproxy)
      Tasks: 5 (limit: 154344)
     Memory: 253.8M
        CPU: 32.111s
     CGroup: /system.slice/pveproxy.service
             ├─ 2284 pveproxy
             ├─ 2286 pveproxy worker
             ├─10373 pveproxy worker
             ├─15128 pveproxy worker (shutdown)
             └─15129 pveproxy worker

May 06 04:18:51 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 04:18:51 proxmox pveproxy[2284]: worker 7560 started
May 06 04:34:41 proxmox pveproxy[2287]: worker exit
May 06 04:34:41 proxmox pveproxy[2284]: worker 2287 finished
May 06 04:34:41 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 04:34:41 proxmox pveproxy[2284]: worker 10373 started
May 06 05:00:05 proxmox pveproxy[2284]: worker 7560 finished
May 06 05:00:05 proxmox pveproxy[2284]: starting 1 worker(s)
May 06 05:00:05 proxmox pveproxy[2284]: worker 15129 started
May 06 05:00:06 proxmox pveproxy[15128]: got inotify poll request in wrong process - di>

I have letsencrypt certs for my servers port 8006 https://prox.server.tld:8006

Latest version or PVE

proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

if you need any other info please do let me know
thanks in advance for your help

Spiro

 

[datschlatscher]

Hi Spiro!

According to this thread these messages do not pose any threat to your system, they "just should not happen".

Still, if you follow the link that Dominic suggested, it seems somebody else was able to resolve this by running pvecm updatecerts.

 

[Spirog]

Hi Spiro!

According to this thread these messages do not pose any threat to your system, they "just should not happen".

Still, if you follow the link that Dominic suggested, it seems somebody else was able to resolve this by running pvecm updatecerts.

Hello thanks for your reply. I do not have a cluster though ? If I am correct ( which I could be wrong) is pvecm only if you have a cluster ? Not just 1 node ? Could it be just pve updatecerts then ?

 

[Spirog]

Nope. Pve updatecerts not working is not a correct command.

I did pvecm updatecerts
How to check if it’s still a warning ?

Thanks

 

[datschlatscher]

How to check if it’s still a warning ?

Well due to the problem being rather elusive, I'm not sure whether there is a direct way of testing this. I guess all you can do for now is to wait and see, and occasionally check the logs...

 

[RolandK]

i also see these with pve8

un 22 23:46:17 pve8 pveproxy[1402]: starting 1 worker(s)
Jun 22 23:46:17 pve8 pveproxy[1402]: worker 535170 started
Jun 22 23:46:22 pve8 pveproxy[535169]: got inotify poll request in wrong process - disabling inotify
Jun 22 23:47:41 pve8 pveproxy[535169]: worker exit
Jun 22 23:49:33 pve8 pveproxy[523417]: worker exit
Jun 22 23:49:33 pve8 pveproxy[1402]: worker 523417 finished
Jun 22 23:49:33 pve8 pveproxy[1402]: starting 1 worker(s)
Jun 22 23:49:33 pve8 pveproxy[1402]: worker 536708 started
Jun 22 23:50:40 pve8 pveproxy[1402]: worker 525257 finished
Jun 22 23:50:40 pve8 pveproxy[1402]: starting 1 worker(s)
Jun 22 23:50:40 pve8 pveproxy[1402]: worker 537198 started
Jun 22 23:50:43 pve8 pveproxy[537197]: got inotify poll request in wrong process - disabling inotify
Jun 23 00:03:34 pve8 pveproxy[535170]: worker exit
Jun 23 00:03:34 pve8 pveproxy[1402]: worker 535170 finished
Jun 23 00:03:34 pve8 pveproxy[1402]: starting 1 worker(s)