[dev.icinga.com #11740] .conf file will remain in apifolder if the zonesfolder in zones.d is removed or the last .conf-file is removed from /zones.d/zonefolder.

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11740

Created by rafael.voss on 2016-05-08 09:47:14 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-18 14:08:56 +00:00 (in Redmine)

Icinga Version: 2.4.7
Backport?: Not yet backported
Include in Changelog: 1

---

As long there is more than one conf file in the zonefolder there is no problem, but if there is only one .conf-file in a zonefolder in /etc/icinga2/zones.d and this file is deleted (folder is empty now), the .conf-file will remain in the api folder in /var/lib/icinga2/api/zones/.

I have the same problem when i delete the entire zonefolder in zones.d.

i use the debmon packages on Debian Jessi.

As a workaround i have placed a dummy.conf with no content in the zonefolder.

---

Relations:

• relates #10000

[icinga-migration]

Updated by rafael.voss on 2016-07-08 07:41:49 +00:00

To recreate this bug:

1. Create a new zone,endpoint
2. mkdir etc/icinga2/zones.d/zonename
3. copy a working .conf file into etc/icinga2/zones.d/zonename/
4. reload icinga
5. remove the conf file
6. reload icinga

the conf file will remain in /var/lib/icinga2/api/zones/zonename/_etc/filename.conf

The problem: the master will not use this file in configchecks as its not in zones.d anymore, but it will transfer this file to the zones. As result the zone executes the checks, but you will not find these checks in your configs on the master. And finally its possible to create new checks with same names somewhere else without hitting a config error.

If you follow the steps again, but create/copy 2 .conf files into the zonename directory all will work as expected.

[icinga-migration]

Updated by mfriedrich on 2016-11-18 14:08:48 +00:00

• Relates set to 10000

[icinga-migration]

Updated by mfriedrich on 2016-11-18 14:08:56 +00:00

• Category set to Cluster

[NeverUsedID]

Looks like this bug still exists in 2.8.0

Just moved the last .conf file from one global zone to another. ALL Icinga2 agents failed to reload, because now the command "is predefined" in both zones. To solve this, a simple "touch dummy.conf" in the "empty" old zone at the master, followed by a reload solved the problem.

[Al2Klimov]

@NeverUsedID What about v2.10.2?

[dnsmichi]

I will deal with this as part of #6716.

[dnsmichi]

I'm closing this in favor of #6716.