Expected Behavior

The IDO MySQL feature is being turned on if requested during Debian package configuration.

Current Behavior

The IDO MySQL feature isn't being turned on.

Possible Solution

Turn it on if requested during Debian package configuration.

Steps to Reproduce (for bugs)

https://youtu.be/rZc8NPCT-as?t=767 (about one minute)

Context

#6766

Your Environment

The latest bleeding edge hipster stuff, see the Vagrantfile.

See Icinga/icinga2#6082

We have made changes to out init system but since we overwrite them in packaging we need to sync those changes here sigh

In spite of my ticket Icinga/icinga2#6484 in the main repo and the ticket #4 in this repo, the latest release still does not contain the WatchdogSeconds handling in the systemd unit.

Enabling it will ensure that a hanging Icinga will be restarted by systemd, because it did not ping the notification socket within the timeout:

WatchdogSec=5m

You can pick the appropriate timeout value.

Expected Behavior

Using the following lines

icinga2-ido-pgsql icinga2-ido-pgsql/dbconfig-install boolean false
icinga2-ido-pgsql icinga2-ido-pgsql/enable boolean false

by debconf-set-selections disables the configuration of the feature.

Current Behavior

Only on debian jessie: after the installation, configures still ask i.g. for a password to set. On debian stretch, ubuntu xenial and bionic works fine.

Formerly Icinga/icinga2#6082

Information from the original topic below. Thanks to @tmatthaeus for reporting this issue.
After a reload of icinga2 there is no icinga2 process via /etc/init.d/icinga2 reload there is no icinga2 process anymore.

OS: Debian 9.3
Icinga Version:

icinga2                                   2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 amd64
icinga2-bin                               2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 amd64
icinga2-common                            2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 all
icinga2-doc                               2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 all
icinga2-ido-mysql                         2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 amd64
libicinga2                                2.8.1+406.g407a2d052.2018.02.07+1.stretch-0 amd64

Debug Logfile output:

[2018-02-07 09:11:06 +0100] information/Application: Got reload command: Starting new instance.
[2018-02-07 09:11:06 +0100] notice/Process: Running command '/usr/lib/x86_64-linux-gnu/icinga2/sbin/icinga2' '--no-stack-rlimit' 'daemon' '-e' '/var/log/icinga2/error.log' '--reload-internal' '27264': PID 27446
[2018-02-07 09:11:07 +0100] debug/IdoMysqlConnection: Query: COMMIT
[2018-02-07 09:11:07 +0100] debug/IdoMysqlConnection: Query: BEGIN
[2018-02-07 09:11:07 +0100] information/Application: Reload requested, letting new process take over.

After that no output anymore and no icinga2 process is running anymore.

Steps to reproduce

1. Spin up a fresh Debian 9 system – either bare metal or fully virtualized
2. # wget -O - https://packages.icinga.com/icinga.key | apt-key add -

# cat <<EOF >>/etc/apt/sources.list
deb http://packages.icinga.com/debian icinga-stretch main
deb-src http://packages.icinga.com/debian icinga-stretch main
EOF

4. # apt update
5. # apt install icinga2-{bin,ido-mysql} mariadb-server
   • "Enable Icinga 2's ido-mysql feature?" – yes
   • "Configure database for icinga2-ido-mysql with dbconfig-common?" – yes
   • "MySQL application password for icinga2-ido-mysql:" – "123456"
   • "Password confirmation:" – "123456"
   • "Password of the database's administrative user:" (what for?) – ""

Result

"An error occurred while installing the database: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") . (...)"

Hi there,

I've just received the icinga2 r2.10.0-1 packages via packages.icinga.org and hit a nasty bug as far as I can see, as the service fails a restart after installing:

root@server:~# service icinga2 restart
Job for icinga2.service failed. See 'systemctl status icinga2.service' and 'journalctl -xn' for details.

this seems to be caused by either a wrong icinga2.service file for systemd or a missing file - don't know what the expected correct state is.

root@server:~# systemctl status icinga2.service
...
Oct 12 09:06:43 server systemd[1]: Failed to load environment files: No such file or directory
...

root@server:~# less /etc/systemd/system/multi-user.target.wants/icinga2.service
[Service]
Type=simple
UMask=0007
EnvironmentFile=/usr/lib/icinga2/icinga2

the above mentioned file does not exist, hence restarting/installing wil fail:

root@server:/usr/lib/icinga2# ls
prepare-dirs  safe-reload

Edit: Encountered only on Debian 8.