Uppercase in agent name running on Windows server

Icinga 2
, , ,
1

Hello,

I have an error on an agent deployed on a Windows 2022 server. Agent version: 2.14.3. A similar server has been deployed with the agent no later than last week, with no issue. I do not understand what could be the issue with this server.

The issue seems to be related with uppercase/lowercase. I wish the server to be known in Icinga as “MYSERVER.my.fqdn”. However, for some reason, Icinga looks for “myserver.my.fqdn.crt” and “myserver.my.fqdn.key”. The directory exists but the file names are “MYSERVER.my.fqdn.crt” and “MYSERVER.my.fqdn.key”.

Thank you for your help,

Jean

Here the output of the configuration validation:

C:\Program Files\ICINGA2\sbin>icinga2.exe daemon -C
[2025-02-13 10:19:27 +0100] information/cli: Icinga application loader (version: v2.14.3)
[2025-02-13 10:19:27 +0100] information/cli: Loading configuration file(s).
[2025-02-13 10:19:27 +0100] information/ConfigItem: Committing config item(s).
[2025-02-13 10:19:27 +0100] information/ApiListener: My API identity: MYSERVER.my.fqdn
[2025-02-13 10:19:28 +0100] critical/SSL: Error with private key file 'C:\ProgramData\icinga2\var\lib\icinga2/certs//myserver.my.fqdn.key': 2147483650, "error:80000002:system library::No such file or directory"
[2025-02-13 10:19:28 +0100] critical/config: Error: Cannot make SSL context for cert path: 'C:\ProgramData\icinga2\var\lib\icinga2/certs//myserver.my.fqdn.crt' key path: 'C:\ProgramData\icinga2\var\lib\icinga2/certs//myserver.my.fqdn.key' ca path: 'C:\ProgramData\icinga2\var\lib\icinga2/certs//ca.crt'.
Location: in C:\ProgramData\icinga2\etc\icinga2/icinga2.conf: 63:1-63:24
C:\ProgramData\icinga2\etc\icinga2/icinga2.conf(61): }
C:\ProgramData\icinga2\etc\icinga2/icinga2.conf(62):
C:\ProgramData\icinga2\etc\icinga2/icinga2.conf(63): object ApiListener "api" {
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^
C:\ProgramData\icinga2\etc\icinga2/icinga2.conf(64):  accept_commands = true
C:\ProgramData\icinga2\etc\icinga2/icinga2.conf(65):  accept_config = true
[2025-02-13 10:19:28 +0100] critical/config: 1 error
[2025-02-13 10:19:28 +0100] critical/cli: Config validation failed. Re-run with 'icinga2 daemon -C' after fixing the config.
2

The issue was worked around by adding the following line to constants.conf:

const NodeName = "MYSERVER.my.fqdn"

Previously the NodeName constant had no value explicitly defined in constants.conf.

I am still unsure why this workaround is needed on this particular server and not on others.