OpenMarine
How do I stop SignalK from flooding syslog and daemon.log ? - Printable Version

+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: How do I...? (https://forum.openmarine.net/forumdisplay.php?fid=3)
+--- Thread: How do I stop SignalK from flooding syslog and daemon.log ? (/showthread.php?tid=2883)



How do I stop SignalK from flooding syslog and daemon.log ? - Geronius - 2020-08-26

I am experimenting with OP2 and SignalK (1.33.0), all updated to latest version.
Although in SignalK I have turned off all logging options accessible through the web interface,
/var/log/syslog and /var/log/daemon.log get flooded with entries like these:


Code:
Aug 26 18:04:44 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.186 ms - 12#033[0m
Aug 26 18:04:49 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.578 ms - 206#033[0m
Aug 26 18:04:49 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.059 ms - 12#033[0m
Aug 26 18:04:54 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.591 ms - 206#033[0m
Aug 26 18:04:54 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 0.916 ms - 12#033[0m
Aug 26 18:04:59 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.191 ms - 206#033[0m
Aug 26 18:04:59 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.040 ms - 12#033[0m
Aug 26 18:05:04 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.485 ms - 206#033[0m
Aug 26 18:05:04 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.039 ms - 12#033[0m
Aug 26 18:05:09 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.889 ms - 206#033[0m
Aug 26 18:05:09 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.273 ms - 12#033[0m
Aug 26 18:05:14 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.669 ms - 206#033[0m
Aug 26 18:05:14 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.158 ms - 12#033[0m
Aug 26 18:05:19 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 2.368 ms - 206#033[0m
Aug 26 18:05:19 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.105 ms - 12#033[0m
Aug 26 18:05:24 openplotter signalk-server[16325]: #033[0mGET /signalk #033[32m200#033[0m 3.885 ms - 206#033[0m
Aug 26 18:05:24 openplotter signalk-server[16325]: #033[0mGET /signalk/v1/api/vessels/self #033[33m401#033[0m 1.708 ms - 12#033[0m


what settings cause this and how can I stop it?

Thanks
Michael


RE: How do I stop SignalK from flooding syslog and daemon.log ? - e-sailing - 2020-08-26

You can change signalk.service.

git clone https://github.com/e-sailing/OP-Desktop.git
cd OP-Desktop
cd SKsyslog
sudo bash SKsyslog.sh

(It will change the line
StandardOutput=syslog
to
StandardOutput=null
)


RE: How do I stop SignalK from flooding syslog and daemon.log ? - Geronius - 2020-08-26

it's silenced now, great. I directly modified /etc/systemd/system/signalk.service
thanks
Michael