EyezOn Forum

Posted: **Mon Jul 29, 2019 1:21 am**

Is there a way to either fine tune the debug entries in my syslog files, or disable debug logging while leaving the general event logging enabled?

Not that I never ever want to see debug info, but if all I ever get is as follows, when the EnvisaLink is running ok:

Code: Select all

xxx@deb-box:/var/log$ sudo cat evl4debug.log
[sudo] password for xxx: 
<135>1 2019-07-28T09:50:56.967548-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:50:58.967468-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:51:02.967334-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:51:10.967515-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:51:13.467410-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:51:16.466958-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:54:07.465755-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:54:10.972963-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:55:36.456218-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:55:40.963761-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:55:49.456033-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:55:53.955957-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:56:05.963142-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:56:35.454637-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:56:38.462301-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:56:46.462509-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:56:53.454753-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01
<135>1 2019-07-28T09:57:07.454509-06:00 192.168.1.36 ENVISALINK xxxx MAC xxxx - -   PS: 01

then Its not serving much of a purpose other than filling a rotated file over and over (username and MAC of EVL4 obscured by me). Fortunately, the rotation function gzips older files down to pretty small sizes, but still ...

Or have I missed something? I've searched for, and found, precious little info on the syslog client and what it sends to the server. But maybe I just haven't found the right reference? If there's documentation on configuring the syslog client function (aside from the general 1-pager on how to enable logging to a server), just point me at it and I'll take it from there.

Thanks for any nudges.

Posted: **Mon Jul 29, 2019 7:26 am**

Submit a tech support request from your Eyezon portal. I've never seen anything like that before and we use the syslog client all the time for testing.

Posted: **Wed Jul 31, 2019 11:01 am**

Thanks for pointing that out. It looks like it is a left-over from build testing that should have not have made it into the release. There shouldn't be any debug syslog entries in a normal release.

Posted: **Thu Aug 01, 2019 3:03 am**

I've submitted a support request via the Portal, under "Alerts and Messages" and mentioned that I posted the issue here in the forums. Hope that's sufficient - if not, let me know what you need me to provide.

I kinda wondered why this debug "info" just gets output and repeated over and over, it made no sense. Now you've confirmed it wasn't meant to be part of a debug output log. And that means I can get rid of gz'd debug files (my linux box thanks you !)

EyezOn Forum

EVL4 DSC Debug in Syslog

EVL4 DSC Debug in Syslog

Re: EVL4 DSC Debug in Syslog

Re: EVL4 DSC Debug in Syslog

Re: EVL4 DSC Debug in Syslog