Hi, I have able to reproduce, after 1hour.
I have enable debug to get it run in foreground. This time, the process was not crashed, but was hanging. output was simply hanging, and no more write in /var/log/pve-firewall.log Also, memory was pretty huge, and still increasing during the hang (not sure if it's related to debug mode) ps -aux|grep logger root 19434 26.2 0.4 1770688 1679136 pts/1 Rl+ 10:44 11:27 ./pvefw-logger after some minutes root 19434 24.8 0.8 3625024 3533496 pts/1 Sl+ 10:44 12:20 ./pvefw-logger I was able to do a coredump with gdb http://odisoweb1.odiso.net/core.19434.gz Hope it's help. ----- Mail original ----- De: "Wolfgang Bumiller" <w.bumil...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "David Limbeck" <d.limb...@proxmox.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Lundi 14 Janvier 2019 08:01:54 Objet: Re: [pve-devel] [PATCH firewall] make nfct_catch non-blocking On Fri, Jan 11, 2019 at 06:05:36PM +0100, Alexandre DERUMIER wrote: > >>Do you have any additional information as to why it stopped? > > no sorry. > > >>Maybe we could increase the buffer size via nfnl_set_rcv_buffer_size by > >>default and continue to ignore ENOBUFS? > > I'll try next week. maybe doing strace on the process to have some clues ? > (I'ts crashing after 30min-1h) A coredump should work and produce less noise, perhaps? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel