Title:
Zabbix 8.0.0 — no alerts are created at all: alert manager receives no events (updated 2026-11-19)
Hello everyone,
Zabbix 8.0.0 on Ubuntu 24.04, upgraded from 7.4.14 on 2026-11-06.
Since 2026-11-16 10:41:28 UTC, no alerts are created at all, for any action.
The action log is empty and the alerts table has no new automatic row after alertid 1410.
Events and problems are still created normally.
What I have checked:
- alert manager, escalator and alert syncer are alive, 0% busy.
- At LogLevel 4, the alert manager only logs "select null" every 60 s and receives no event at all.
- The escalator only runs process_escalations() and processes 0 escalations.
- Media type enabled, user media active (severity 56), Admin is Super admin.
- Actions enabled, conditions correct, no maintenance, no CEP rules, events not suppressed.
- CHECK TABLE alerts OK; no lock in SHOW PROCESSLIST.
- config_cache_reload and two service restarts: no change.
- A brand-new action with no conditions produced nothing.
- Another new action (host + severity >= 3) produced nothing for 4 real events.
- The proxies (7.4.11 at the time) have since been migrated to 8.0.0: unchanged.
- A manual Telegram media-type test works: the message is received. The media/token is therefore not the problem.
- Database version:
dbversionid 1, mandatory 8000000, optional 8000000
Important new evidence:
- Escalations ARE created, but alerts stays empty.
Example:
eventid 12323802
actionid 11
escalationid 444
status 2
No row in alerts for this eventid.
- alert manager still reports "sent 0, failed 0".
- SHOW ENGINE INNODB STATUS shows neither a foreign-key error nor a deadlock.
So MySQL is not rejecting the insert: the alert manager does not even attempt it.
Schema comparison:
- I compared the live schema with the official 8.0 schema
(/usr/share/zabbix/sql-scripts/mysql/server.sql.gz).
- 230 tables in both, no missing table, no extra table.
- No AUTO_INCREMENT expected by the official schema is missing.
- The FK constraints on alerts (c_alerts_1..6) are present in the official schema.
- The schema therefore does not appear to be incomplete.
Recurring in the log at every start:
"[event processor #10] thread stopped", then #9, #8...
at roughly 5 min 14 s intervals, leaving only #1 and #2 alive.
Questions:
1. Why does the alert manager receive no events while events are still created in the database?
2. Are the "event processor thread stopped" messages an abnormal termination, and could they be the missing link between event creation and the alert manager?
3. Is this a known issue in Zabbix 8.0.0, or a corrupt internal state after the 7.4.14 -> 8.0.0 upgrade?
4. What would be the safe way to repair the event -> escalation -> alert pipeline without restoring the official schema over the existing database?
Full logs and a sanitized schema dump are available on request.
Thanks in advance.
Zabbix 8.0.0 — no alerts are created at all: alert manager receives no events (updated 2026-11-19)
Hello everyone,
Zabbix 8.0.0 on Ubuntu 24.04, upgraded from 7.4.14 on 2026-11-06.
Since 2026-11-16 10:41:28 UTC, no alerts are created at all, for any action.
The action log is empty and the alerts table has no new automatic row after alertid 1410.
Events and problems are still created normally.
What I have checked:
- alert manager, escalator and alert syncer are alive, 0% busy.
- At LogLevel 4, the alert manager only logs "select null" every 60 s and receives no event at all.
- The escalator only runs process_escalations() and processes 0 escalations.
- Media type enabled, user media active (severity 56), Admin is Super admin.
- Actions enabled, conditions correct, no maintenance, no CEP rules, events not suppressed.
- CHECK TABLE alerts OK; no lock in SHOW PROCESSLIST.
- config_cache_reload and two service restarts: no change.
- A brand-new action with no conditions produced nothing.
- Another new action (host + severity >= 3) produced nothing for 4 real events.
- The proxies (7.4.11 at the time) have since been migrated to 8.0.0: unchanged.
- A manual Telegram media-type test works: the message is received. The media/token is therefore not the problem.
- Database version:
dbversionid 1, mandatory 8000000, optional 8000000
Important new evidence:
- Escalations ARE created, but alerts stays empty.
Example:
eventid 12323802
actionid 11
escalationid 444
status 2
No row in alerts for this eventid.
- alert manager still reports "sent 0, failed 0".
- SHOW ENGINE INNODB STATUS shows neither a foreign-key error nor a deadlock.
So MySQL is not rejecting the insert: the alert manager does not even attempt it.
Schema comparison:
- I compared the live schema with the official 8.0 schema
(/usr/share/zabbix/sql-scripts/mysql/server.sql.gz).
- 230 tables in both, no missing table, no extra table.
- No AUTO_INCREMENT expected by the official schema is missing.
- The FK constraints on alerts (c_alerts_1..6) are present in the official schema.
- The schema therefore does not appear to be incomplete.
Recurring in the log at every start:
"[event processor #10] thread stopped", then #9, #8...
at roughly 5 min 14 s intervals, leaving only #1 and #2 alive.
Questions:
1. Why does the alert manager receive no events while events are still created in the database?
2. Are the "event processor thread stopped" messages an abnormal termination, and could they be the missing link between event creation and the alert manager?
3. Is this a known issue in Zabbix 8.0.0, or a corrupt internal state after the 7.4.14 -> 8.0.0 upgrade?
4. What would be the safe way to repair the event -> escalation -> alert pipeline without restoring the official schema over the existing database?
Full logs and a sanitized schema dump are available on request.
Thanks in advance.
Comment