OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: ejprice on October 31, 2018, 02:50:17 pm

Title: Empty /var/log/flowd.log
Post by: ejprice on October 31, 2018, 02:50:17 pm: Greetings!

I have just completed a fresh install on new hardware,updated to 18.7.6 then restored my config using the web ui. For some reason flowd does not appear to be writing data to /var/log/flowd.log

I have started flowd from the shell in the foreground:

Code: [Select]
root@hades:/var/netflow # flowd -d read_config: entering child_get_config: entering drop_privs: dropping privs without chroot send_config: entering fd = 4 send_config: done child_get_config: child config done recv_config: entering fd = 3 recv_config: ready to receive config Listener for [127.0.0.1]:2056 fd = 3 Adjusted socket receive buffer from 42080 to 524288 Setting socket send buf to 1024 privsep_init: entering drop_privs: dropping privs with chroot init_pfd: entering (num_fds = 0) init_pfd: done (num_fds = 2) client_open_log: entering answer_open_log: entering ^Cprivsep_master: child exited flowd_mainloop: monitor closed Exiting on signal 2
I've removed the file and allowed flowd to recreate it, but still nothing.

Any pointers would be appreciated.

Thanks in advance!
Title: Re: Empty /var/log/flowd.log
Post by: ejprice on November 01, 2018, 02:09:25 am: It seems to be fixed. No idea how or why.
Title: Re: Empty /var/log/flowd.log
Post by: franco on November 02, 2018, 06:59:15 pm: Strange... was this "fixed" after reboot or just after some time after import?

Cheers,
Franco
Title: Re: Empty /var/log/flowd.log
Post by: ejprice on November 03, 2018, 01:30:13 am: No, I have a strong aversion to rebooting except for kernel updates and the like.

I originally noticed there was nothing showing up in the Reporting->Insight view. The aggregator was running but flowd was stopped. I started flowd from the web UI and then checked the log file with flowd-reader but it returned no output. I restarted the daemon from the command line, still nothing. The file had bytes allocated and there was binary data in it, but I assumed it was corrupt since flowd-reader returned nothing.

Thats when I removed the file and restarted flowd again. It created the log file but it was zero bytes in size. No data was being written. I searched the forums here, found nothing and made a post. I went back for a second look and everything was working.

Weird.