zm 1.21.2 generates lots of useless messages in my log files

Support and queries relating to all previous versions of ZoneMinder
Locked
heyho
Posts: 3
Joined: Fri Jul 01, 2005 12:26 pm

zm 1.21.2 generates lots of useless messages in my log files

Post by heyho »

I've installed ZoneMinder 1.22.1 on ML9.1, works fine, but fills
/var/log/messages and /var/log/syslog with useless crap. See for yourself:

Jun 30 22:42:29 home kernel: bttv0: cap vgrab: queue 3 (1:176x144)
Jun 30 22:42:29 home kernel: bttv0: cap sync: buffer 2, retval 0
Jun 30 22:42:29 home kernel: bttv0: cap irq: capture 3 [start]
Jun 30 22:42:29 home kernel: bttv0: cap irq: done 3
Jun 30 22:42:30 home kernel: bttv0: cap vgrab: queue 0 (1:176x144)
Jun 30 22:42:30 home kernel: bttv0: cap sync: buffer 3, retval 0
Jun 30 22:42:30 home kernel: bttv0: cap irq: capture 0 [start]
Jun 30 22:42:30 home kernel: bttv0: cap irq: done 0
Jun 30 22:42:30 home kernel: bttv0: cap vgrab: queue 1 (1:176x144)
Jun 30 22:42:30 home kernel: bttv0: cap sync: buffer 0, retval 0
Jun 30 22:42:30 home kernel: bttv0: cap irq: capture 1 [start]
Jun 30 22:42:30 home kernel: bttv0: cap irq: done 1
Jun 30 22:42:30 home kernel: bttv0: cap vgrab: queue 2 (1:176x144)
Jun 30 22:42:30 home kernel: bttv0: cap sync: buffer 1, retval 0
Jun 30 22:42:30 home kernel: bttv0: cap irq: capture 2 [start]
Jun 30 22:42:30 home kernel: bttv0: cap irq: done 2
Jun 30 22:42:30 home kernel: bttv0: cap vgrab: queue 3 (1:176x144)
Jun 30 22:42:30 home kernel: bttv0: cap sync: buffer 2, retval 0
Jun 30 22:42:30 home kernel: bttv0: cap irq: capture 3 [start]
Jun 30 22:42:30 home kernel: bttv0: cap irq: done 3

How can I get rid of this? I know these are kernel messages, but how to configure syslog.conf to instruct syslogd not to log this up^?
Cmon, it's realy annoying and fills my disk space with pure garbage.
PLZ!
jameswilson
Posts: 5111
Joined: Wed Jun 08, 2005 8:07 pm
Location: Midlands UK

Post by jameswilson »

how u get hold of 1.22.1??
heyho
Posts: 3
Joined: Fri Jul 01, 2005 12:26 pm

Sorry, typo error! 1.21.2 <-

Post by heyho »

Sorry, I've mistyped the version. Now what - kill me?':?:'

But the problem remains. I've searched over the entire forum to find something usable, but nothing. There is worse: the same is in /var/log/kernel/warnings AND file:/var/log/messages AND file:/var/log/syslog:

Jul 1 13:17:08 home kernel: bttv0: cap irq: done 3
Jul 1 13:17:08 home kernel: bttv0: cap vgrab: queue 0 (1:176x144)
Jul 1 13:17:08 home kernel: bttv0: cap sync: buffer 3, retval 0
Jul 1 13:17:08 home kernel: bttv0: cap irq: capture 0 [start]
Jul 1 13:17:08 home kernel: bttv0: cap irq: done 0
Jul 1 13:17:08 home kernel: bttv0: cap vgrab: queue 1 (1:176x144)
Jul 1 13:17:08 home kernel: bttv0: cap sync: buffer 0, retval 0
Jul 1 13:17:08 home kernel: bttv0: cap irq: capture 1 [start]
Jul 1 13:17:08 home kernel: bttv0: cap irq: done 1
Jul 1 13:17:09 home kernel: bttv0: cap vgrab: queue 2 (1:176x144)
Jul 1 13:17:09 home kernel: bttv0: cap sync: buffer 1, retval 0
Jul 1 13:17:09 home kernel: bttv0: cap irq: capture 2 [start]
Jul 1 13:17:09 home kernel: bttv0: cap irq: done 2
Jul 1 13:17:09 home kernel: bttv0: cap vgrab: queue 3 (1:176x144)
Jul 1 13:17:09 home kernel: bttv0: cap sync: buffer 2, retval 0
Jul 1 13:17:09 home kernel: bttv0: cap irq: capture 3 [start]
Jul 1 13:17:09 home kernel: bttv0: cap irq: done 3
Jul 1 13:17:09 home kernel: bttv0: cap vgrab: queue 0 (1:176x144)

