ID: 12619
Title: Fix error on editing downtimes without specifying a new downtime start
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.1.0i1
If you edited a downtime and used the option "Change downtime end" without also
specifying "Change downtime start", an internal error "'<' not supported
between instances of 'NoneType' and 'int'" occurred.
ID: 12191
Title: brocade_fcport: Fix crash when data missing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Check brocade_fcport crashed when if_info data was missing.
Now, the check plugin isn't discovered in that case.
ID: 12424
Title: <tt>check_mail</tt>: Fix <tt>error: argument --connect-timeout: invalid int value</tt>
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
There was bug in the active check <tt>check_mail</tt>, which checks if the login into
a given mailbox is working. In case a connection timeout was configured, the check
crashed with
<tt>error: argument --connect-timeout: invalid int value</tt>
This has been fixed.
ID: 12635
Title: fileinfo, filestats: improve description of upper levels
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
The fileinfo and filestats rules have imprecise descriptions of upper levels
in their respective configuration rulesets. WARN and CRIT configuration
variables were described as "Warning/Critical if above", but the states were
already applied when the configured values were reached. This has been fixed by
changing the configuration descriptions to "Warning/Critical at or above".
ID: 11795
Title: Unknown services in the discovery page
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.1.0i1
Services for checks that need access to the host name, like
e.g. logwatch, were shown as unknown in the service discovery
page. This is fixed.
ID: 12320
Title: Hosts will use Classic SNMP backend for SNMP-v1 datasource
Component: Core & setup
Level: 2
Class: Bug fix
Version: 2.1.0i1
It was discovered that using SNMP-v1 datasource with default(Inline) backend may
lead to memory leak in fetcher processes.
Since this release a host configured with datasources SNMP-v1 will use Classic SNMP
backend thus eliminating the problem.
To enable the fix you may need to update site configuration using WATO or command
line.