Change Details

On booting 1.3.0 (epa3), I saw something I never saw before at boot time: ``` vyos@gw# sudo journalctl|grep -i frr Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: failed to mkdir "/var/tmp/frr/watchfrr.889": File exists Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: crashlog and per-thread log buffering unavailable! ``` Upon checking `/var/tmp/frr` indeed there were directories left behind for old watchfrr processes: ``` root@gw:/var/tmp/frr# ls -la total 68 drwx------ 17 frr frr 4096 Nov 13 13:58 . drwxrwxrwt 1 root root 4096 Nov 13 14:05 .. drwx------ 2 frr frr 4096 Nov 13 13:58 bfdd.989 drwx------ 2 frr frr 4096 Nov 13 13:58 bgpd.953 drwx------ 2 frr frr 4096 Nov 13 13:58 isisd.976 drwx------ 2 frr frr 4096 Nov 13 13:58 ldpd.979 drwx------ 2 frr frr 4096 Nov 13 13:58 ldpd.981 drwx------ 2 frr frr 4096 Nov 13 13:58 ldpd.982 drwx------ 2 frr frr 4096 Nov 13 13:58 ospf6d.972 drwx------ 2 frr frr 4096 Nov 13 13:58 ospfd.969 drwx------ 2 frr frr 4096 Nov 13 13:58 ripd.963 drwx------ 2 frr frr 4096 Nov 13 13:58 ripngd.966 drwx------ 2 frr frr 4096 Nov 13 13:58 staticd.984 drwx------ 2 root root 4096 Nov 13 10:08 watchfrr.21842 drwx------ 2 root root 4096 Nov 13 9:24 watchfrr.889 drwx------ 2 frr frr 4096 Nov 13 13:58 zebra.944 ``` However improbable, the PID seemed to have clashed with an old and earlier invocation of the watchfrr process. What are the odds... Might be related to https://github.com/FRRouting/frr/issues/6541?

On booting 1.3.0 (epa3), I saw something I never saw before at boot time: ``` vyos@gw# sudo journalctl|grep -i frr Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: failed to mkdir "/var/tmp/frr/watchfrr.889": File exists Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: crashlog and per-thread log buffering unavailable! ``` Upon checking `/var/tmp/frr` indeed there were directories left behind for old watchfrr processes: ``` vyos@gw:/$ sudo ls -la /var/tmp/frr total 88 drwx------ 22 frr frr 4096 Nov 19 15:07 . drwxrwxrwt 1 root root 4096 Nov 21 00:00 .. drwx------ 2 frr frr 4096 Nov 19 15:07 bfdd.982 drwx------ 2 frr frr 4096 Nov 19 15:07 bgpd.946 drwx------ 2 frr frr 4096 Nov 19 15:07 isisd.967 drwx------ 2 frr frr 4096 Nov 19 15:07 ldpd.971 drwx------ 2 frr frr 4096 Nov 19 15:07 ldpd.972 drwx------ 2 frr frr 4096 Nov 19 15:07 ldpd.973 drwx------ 2 frr frr 4096 Nov 19 15:07 ospf6d.965 drwx------ 2 frr frr 4096 Nov 19 15:07 ospfd.961 drwx------ 2 frr frr 4096 Nov 19 15:07 ripd.956 drwx------ 2 frr frr 4096 Nov 19 15:07 ripngd.958 drwx------ 2 frr frr 4096 Nov 19 15:07 staticd.977 drwx------ 2 root root 4096 Nov 13 13:58 watchfrr.907 drwx------ 2 root root 4096 Nov 13 10:08 watchfrr.21842 drwx------ 2 root root 4096 Nov 13 9:24 watchfrr.889 drwx------ 2 root root 4096 Nov 19 15:07 watchfrr.900 drwx------ 2 root root 4096 Nov 14 13:30 watchfrr.905 drwx------ 2 root root 4096 Nov 14 13:20 watchfrr.906 drwx------ 2 root root 4096 Nov 15 09:04 watchfrr.909 drwx------ 2 root root 4096 Nov 19 13:53 watchfrr.914 drwx------ 2 frr frr 4096 Nov 19 15:07 zebra.937 ``` However improbable, the PID seemed to have clashed with an old and earlier invocation of the watchfrr process. What are the odds... FRR version: ``` vyos@gw:/$ show version frr FRRouting 7.5.1-20211107-00-ga122222f5 (gw). Copyright 1996-2005 Kunihiro Ishiguro, et al. configured with: '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' '--enable-exampledir=/usr/share/doc/frr/examples/' '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr' '--sysconfdir=/etc/frr' '--with-vtysh-pager=/usr/bin/pager' '--libdir=/usr/lib/x86_64-linux-gnu/frr' '--with-moduledir=/usr/lib/x86_64-linux-gnu/frr/modules' '--disable-dependency-tracking' '--enable-systemd=yes' '--enable-rpki' '--with-libpam' '--enable-doc' '--enable-doc-html' '--enable-snmp' '--enable-fpm' '--disable-protobuf' '--disable-zeromq' '--enable-ospfapi' '--enable-bgp-vnc' '--enable-multipath=256' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' 'build_alias=x86_64-linux-gnu' 'PYTHON=python3' ``` Might be related to https://github.com/FRRouting/frr/issues/6541?

