periodic daily produces ridiculously huge report files
- Reply: Michael Grimm : "Re: periodic daily produces ridiculously huge report files"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 11 Aug 2023 15:18:52 UTC
Hi, I recently upgraded from 13-STABLE to MAIN, now at FreeBSD 14.0-ALPHA1 amd64 1400094 #12 main-n264689-580cadd6a5f0, a custom kernel compiled *without* IPv6 (WITHOUT_INET6=yes). Ever since either upgrading to MAIN or WITHOUT_INET6=yes [1] I noticed that periodic daily still runs in the morning failing to mail ridiculously huge report files (>= 90 *GB*). [1] Can't remember when this started. I believe to have found the step in periodic daily causing these huge files, but I do not know why: 1) I used to run default daily_status_network_netstat_flags="-d -W" in /etc/periodic.conf This normally produces an output like: MWN> netstat -i -d -W -n Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop vtnet0 1490 <Link#1> fa:16:3e:37:a7:35 963666 0 0 1145053 0 0 0 vtnet0 - 1.2.3.4/32 1.2.3.4 859598 - - 1068898 - - - vtnet0 - 10.20.30.40/32 10.20.30.40 12176 - - 0 - - - vtnet0 - 50.60.70.80/32 50.60.70.80 0 - - 0 - - - vtnet0 - 100.100.100.10/32 100.100.100.10 5200 - - 0 - - - vtnet1* 1500 <Link#2> fa:16:3e:58:c8:c9 0 0 0 0 0 0 0 lo0 16384 <Link#3> lo0 20 0 0 20 0 0 0 lo0 - - - - - - - - lo0 - - - - - - - - lo0 - 127.0.0.0/8 127.0.0.1 20 - - 20 - - - bridge0 1490 <Link#4> 58:9c:fc:00:61:18 186483 0 0 173172 0 0 0 bridge0 - 10.2.2.0/24 10.2.2.254 6625 - - 6698 - - - bridge0 - 10.2.2.199/32 10.2.2.199 5198 - - 0 - - - bridge0 - 10.2.2.220/32 10.2.2.220 363021 - - 0 - - - ipsec0 1400 <Link#5> ipsec0 852284 0 0 1035859 0 0 0 ipsec0 - 10.2.2.0/24 10.2.2.250 391221 - - 941898 - - - pflog0 33152 <Link#6> pflog0 0 0 0 49185 0 0 0 epair201a 1490 <Link#7> 02:0a:28:51:b5:0a 33154 0 0 32531 0 0 0 epair203a 1490 <Link#11> 02:0b:44:a0:f4:0a 2807 0 0 2567 0 0 0 epair2a 1490 <Link#15> 02:22:d3:ae:82:0a 7635 0 0 5435 0 0 0 epair1a 1490 <Link#19> 02:61:a8:aa:89:0a 142474 0 0 132256 0 0 0 epair6a 1490 <Link#23> 02:b4:4a:c7:dd:0a 228 0 0 213 0 0 0 epair5a 1490 <Link#27> 02:ba:52:8a:6d:0a 185 0 0 170 0 0 0 But pretty often "netstat -i -d -W -n" produces garbage like spaces or "0". This fills /tmp pretty fast (luckily a compressed zfs filesystem) and my mta still tries to mail in the morning. 2) I modified /etc/periodic.conf to daily_status_network_netstat_flags="-d -W -4" This produces an output like: MWN> netstat -i -d -W -n -4 Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop vtnet0 - 1.2.3.4/32 1.2.3.4 859590 - - 1068102 - - - vtnet0 - 10.20.30.40/32 10.20.30.40 11592 - - 0 - - - vtnet0 - 50.60.70.80/32 50.60.70.80 0 - - 0 - - - vtnet0 - 100.100.100.10/32 100.100.100.10 5192 - - 0 - - - lo0 - 127.0.0.0/8 127.0.0.1 20 - - 20 - - - bridge0 - 10.2.2.0/24 10.2.2.254 6623 - - 6696 - - - bridge0 - 10.2.2.199/32 10.2.2.199 5196 - - 0 - - - bridge0 - 10.2.2.220/32 10.2.2.220 363021 - - 0 - - - ipsec0 - 10.2.2.0/24 10.2.2.250 391221 - - 941898 - - - This fixed my issue with periodic daily. But I would like to know, if this has to do with WITHOUT_INET6=yes or FreeBSD 14? Or something different ... Did someone of you experiences equal behaviour of "netstat -i -d -W"? Anyone with WITHOUT_INET6=yes willing to test this? Regards, Michael