You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After Updating our Icinga Agents/Satellites to v2.10.0, we saw that it now appends the environment "production" to the SNI header on an TSL connection, even when environment is not set anywhere in the config.
Before v2.10.0, SNI was always like "master1-local-domon.testing.mms-at-work.de", with v2.10.0 it is now "master1-local-domon.testing.mms-at-work.de:production".
:production was new and broke our load balancing setup.
I think this came with #6512, but i dont know if its a bug or simply not mentioned in the upgradeing docs.
Your Environment
Version used (icinga2 --version):
icinga2 - The Icinga 2 network monitoring daemon (version: r2.10.0-1)
Copyright (c) 2012-2018 Icinga Development Team (https://www.icinga.com/)
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl2.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
System information:
Platform: CentOS Linux
Platform version: 7 (Core)
Kernel: Linux
Kernel version: 3.10.0-862.11.6.el7.x86_64
Architecture: x86_64
Build information:
Compiler: GNU 4.8.5
Build host: unknown
Application information:
General paths:
Config directory: /etc/icinga2
Data directory: /var/lib/icinga2
Log directory: /var/log/icinga2
Cache directory: /var/cache/icinga2
Spool directory: /var/spool/icinga2
Run directory: /run/icinga2
Old paths (deprecated):
Installation root: /usr
Sysconf directory: /etc
Run directory (base): /run
Local state directory: /var
Internal paths:
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /run/icinga2/icinga2.pid
Operating System and version:
CentOS Linux release 7.5.1804 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
CentOS Linux release 7.5.1804 (Core)
CentOS Linux release 7.5.1804 (Core)
If you run multiple Icinga 2 instances, the zones.conf file (or icinga2 object list --type Endpoint and icinga2 object list --type Zone) from all affected nodes.
object Endpoint "master1-local-domon.testing.mms-at-work.de" {
host = "master1-local-domon.testing.mms-at-work.de"
}
object Endpoint "master2-local-domon.testing.mms-at-work.de" {
host = "master2-local-domon.testing.mms-at-work.de"
}
object Zone "master" {
endpoints = [ "master1-local-domon.testing.mms-at-work.de", "master2-local-domon.testing.mms-at-work.de", ]
}
object Zone "director-global" {
global = true
}
object Zone "global-templates" {
global = true
}
The text was updated successfully, but these errors were encountered:
After Updating our Icinga Agents/Satellites to v2.10.0, we saw that it now appends the environment "production" to the SNI header on an TSL connection, even when environment is not set anywhere in the config.
Before v2.10.0, SNI was always like "master1-local-domon.testing.mms-at-work.de", with v2.10.0 it is now "master1-local-domon.testing.mms-at-work.de:production".
:production was new and broke our load balancing setup.
I think this came with #6512, but i dont know if its a bug or simply not mentioned in the upgradeing docs.
Your Environment
icinga2 --version
):icinga2 feature list
):zones.conf
file (oricinga2 object list --type Endpoint
andicinga2 object list --type Zone
) from all affected nodes.The text was updated successfully, but these errors were encountered: