I cannot syslog messages from an Icinga2 podman container

  • Version used (icinga2 --version): r2.13.6-1
  • Operating System and version: Linux CentOS7
  • Enabled features (icinga2 feature list): api checker command ido-mysql influxdb mainlog notification syslog


I am running icinga2 in a custom podman container (Centos7-based image) running on RHEL9 platform.
Regarding Icinga everything works like a charm (including Icingaweb2 running from a separate container, same image).

The points is that I can send syslog messages from container instance (for instance using the command ‘logger’) only when Icinga2 is not running. Trying logger message from the container running Icinga2 has no error but does not send anything.

It looks like Icinga2 is blocking (redirecting, …?) syslog somehow.
May the standard option ‘–close-stdio’ the culprit?

Would appreciate a lot your help here!
Thank you in advance

Would it be possible having an answer to this request? … at least just confirmed it’s well received and in the pipeline?

I’m not quite sure what you mean by “pipeline”.

This is not a ticket-based support service - this is a community forum where
people can ask questions and if others feel able to help, there may be

If nobody else is doing something similar to what you’re doing, or if nobody
has run into the problems you’re encountering, then you may simply not get a
reply, because nobody thinks they have anything useful to say.


1 Like

Thank you Antony, It’s clear for me now.
Sorry but i thought it was a ticket-based support.

I will try to reformulate my question if by chance someone better understands my issue. and can help.