[mythtv-users] log files too big
Eyal Lebedinsky
eyal at eyal.emu.id.au
Sun Mar 20 00:21:29 UTC 2005
Mary Strimel wrote:
> hi,
> I have a smallish root filesystem (7 GB or so), and the mythbackend.log
> files are quickly filling my disk.
Before I start, if there a proper doco that explains what events are
logged by which option?
I have the same problem. The bulk of my log is clogged with messages
like this:
2005-03-20 10:57:54.404 DVB#1 WARNING - Transport Stream Continuity Error. PID = 161
2005-03-20 10:57:54.404 DVB#1 PID 161 _continuity_count 1 cc 4
2005-03-20 10:57:54.405 DVB#1 WARNING - Transport Stream Continuity Error. PID = 81
2005-03-20 10:57:54.405 DVB#1 PID 81 _continuity_count 1 cc 3
2005-03-20 10:57:54.623 DVB#1 WARNING - Transport Stream Continuity Error. PID = 512
2005-03-20 10:57:54.623 DVB#1 PID 512 _continuity_count 2 cc 3
2005-03-20 10:58:24.178 DVB#1 WARNING - Transport Stream Continuity Error. PID = 512
2005-03-20 10:58:24.186 DVB#1 PID 512 _continuity_count 4 cc 1
2005-03-20 10:58:24.186 DVB#1 WARNING - Transport Stream Continuity Error. PID = 660
2005-03-20 10:58:24.187 DVB#1 PID 660 _continuity_count 8 cc 9
2005-03-20 10:58:24.187 DVB#1 WARNING - Transport Stream Continuity Error. PID = 650
2005-03-20 10:58:24.187 DVB#1 PID 650 _continuity_count 9 cc 10
2005-03-20 10:58:24.195 DVB#1 WARNING - Transport Stream Continuity Error. PID = 512
2005-03-20 10:58:24.196 DVB#1 PID 512 _continuity_count 12 cc 13
2005-03-20 10:58:25.045 DVB#1 WARNING - Transport Stream Continuity Error. PID = 512
2005-03-20 10:58:25.046 DVB#1 PID 512 _continuity_count 8 cc 9
2005-03-20 10:58:27.550 DVB#1 WARNING - Uncorrectable error in packet, dropped.
2005-03-20 10:58:27.550 DVB#1 WARNING - Transport Stream Continuity Error. PID = 512
2005-03-20 10:58:27.551 DVB#1 PID 512 _continuity_count 15 cc 0
2005-03-20 10:58:27.553 DVB#1 WARNING - Uncorrectable error in packet, dropped.
2005-03-20 10:58:27.553 DVB#1 WARNING - Uncorrectable error in packet, dropped.
This turns up even when I start the backend with no verbosity specified
(as Debian does). Many messages do not have a source prefix so one cannot
tell which verbosity option to turn off.
I notice that there are two verbosity options turned on internally
important general
and both are rejected is specified explicitly. I do not see a syntax
to turn off a specific option. I now use ('playback,jobqueue' removed):
none,record,channel,osd,file,schedule,commflag,audio
and wonder if I will miss something that 'important,general' had.
I still get these:
2005-03-20 11:17:42.812 DVB#1 PID 512 _continuity_count 4 cc 7
2005-03-20 11:17:42.812 DVB#1 PID 512 _continuity_count 8 cc 9
2005-03-20 11:17:42.812 DVB#1 PID 512 _continuity_count 14 cc 15
2005-03-20 11:17:42.815 DVB#1 PID 512 _continuity_count 8 cc 9
And while on the subject of logging, how do I get information about
the streams which was in 0.16:
Audiostream: Layer: 2 BRate: 384 kb/s Freq: 48.0 kHz
Videostream: ASPECT: 16:9 Size = 704x576 FRate: 25 fps BRate: 6.90 Mbit/s
--
Eyal Lebedinsky (eyal at eyal.emu.id.au) <http://samba.org/eyal/>
attach .zip as .dat
More information about the mythtv-users
mailing list