Icinga Notifications: Establishing an Event Stream API connection failed, will be retried

Icinga 2
1

Hi,

I installed Icinga2 in Fedora 41 (v2.15.0-1) - It has only one Master - no Agent - No Satellite

I definitively cannot raise up Notifications feature. It tells this error:

ago 21 09:04:26 srvicinga-mt icinga-notifications[117365]: runtime-updates: Applied configuration updates
ago 21 09:04:26 srvicinga-mt icinga-notifications[117365]: incident: Loading all active incidents from database
ago 21 09:04:26 srvicinga-mt icinga-notifications[117365]: listener: Starting listener on http://localhost:5680
ago 21 09:04:26 srvicinga-mt systemd[1]: Started icinga-notifications.service - Icinga Notifications.
ago 21 09:04:26 srvicinga-mt icinga-notifications[117365]: channel: Successfully started channel plugin
ago 21 09:04:26 srvicinga-mt icinga-notifications[117365]: icinga2: Establishing an Event Stream API connection failed, will be retried
ago 21 09:04:27 srvicinga-mt icinga-notifications[117365]: icinga2: Establishing an Event Stream API connection failed, will be retried
ago 21 09:04:29 srvicinga-mt icinga-notifications[117365]: icinga2: Establishing an Event Stream API connection failed, will be retried
ago 21 09:04:33 srvicinga-mt icinga-notifications[117365]: icinga2: Establishing an Event Stream API connection failed, will be retried
ago 21 09:04:41 srvicinga-mt icinga-notifications[117365]: icinga2: Establishing an Event Stream API connection failed, will be retried

At the icinga2 side:

● icinga2.service - Icinga host/service/network monitoring system
     Loaded: loaded (/usr/lib/systemd/system/icinga2.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
             /etc/systemd/system/icinga2.service.d
             └─limits.conf
     Active: active (running) since Thu 2025-08-21 08:52:56 -04; 22min ago
 Invocation: 20efbd2fbdc3468a8d2e7ef4965c842d
   Main PID: 107864 (icinga2)
     Status: "Startup finished."
      Tasks: 64
     Memory: 42.2M (peak: 56.5M)
        CPU: 1min 2.216s
     CGroup: /system.slice/icinga2.service
             ├─107864 /usr/lib64/icinga2/sbin/icinga2 --no-stack-rlimit daemon --close-stdio -e /var/log/icinga2/error.log
             ├─107898 /usr/lib64/icinga2/sbin/icinga2 --no-stack-rlimit daemon --close-stdio -e /var/log/icinga2/error.log
             └─107915 /usr/lib64/icinga2/sbin/icinga2 --no-stack-rlimit daemon --close-stdio -e /var/log/icinga2/error.log

ago 21 09:04:27 srvicinga-mt icinga2[107898]: Client TLS handshake failed (from [::ffff:127.0.0.1]:54148): packet length too long (SSL routines)
ago 21 09:04:29 srvicinga-mt icinga2[107898]: Client TLS handshake failed (from [::ffff:127.0.0.1]:54160): packet length too long (SSL routines)
ago 21 09:04:33 srvicinga-mt icinga2[107898]: Client TLS handshake failed (from [::ffff:127.0.0.1]:54166): packet length too long (SSL routines)
ago 21 09:04:41 srvicinga-mt icinga2[107898]: Client TLS handshake failed (from [::ffff:127.0.0.1]:39872): packet length too long (SSL routines)

this command curl -k -u notificador:ici -H 'Accept: application/json' https://127.0.0.1:5665/v1/status doesn’t give error message
but this command openssl s_client -connect 127.0.0.1:5665 -CAfile /var/lib/icinga2/certs/ca.crt
gives this kind of error (final lines):

read R BLOCK

HTTP/1.1 400 Bad Request
Server: Icinga/r2.15.0-1
Content-Type: text/html
Content-Length: 48
Connection: close

<h1>Bad Request</h1><p><pre>bad method</pre></p>closed
  • Icinga Web 2 version 2.12.5
  • Monitoring: 2.12.5
  • Notifications: 0.1.0
  • Icinga 2 version used (icinga2 --version) r2.15.0-1
  • PHP version used 8.3.24
  • Server operating system and version - Fedora 41
2

The Icinga Notifications logs contain more information, but are hidden in the default journald configuration. Please read the Systemd Journald Fields section and post the relevant logs[1].

Please paste the Icinga 2 ApiUser configuration for the Icinga Notifications user and show the source configuration from Icinga Notifications Web - either as a screenshot from Icinga Notifications Web or by querying the sources SQL table. Passwords can be redacted :slight_smile:

This is fine. You are establishing a TLS connection but do not speak HTTP within.

  1. For the record: Since hiding error information is not the expected behavior, this was changed in version 0.7.0 of our internal Go library, #126. This change has already landed in the recent Icinga DB release and will be available in the next Icinga Notifications release. ↩︎