LinHES Forums http://forums.linhes.org/ |
|
Logging level http://forums.linhes.org/viewtopic.php?f=21&t=24588 |
Page 1 of 1 |
Author: | Big boy stan [ Tue Nov 01, 2016 3:03 pm ] |
Post subject: | Logging level |
Not a particularly big issue but is there a way to check the verbose setting or loglevel of the mythtv logs? My mythbackend seems to be full of useless information entries that dont really help solve problems for me. just clutter up when looking for other stuff. My mythbackend log is usually about 1.2M to 2M in size. Is that normal? The majority of it looks like this: Code: 2016-10-31T00:14:19.342346-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:19.342444-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b636f6ba10) as a client (events: 0) 2016-10-31T00:14:19.342525-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b636f6ba10) 'envy' disconnected 2016-10-31T00:14:20.443621-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:20.443732-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b636ffdc60) as a client (events: 0) 2016-10-31T00:14:28.657551-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b636ffdc60) 'envy' disconnected 2016-10-31T00:14:28.657637-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:28.657708-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b6370c15a0) as a client (events: 0) 2016-10-31T00:14:28.657777-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b6370c15a0) 'envy' disconnected 2016-10-31T00:14:28.657845-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:28.657914-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b637033dc0) as a client (events: 0) 2016-10-31T00:14:28.657981-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b637033dc0) 'envy' disconnected 2016-10-31T00:14:28.658048-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:28.658117-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b636f64b70) as a client (events: 0) 2016-10-31T00:14:28.658185-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b636f64b70) 'envy' disconnected 2016-10-31T00:14:34.663224-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1730 (HandleAnnounce) MainServer: MainServer::ANN Monitor 2016-10-31T00:14:34.663323-04:00 mythbackend[19904]: I ProcessRequest mainserver.cpp:1735 (HandleAnnounce) MainServer: adding: envy(55b637041720) as a client (events: 0) 2016-10-31T00:14:34.663494-04:00 mythbackend[19904]: I MythSocketThread(68) mainserver.cpp:7656 (connectionClosed) Monitor sock(55b637041720) 'envy' disconnected The messages.log and sudo.log are even larger. They have nothing but: Code: Oct 31 00:00:00 envy sudo: root : unknown user: vncsvc
Oct 31 00:00:01 envy sudo: root : unknown user: vncsvc Oct 31 00:00:02 envy sudo: root : unknown user: vncsvc Oct 31 00:00:03 envy sudo: root : unknown user: vncsvc Oct 31 00:00:05 envy sudo: root : unknown user: vncsvc Oct 31 00:00:06 envy sudo: root : unknown user: vncsvc Oct 31 00:00:07 envy sudo: root : unknown user: vncsvc Oct 31 00:00:08 envy sudo: root : unknown user: vncsvc Oct 31 00:00:09 envy sudo: root : unknown user: vncsvc Oct 31 00:00:10 envy sudo: root : unknown user: vncsvc Oct 31 00:00:11 envy sudo: root : unknown user: vncsvc Oct 31 00:00:12 envy sudo: root : unknown user: vncsvc |
Author: | nigelpearson [ Fri Feb 03, 2017 7:42 pm ] |
Post subject: | Re: Logging level |
Yes, the default log level for MythTV binaries is very verbose. If you do mythbackend -h, it reports: Code: Logging Options: --enable-dblog Enable logging to database. --loglevel Set the logging level. All log messages at lower levels will be discarded. In descending order: emerg, alert, crit, err, warning, notice, info, debug defaults to info So, to change it from info to notice, add '--loglevel notice' to /etc/sv/mythbackend/run - Code: [nigel@mythtv-server mythbackend]$ tail -2 /etc/sv/mythbackend/run exec su mythtv -c "/usr/bin/mythbackend -q --syslog local6 --loglevel notice" # fi [nigel@mythtv-server mythbackend]$ P.S. The vncsvc really annoyed me. I don't actually understand why services are trying to kill something on the server every second, so I just commented out this line in /etc/sv/vnc/finish: Code: sudo -u vncsvc vncserver -kill :1 An untested, better fix, might be to change it to:Code: su vncsvc -c "vncserver -kill :1"
|
Page 1 of 1 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |