Some people stumbled upon a problem when installing LogAnalyzer v3.0.0. They got the following error message:
No syslog records found (code 8 ) – Error Details:
Unknown or unhandeled error occured.
Additionally, when “MiscShowDebugMsg” is enabled they would see the following:
LogStreamPDO|PrintDebugError: Invalid SQL: SELECT id, devicereportedtime, fromhost, infounitid, facility, priority, syslogtag, eventid, eventlogtype, eventsource, eventcategory, eventuser, systemid, checksum, message FROM systemevents WHERE id <= 45 ORDER BY id DESC LIMIT 100
Detail error: 42703;7;ERROR: column “checksum” does not exist
Error Code: 42703
These error messages result from a missing column in the database. More specifically, this is resulting in the need of LogAnalyzer’s report module for the checksum column in the database (usually this is the table SystemEvents), which is already present when creating the database with some of the MonitorWare Products, but which will not be created when using LogAnalyzer 3.0.0 to set up the tables for storing Events. This is indeed a bug. Usually, the checksum column is not part of the regular MonitorWare database scheme, because it is not needed. Currently only LogAnalyzer and MonitorWare Console need it.
There are two possibilities to resolve this issue. The first is to insert the column manually into the database. You can use the following SQL script to do this. Please note, that you might need to alter the tablename if you don’t use the default name SystemEvents.
ALTER TABLE `systemevents` ADD `Checksum` int(11) NOT NULL DEFAULT ‘0’ AFTER `SystemID`;
The second option is to update to LogAnalyzer 3.0.1. You can download it here: http://loganalyzer.adiscon.com/downloads/loganalyzer-3-0-1-v3-beta
When updating to the newest version, the database can be upgraded automatically for MySQL and PostgreSQL databases. If you use a different database, you have to insert the column manually into the SystemEvents table.