Bill, it's new since 16.7 and not completely obvious. It's our fault really.There may be something to read through the flowd file and partially restore it if it was damaged:# flowd-reader /var/log/flowd.logJonas, do you get any error readings on that?Best to keep the indexing running for now.
# flowd-reader /var/log/flowd.log
...FLOW recv_time 2016-09-01T16:02:42.659872 proto 17 tcpflags 00 tos 00 agent [127.0.0.1] src [10.42.50.254]:27402 dst [10.42.50.11]:53 packets 1 octets 87FLOW recv_time 2016-09-01T16:02:42.659872 proto 17 tcpflags 00 tos 00 agent [127.0.0.1] src [10.42.50.254]:41226 dst [10.42.50.10]:53 packets 1 octets 75FLOW recv_time 2016-09-01T16:02:42.659872 proto 17 tcpflags 00 tos 00 agent [127.0.0.1] src [10.42.50.254]:41226 dst [10.42.50.11]:53 packets 1 octets 75root@OPNsense:~ #
...The graphs look ok to me. There are data points for all of the 2h interval and your data collection started on August 31?...
root@OPNsense:~ # df -hFilesystem Size Used Avail Capacity Mounted on/dev/ada0s1a 77G 1.7G 69G 2% /devfs 1.0K 1.0K 0B 100% /devdevfs 1.0K 1.0K 0B 100% /var/dhcpd/devroot@OPNsense:~ #
root@OPNsense:/var/log # ls -lah /var/log/flowd*-rw------- 1 root wheel 2.1M Sep 2 12:50 /var/log/flowd.log-rw------- 1 root wheel 11M Sep 2 12:21 /var/log/flowd.log.000001-rw------- 1 root wheel 11M Sep 2 10:25 /var/log/flowd.log.000002-rw------- 1 root wheel 11M Sep 2 08:12 /var/log/flowd.log.000003-rw------- 1 root wheel 11M Sep 2 05:58 /var/log/flowd.log.000004-rw------- 1 root wheel 11M Sep 2 03:29 /var/log/flowd.log.000005-rw------- 1 root wheel 11M Sep 2 00:58 /var/log/flowd.log.000006-rw------- 1 root wheel 11M Sep 1 22:46 /var/log/flowd.log.000007-rw------- 1 root wheel 11M Sep 1 20:17 /var/log/flowd.log.000008-rw------- 1 root wheel 107M Sep 1 17:56 /var/log/flowd.log.000009-rw------- 1 root wheel 11M Aug 31 20:39 /var/log/flowd.log.000010root@OPNsense:/var/log #