On Tue, Jan 07, 2025 at 03:57:15PM +0100, Christian Ruppert wrote: > It was restarted, not reloaded: > > zsh 10053 # lsof | grep haproxy | grep DEL > haproxy 10493 root DEL REG > 0,21 319 /dev/shm/haproxy_startup_logs_10491 > haproxy 10494 haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10495 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10496 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10497 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10498 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10499 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10500 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > haproxy 10494 10501 haproxy haproxy DEL REG > 0,1 66990 /dev/zero > > zsh 10054 # ps aux|grep hapro > root 10493 0.0 0.0 92416 8384 ? Ss 12:22 0:00 > /usr/sbin/haproxy -D -W -p /run/haproxy.pid -f /etc/haproxy/haproxy.cfg -S > /run/haproxy-master.sock > haproxy 10494 0.0 0.0 547340 28852 ? Sl 12:22 0:08 > /usr/sbin/haproxy -D -W -p /run/haproxy.pid -f /etc/haproxy/haproxy.cfg -S > /run/haproxy-master.sock > root 15127 0.0 0.0 6600 2176 pts/6 S+ 15:55 0:00 grep > --color=auto hapro > > 3.1.1 stable. I'm not sure if 3.1.0 was affected as well but before 3.1.x I > haven't seen that for sure. >
In this case that's your version of lsof which is not behaving like mine, just check in /proc/10493/fd, you shouldn't see any FD attached to the shm. It's just the shm which is not munmap(). My version of lsof is showing a "mem" type with a description, not the original file: haproxy 222416 root mem REG 0,29 49606 [anon_shmem:errors:startup_logs] (stat: No such file or directory) The fd is really closed just after opening the shm: https://git.haproxy.org/?p=haproxy-3.1.git;a=blob;f=src/errors.c;h=8c508e7af2c5b2cf48f5c7e87529bce8afcfcfde;hb=HEAD#l122 -- William Lallemand
