OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: phoenix on November 19, 2017, 10:03:43 am

Title: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 19, 2017, 10:03:43 am
I'm seeing the following errors in the telegraf log:

Code: [Select]
2017-11-18T15:52:58Z E! Error in plugin [inputs.system]: open /var/run/utmp: no such file or directoryFrom what I've read (hopefully correctly) this is a problem with a missing lsof but that's not supplied in OPNsense, is it? I can't see anywhere that netstat is input is defined in the config file, is there any way to disable that message or does something need fixing?
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: franco on November 19, 2017, 10:07:53 am
Hi Bill,

There is a lsof package in ports (which we don't enable), but it would seem that this is a Telegraf issue not correctly reading that data on FreeBSD...


Cheers,
Franco
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 19, 2017, 03:16:29 pm
Hi Franco

Thanks for the quick reply. Do you mean this is a problem with the upstream telegraf package or the plugin? Do you want me to file a bug on OPNsense github or on the telegraf bug system?
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: mimugmail on November 19, 2017, 04:49:42 pm
Please let ne double check tomorrow first :)
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: franco on November 20, 2017, 07:42:01 am
Bill, something to coordinate with the Telegraf authors for sure. lsof is not part of FreeBSD, either they need to change their data collection or the FreeBSD port needs a lsof dependency.


Cheers,
Franco
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 20, 2017, 07:47:20 am
Hi Franco

I thought that would be the case, I'll file a bug report with them.
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: franco on November 21, 2017, 05:47:52 am
Hi guys,

We're updating from version 1.3.0 to 1.4.4 with 17.7.8... it is probably a good idea to reevaluate on top of this newer version.


Cheers,
Franco
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 21, 2017, 10:41:35 am
I'll take another look at it when it's released, I'm currently on the 18.1b release so I might wait until that's GA before I can confirm if it's a bug. Just a quick question about 18.1, is there going to be anymore updates before release? I've not noticed any amiss on my installation, everything is working as it should. :)
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: franco on November 21, 2017, 11:11:33 am
The BETA approach for 18.1 makes sure that you can upgrade all packages and keep the newer FreeBSD underneath (if you have locked the operating system as described). So you get all the updates like you would on 17.7.x. :)


Cheers,
Franco
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 21, 2017, 11:25:07 am
So you get all the updates like you would on 17.7.x. :)
Excellent, I must have glossed over that bit of the announcement.  :-[  In that case, I'll be testing it as soon as it's released.
Title: Re: Telegraf logging errors for netstat, missing lsof
Post by: phoenix on November 22, 2017, 02:44:24 pm
Hi Franco

The upgrade went well and the error I mentioned above has gone but it's been replaced by this one:

Code: [Select]
2017-11-22T13:30:08Z E! Error in plugin [inputs.system]: open /var/run/utmp: no such file or directory

Just doing a: "touch /var/run/utmp" seems to have stopped that message being produced, I also restarted the telegraf server and also tried a reboot and no further messages.