On booting 1.3.0 (epa3), I saw something I never saw before at boot time: ``` vyos@gw# sudo journalctl|grep -i frr Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: failed to mkdir "/var/tmp/frr/watchfrr.889": File exists Nov 13 13:58:30 gw vyos-router[745]: 2021/11/13 13:58:30 WATCHFRR: crashlog and per-thread log buffering unavailable! ``` Upon checking `/var/tmp/frr` indeed there were directories left behind for old watchfrr processes: ``` rootvyos@gw:/$ sudo ls -la /var/tmp/frr# ls -la total 6888 drwx------ 1722 frr frr 4096 Nov 13 13:5819 15:07 . drwxrwxrwt 1 root root 4096 Nov 13 14:0521 00:00 .. drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 bfdd.9892 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 bgpd.95346 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 isisd.97667 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ldpd.9791 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ldpd.98172 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ldpd.98273 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ospf6d.97265 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ospfd.9691 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ripd.96356 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 ripngd.96658 drwx------ 2 frr frr 4096 Nov 13 13:5819 15:07 staticd.98477 drwx------ 2 root root 4096 Nov 13 13:58 watchfrr.907 drwx------ 2 root root 4096 Nov 13 10:08 watchfrr.21842 drwx------ 2 root root 4096 Nov 13 9:24 watchfrr.889 drwx------ 2 frr frr root root 4096 Nov 13 13:58 zebra.9449 15:07 watchfrr.900 drwx------ 2 root root 4096 Nov 14 13:30 watchfrr.905 drwx------ 2 root root 4096 Nov 14 13:20 watchfrr.906 drwx------ 2 root root 4096 Nov 15 09:04 watchfrr.909 drwx------ 2 root root 4096 Nov 19 13:53 watchfrr.914 drwx------ 2 frr frr 4096 Nov 19 15:07 zebra.937 ``` However improbable, the PID seemed to have clashed with an old and earlier invocation of the watchfrr process. What are the odds... FRR version: ``` vyos@gw:/$ show version frr FRRouting 7.5.1-20211107-00-ga122222f5 (gw). Copyright 1996-2005 Kunihiro Ishiguro, et al. configured with: '--build=x86_64-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' '--libdir=${prefix}/lib/x86_64-linux-gnu' '--libexecdir=${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' '--enable-exampledir=/usr/share/doc/frr/examples/' '--localstatedir=/var/run/frr' '--sbindir=/usr/lib/frr' '--sysconfdir=/etc/frr' '--with-vtysh-pager=/usr/bin/pager' '--libdir=/usr/lib/x86_64-linux-gnu/frr' '--with-moduledir=/usr/lib/x86_64-linux-gnu/frr/modules' '--disable-dependency-tracking' '--enable-systemd=yes' '--enable-rpki' '--with-libpam' '--enable-doc' '--enable-doc-html' '--enable-snmp' '--enable-fpm' '--disable-protobuf' '--disable-zeromq' '--enable-ospfapi' '--enable-bgp-vnc' '--enable-multipath=256' '--enable-user=frr' '--enable-group=frr' '--enable-vty-group=frrvty' '--enable-configfile-mask=0640' '--enable-logfile-mask=0640' 'build_alias=x86_64-linux-gnu' 'PYTHON=python3' ``` Might be related to https://github.com/FRRouting/frr/issues/6541?