ID: 0305
Title: apache_status: Fixed exception when agent reports HTML code as apache-status data
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.3i8
When the apache-status module is not enabled or the webserver is somehow missconfigured,
the agents HTTP request to the apache-status URL might return HTML code instead of the
expected textual response. Added code to detect HTML code and skip the webserver instance
in this case.
ID: 0304
Title: Escaping several unwanted chars from incoming log messages
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.3i8
There are several kind of chars which are not wanted to be included
in log messages. For example the null byte is nothing to be expected
in log messages. We simply remove those chars now from the log messages.
Single log lines do not contain new line chars (\n), since they are
already processed as single lines. But snmp traps might contain those
chars, which might break e.g. processing the log history (resulting
in error messages "Invalid line XX in history file..."). The newline
chars are now simply removed from the incoming data.
This might change incoming values, but this seems to be better than
before. In future, when trap the parsing/processing code is extended
by single value matching etc., we might be able to clean this up.
ID: 0303
Title: Old log entries were shown in event history first
Component: Event Console
Level: 1
Class: Bug Fix
Version: 1.2.3i8
In previous versions, when the event history views had a limit
applied, like it is configured by default, it happened that
too old entries were read first. When reaching the limit of entries,
the processing stopped and newer events were ignored.
The order of the log files during processing has now been changed.
ID: 0057
Title: Fix exception in WATO host editor on custom tag without topic
Component: WATO
Level: 2
Class: Bug Fix
Version: 1.2.3i8
When you've defined a host tag group in WATO that has no topic,
then the host edit dialog would be interrupted with an exception.
A simple workaround to this is to alwasy define a topic.
The problem has now been fixed. It had shortly been introduced by fixing a
problem appearing when you used a slash in the name of a tag group.
ID: 0301
Title: Handling messages of special syslog format correctly
Component: Event Console
Level: 1
Class: New Feature
Version: 1.2.3i8
The syslog RFCs allow different formats of syslog messages. The
message parsing code in the event console does support several
formats and should be able to deal with all formats allowed by
the specifications. However, one format was not supported in
past versions. Those messages were simply dropped and only seen
in the logs of the event console, when rule execution debugging
is enabled.
These log entries look as follows:
<tt><5>SYSTEM_INFO: [WLAN-1] Performing Background Scan : channel 12, active, 28 TU</tt>
The specific part here is the missing date/time and missing hostname
information, which is sent by most syslog clients. The parser has been
changed to be able to parse this format. The event console adds the
current date/time to the event and the IP address of the sending
client as host information.
ID: 0300
Title: cisco_fru_power: Trying not to inventorize not plugged in FRUs
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.3i8
In the previous version, the check did inventorize all FRUs reported
by the device. The devices also send information for slots which have
no FRU plugged in. This change tries to ignore all not plugged in slots.
ID: 0103
Title: services: Fixed bug with service inventory defined in main.mk
Component: Checks & Agents
Level: 1
Class: Bug Fix
Version: 1.2.3i8
There was an error message while inventory when using main.mk based config.