Re: periodic daily produces ridiculously huge report files

2023-08-12 Thread Michael Grimm
Michael Grimm  wrote

> 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.

FTR: It started with WITHOUT_INET6=yes. Recompiling world and kernel including 
IPv6 support brings "netstat -i -d -W -n" back to normal behavior. No more of 
netstat producing producing huge amounts of garbage. 

> 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?

Anyone?

Regards,
Michael




periodic daily produces ridiculously huge report files

2023-08-11 Thread Michael Grimm
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 
NameMtu NetworkAddress  Ipkts Ierrs 
IdropOpkts Oerrs  Coll  Drop
vtnet0 1490fa: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.105200 - 
-0 - - -
vtnet1*1500fa:16:3e:58:c8:c90 0 
00 0 0 0
lo0   16384lo0 20 0 
0   20 0 0 0
lo0   -- - -- - - -
lo0   -- - -- - - -
lo0   - 127.0.0.0/8127.0.0.1   20 - 
-   20 - - -
bridge0149058:9c:fc:00:61:18   186483 0 
0   173172 0 0 0
bridge0   - 10.2.2.0/2410.2.2.2546625 - 
- 6698 - - -
bridge0   - 10.2.2.199/32  10.2.2.1995198 - 
-0 - - -
bridge0   - 10.2.2.220/32  10.2.2.220  363021 - 
-0 - - -
ipsec0 1400ipsec0  852284 0 
0  1035859 0 0 0
ipsec0- 10.2.2.0/2410.2.2.250  391221 - 
-   941898 - - -
pflog033152pflog0   0 0 
049185 0 0 0
epair201a  149002:0a:28:51:b5:0a33154 0 
032531 0 0 0
epair203a  1490   02:0b:44:a0:f4:0a 2807 0 
0 2567 0 0 0
epair2a1490   02:22:d3:ae:82:0a 7635 0 
0 5435 0 0 0
epair1a1490   02:61:a8:aa:89:0a   142474 0 
0   132256 0 0 0
epair6a1490   02:b4:4a:c7:dd:0a  228 0 
0  213 0 0 0
epair5a1490   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 NetworkAddress   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/8127.0.0.120 - -
   20 - - -
bridge0 - 10.2.2.0/2410.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/2410.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