this is what goes to /var/log/kernel/info

Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=8, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=2, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=8, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=2, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=8, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=2, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=8, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:24 home kernel: bttv0: irq loop=0 risc=2, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:25 home kernel: bttv0: irq loop=0 risc=8, bits: VSYNC HSYNC OFLOW RISCI*
Jul 1 13:20:25 home kernel: bttv0: irq loop=0 risc=2, bits: VSYNC HSYNC OFLOW RISCI*

It makes large log files. LARGE. Eventually with events it will grow until it fills my disk with crap.

Here is my syslog.conf:

# Various entry
auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none;kern.!=* -/var/log/syslog
user.* -/var/log/user.log
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
kern.!=notice;*.info;mail.none;;news.none;authpriv.none;kern.!=info -/var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Mail logging
mail.=debug;mail.=info;mail.=notice -/var/log/mail/info
mail.=warn -/var/log/mail/warnings
mail.err -/var/log/mail/errors

# Cron logging
cron.=debug;cron.=info;cron.=notice -/var/log/cron/info
cron.=warn -/var/log/cron/warnings
cron.err -/var/log/cron/errors

# Kernel logging
kern.=debug;kern.!=info;kern.!=notice -/var/log/kernel/info
kern.=warn -/var/log/kernel/warnings
kern.err /var/log/kernel/errors

# Lpr logging
#lpr.=debug;lpr.=info;lpr.=notice -/var/log/lpr/info
#lpr.=warn -/var/log/lpr/warnings
#lpr.err -/var/log/lpr/errors

# News logging
#news.=debug;news.=info;news.=notice -/var/log/news/news.notice
#news.=crit -/var/log/news/news.crit
#news.=err -/var/log/news/news.err

# Daemons logging
daemon.=debug;daemon.=info;daemon.=notice -/var/log/daemons/info
daemon.=warn -/var/log/daemons/warnings
daemon.err -/var/log/daemons/errors


# Everybody gets emergency messages
*.emerg *

# Save mail and news errors of level err and higher in a
# special file.
uucp,news.crit -/var/log/spooler

# Save boot messages also to boot.log
local7.* -/var/log/boot.log

# Explanations from Mandrake Linux configuration tools
local1.* -/var/log/explanations
local7.none /var/log/radius/radius.log

Eehh? Any suggestions?
User avatar
lazyleopard
Posts: 403
Joined: Tue Mar 02, 2004 6:12 pm
Location: Gloucestershire, UK

Post by lazyleopard »

Those look like debug output from the bttv driver. Is there a line in your /etc/modules.conf (or /etc/modules.d/* or wherever) file saying something like "options bttv debug=" followed by some number other than zero?
Rick Hewett
heyho
Posts: 3
Joined: Fri Jul 01, 2005 12:26 pm

Post by heyho »

YOU are ABSOLUTELY right!
I had that debug options enabled. I corrected that and now it works flawlesly!
THANK YOU, Rick
User avatar
cordel
Posts: 5210
Joined: Fri Mar 05, 2004 4:47 pm
Location: /USA/Washington/Seattle

Post by cordel »

BTW,
I have a new rpm ready to be posted that installs the script for logrotate and will rotate the logs once a week. Just making sure all is working before I load it to the FTP. I can load it in testing if anyone is interested.
Regards,
Cordel
Image
Image
3939663646337

It's better to keep your mouth shut and appear stupid than open it and remove all doubt.
-Mark Twain
Locked