[LogReport Questions] DBD::SQLite2::st: no such table: dlf_lire_import_log(1) / Re: Lire errors found in syslog

Joost van Baal joostvb at logreport.org
Sat Nov 24 22:11:04 CET 2007


Hi grummond,

Op Wed 21 Nov 2007 om 08:46:42 +0000 schreef x_logreport-questions_x at nospam.pz.podzone.net:
> I have logwatch installed, so it emails me out of the ordinary
> messages found in syslog.  Such as this:
> 
> Nov 11 08:30:26 duke lire: lr_log2mail: WARNING DBD::SQLite2::st execute failed: disk I/O error(1) at dbdimp.c line 419 at /usr/share/perl5/Lire/DlfStream.pm line 283, <$fh> line 209519.
> Nov 11 08:30:26 duke lire:
> Nov 11 08:30:26 duke lire: lr_log2mail: WARNING DBD::SQLite2::st execute failed: no such table: dlf_lire_import_log(1) at dbdimp.c line 412 at /usr/share/perl5/Lire/DlfStream.pm line 283, <$fh> line 209519.
> Nov 11 08:30:26 duke lire:
> Nov 11 08:30:26 duke lire: lr_log2mail: ERROR DBD::SQLite2::st execute failed: no such table: dlf_lire_import_log(1) at dbdimp.c line 412 at /usr/share/perl5/Lire/DlfStream.pm line 283, <$fh> line 209519.
> Nov 11 08:30:26 duke lire:
> Nov 11 08:30:28 duke su[31685]: + ??? root:lire
> Nov 11 08:30:28 duke su[31685]: (pam_unix) session opened for user lire by (uid=0)
> Nov 11 08:31:07 duke lire: Parsing log file using syslog DLF Converter...
> Nov 11 08:31:34 duke lire: Extracted 670 DLF records on 670 lines.
> Nov 11 08:31:34 duke lire: Encountered 0 errors and ignored 0 lines.
> Nov 11 08:31:34 duke lire: Running analysers...
> Nov 11 08:31:34 duke lire: Generating XML report...
> Nov 11 08:32:12 duke lire: Formatting report as txt and emailing it to root...
> 
> 
> The system is not misbehaving in any other way to lead me to suspect a
> dying hard drive, although it is under fairly heavy load with some
> scripts constantly running.  Exim, Apache, & Bind don't complain.
> 
> The bind query logs grew quite huge while DNS was under 'extreme' load
> ;-), so it maybe I upset lire by deleting some logs, or maybe the logs
> themselves are corrupt.
> 
> However, I raise this as an issue in case it leads to a bug discovery
> in lire... perhaps lire barfs in a situation not envisioned by the
> developer(s)?  I hope this is of some use to you.
> 
> Regards,
> 
> grummund @ irc://irc.freenode.net
> 
> (Currently idle in #logreport)

Thanks for reporting this.  I see you are using the syslog DLF
converter.  Are you using this converter for analysing your bind query
logs?  Perhaps filtering out these before feeding the rest of the log
file to the syslog converter would be a good idea.  The pure query logs
could get processed by the "bind9_query" converter.

Futhermore, I believe you told on IRC the resulting report looks just
fine.

As for the error message: I'm not sure what's going on here.  Do these
errors show up _every_ time you process a syslog file?  (FWIW: I found
one other similar message about SQLite2 errors:
http://lists.logreport.org/pipermail/questions/2004/000579.html .)

Bye,

Joost

-- 
.    .                           Log Analysis and Report Generation
| '.|        /^LogReport$/
| Lire                                    http://www.logreport.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: Digital signature
Url : http://lists.logreport.org/pipermail/questions/attachments/20071124/7b8b16a9/attachment.bin 


More information about the Questions mailing list