Icinga : docker restart=always not working

[jjethwa]

Icinga : docker restart=always not working

[jjethwa]

Hi @Quentinvarquet

Can you provide the docker log for the container? It should be named icinga

sudo docker logs icinga

Also, what are the contents for this file:

/run/containerd/9de1f2232f43f567c57574e46dee183cba4081bb078694112c1cbb668061405e

Thanks :)

[Quentinvarquet]

Hi @jjethwa thank you for your answer ! :-)

The logs of the container :

Now restart your Icinga 2 daemon to finish the installation!

information/base: Writing private key to '/etc/icinga2/pki/9de1f2232f43.key'.
information/base: Writing certificate signing request to '/etc/icinga2/pki/9de1f2232f43.csr'.
=>Finished cert generation
=>Initializing databases and icinga2 configurations.
=>This may take a few minutes
Starting MySQL database server: mysqld ..
Checking for tables which need an upgrade, are corrupt or were
not closed cleanly..
Stopping MySQL database server: mysqld.

MySQL user 'root' has no password but only allows local connections
MySQL user 'debian-sys-maint' password set to password
MySQL user 'icinga' password set to password
MySQL user 'icinga2-ido-mysq' password set to password
MySQL user 'icinga-web' password set to password
MySQL user 'icingaweb2' password set to password
MySQL user 'director' password set to password
Director API password set to 5bIb0c8vMEqUNS3

Icinga Web 2 (/icingaweb2) default credentials: icingaadmin:icinga

Starting Supervisor. You can safely CTRL-C and the container will continue to run with or without the -d (daemon) option
Starting Supervisor. You can safely CTRL-C and the container will continue to run with or without the -d (daemon) option
Unlinking stale socket /var/run/supervisor.sock

I think it's the firt time I see the line Unlinking stale socket /var/run/supervisor.sock

And now, the content of the folder 9de1f2232f43f567c57574e46dee183cba4081bb078694112c1cbb668061405e : (by the way, the ID of my icinga container is 9de1f2232f43, like the first letters of the folder)

• state.json
• init/

The content of the file state..json

{"bundle":"/var/run/docker/libcontainerd/9de1f2232f43f567c57574e46dee183cba4081bb078694112c1cbb668061405e","labels":null,"stdin":"","stdout":"","stderr":"","runtime":"docker-runc","runtimeArgs":[],"noPivotRoot":false}

The content of the folder init/ :

• control
• exit
• log.json
• pid
• process.json -> I checked inside, it's all informations about my icinga container : env variables, and some others informations about it
• shim-log.json

Really weird. In /run/containerd I only have this folder 9de1f2232f43f567c57574e46dee183cba4081bb078694112c1cbb668061405e

[jjethwa]

Thanks @Quentinvarquet

It looks like the icinga2 container was OK but containerd had an issue. The supervisor message about unlinking the stale socket should be fine. It's just cleaning up after a bad shutdown. You should try shutting down the containers before restarting the docker daemon next time.

Your issue might be related to this one: moby/moby#21702

[Quentinvarquet]

Yes it's seem to be the same. Just weird because the problem is only with my icinga container. All others restart good. I tried to do like if my Docker daemon had a big problem :-).
Thank you.

Tomorrow I will probably open another issue, it's just gonna be a question about a configuration

[jjethwa]

@Quentinvarquet No problem! I hope one of the solutions mentioned works for you. I think it was just bad luck :(

[Quentinvarquet]

I hope too ! I will try tomorrow, starting to be late in France :-)