Windows Client (Icinga2-v2.10.0-x86_64.msi) missing InitRunDir - icinga2.pid ends up on root of C:\ (if permissions allow) otherwise fails to start

JohnZ-H commented 6 years ago

Expected Behavior

Windows client (when run by service control manager) starts

Current Behavior

Windows client (when run by service control manager) fails to start

Possible Solution

It seems from the debug logs as though the initrundir for the packaged windows client is unset

[2018-10-12 14:26:51 +0100] critical/Application: Could not open PID file '/icinga2.pid'. ... [2018-10-12 14:26:51 +0100] critical/Application: Cannot update PID file '/icinga2.pid'. Aborting.

Steps to Reproduce (for bugs)

Install client with no additional config
Try and start it via windows service control manager

Context

We can't update to this version if we want to continue to monitor

Your Environment

Version used (icinga2 --version): icinga2.exe - The Icinga 2 network monitoring daemon (version: v2.10.0)
Operating System and version: windows10 (also server 2012r2)
Enabled features (icinga2 feature list): Disabled features: api command compatlog gelf graphite ido-mysql ido-pgsql influxdb livestatus opentsdb perfdata statusdata Enabled features: checker debuglog mainlog notification
Icinga Web 2 version and modules (System - About): n/a
Config validation (icinga2 daemon -C): [2018-10-12 14:40:10 +0100] information/cli: Icinga application loader (version: v2.10.0) [2018-10-12 14:40:10 +0100] information/cli: Loading configuration file(s). [2018-10-12 14:40:11 +0100] information/ConfigItem: Committing config item(s). [2018-10-12 14:40:11 +0100] warning/ApplyRule: Apply rule 'satellite-host' (in C:\ProgramData\icinga2\etc\icinga2/conf.d/satellite.conf: 29:1-29:41) for type 'Dependency' does not match anywhere! [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 CheckerComponent. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 NotificationComponent. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 User. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 Host. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 2 NotificationCommands. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 9 Services. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 3 TimePeriods. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 ScheduledDowntime. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 UserGroup. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 Endpoint. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 Zone. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 10 Notifications. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 Downtime. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 2 HostGroups. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 1 IcingaApplication. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 2 FileLoggers. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 215 CheckCommands. [2018-10-12 14:40:11 +0100] information/ConfigItem: Instantiated 3 ServiceGroups. [2018-10-12 14:40:11 +0100] information/ScriptGlobal: Dumping variables to file 'C:\ProgramData\icinga2\var\cache\icinga2/icinga2.vars' [2018-10-12 14:40:11 +0100] information/cli: Finished validating the configuration file(s).
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. single instance

JohnZ-H commented 6 years ago

Looks to be fixed in snapshot as per #6677 (of which this seems to be a duplicate)

mcktr commented 6 years ago

I'm closing here in favor of #6677.

Icinga / icinga2