Icinga Director Background Service without systemd?

Hello everybody
Due to another problem (Apply hostgroups in director didn’t work)
I wanted to upgrade the director to the current version.
For this you need the Icinga Director Background Service.

My installation is running without systemd:
Is there a template for initialization with the previous init.d system?

Best regards
josh

Hi,

which distribution are you using that Systemd is not available there?

I’d say that one could create an init.d file from other application examples with just invoking the required Director commands done in the systemd service file.

Cheers,
Michael

Hello Michael.

Thx for your reply.
In the concrete case it is a longer story. The customer does not want native Linux in his network.
Now you might ask why he wants to have Icinga at all. The answer is: he does not want it, but he has to take it because his boss decided it that way.
So I’ve been developing a scenario on 3 Windows 2019 servers with WSL for several months (even HA, etc.). In WSL there is no systemd.

I thought there was already a solution. Especially since there are also Distributions like Devuan (and I myself am not really convinced of systemd.) Then I have to actually try it myself to build.

Thanks and regards
josh

Remark: Im using Ubuntu 18.04. in the WSL

Devuan is a great replacement for Debian if you want GNU/Linux instead of
Systemd.

To the Icinga2 developers: please don’t drop support for sysvinit.

Thanks,

Antony.

I’m not a friend of those systemd vs sysvinit discussions, so please leave them away in favor of finding a solution.

In terms of sysvinit support, you also might want to open a feature request in the Director project if not already existing. For a quick solution, you might want to look into other tools/scripts how they do it, and copy the ExecStart line from the Director. Maybe it works, maybe not.

Cheers,
Michael

I’m not a friend of those systemd vs sysvinit discussions, so please leave
them away in favor of finding a solution.

I wasn’t trying to have any systemd vs. sysvinit “discussion” - the original
poster said that he’s working on machines without systemd, and also said that
he’s not convinced about it, so I wanted to suggest to developers that there
are also other people who would like to see sysvinit support maintained.

There dosen’t have to be a debate about the topic just because it might be a
good idea to maintain end-user choice about how their systems run.

Why abandon something that already exists, and some people continue to want?

In terms of sysvinit support, you also might want to open a feature request
in the Director project if not already existing.

Thanks - where do I find that?

For a quick solution, you might want to look into other tools/scripts how
they do it, and copy the ExecStart line from the Director. Maybe it works,
maybe not.

Is it so hard for the official Icinga2 installer to support both systemd and
non-systemd distributions? I would far prefer to be using an officially-
distributed startup script than something else I’ve found and implemented
myself, in the hope that it works (but with no guarantee from the Icinga
team).

Antony.

I’m not sure where you are heading here … the Director daemon is new in 1.7 and has a new systemd service file introduced in the source code. No-one removed something which existed before.

On GitHub, where all of our development happens including issue tracking.

There is no such thing called “icinga2 installer”. Each product has its own package, and provides the necessary configuration files to actually run it. Be it apache config for Icinga Web, Systemd service files for Icinga 2, etc. And yes, it is hard to maintain everything and test everything prior to a release. I’d rather only use one init system than 3 different ones.

As said, this was for a quick solution if you really need it. I fairly doubt that someone from us will jump right in and create a sysvinit file for you to use. If you want, you can also look into this and help @Josh out.

Cheers,
Michael

Why abandon something that already exists, and some people continue to
want?

I’m not sure where you are heading here … the Director daemon is new in
1.7 and has a new systemd service file introduced in the source code.
No-one removed something which existed before.

Sorry, I did not realise that.

I read the original comment “I wanted to upgrade the director to the current
version.” and assumed that this meant there was a previous version of the
(now) systemd-only startup script.

Apologies for the misinterpretation.

Is it so hard for the official Icinga2 installer to support both systemd
and non-systemd distributions?

There is no such thing called “icinga2 installer”. Each product has its own
package, and provides the necessary configuration files to actually run
it.

Okay, so there are several “Icinga2 installers”, or packages providing the
necessary startup files if you prefer. Bad phrasing on my part.

Be it apache config for Icinga Web, Systemd service files for Icinga
2, etc. And yes, it is hard to maintain everything and test everything
prior to a release. I’d rather only use one init system than 3 different
ones.

I can understand a preference for keeping things simple, but I simply wanted
to point out that there might be some noticeable proportion of your userbase
who want (or need) to continue using sysvinit.

If the Icinga team decides at some point that this is not a sufficient
proportion to continue supporting it, so be it, but I’d rather make the
request than go unnoticed.

As said, this was for a quick solution if you really need it. I fairly
doubt that someone from us will jump right in and create a sysvinit file
for you to use.

Again, apologies - I did not realise that this was something new which has
never previously had a sysvinit script for it.

If you want, you can also look into this and help @Josh out.

Sure, I’ll see how much the service file differs from others which have sysvinit
equivalents.

Thanks for the overall clarification - that’s useful.

Regards,

Antony.

Good evening everyone.

Sorry that I’m writing now, but I was on vacation for a week.

Thank you Michi for your explanations. If it is not intended, I will try to implement it somehow in sysinit.

If this reads someone who has already done it I ask for an info.

greetings
Josh