Hello everyone,
Since 2026-11-16 10:41:28 UTC my Zabbix 8.0.0 server (Ubuntu 24.04, upgraded from 7.4.14
on 2026-11-06) creates no alerts at all - for any action. The action log is empty and the
alerts table has no row after alertid 1410. Events and problems are still created normally.
Already 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().
- media type enabled, user media active (severity 56), Admin is Super admin, actions
enabled with correct conditions, 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.
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.
One anomaly: the database is not the stock Zabbix schema - 299 foreign keys and no
AUTO_INCREMENT anywhere. INSERT INTO alerts failed with "ERROR 1364: Field 'alertid'
doesn't have a default value". After ALTER TABLE alerts MODIFY alertid bigint unsigned
NOT NULL AUTO_INCREMENT, a manual insert works, but alerts are still never created.
Questions:
1. Why does the alert manager receive no events while events are created in the database?
2. Do the "event processor thread stopped" messages indicate an abnormal termination, and
could they be the missing link between event creation and the alert manager?
3. Can a non-standard schema (FK constraints, missing AUTO_INCREMENT) break the event ->
alert path in 8.0?
Full logs, the FK list or a sanitized schema dump available on request. Thanks in advance.
Since 2026-11-16 10:41:28 UTC my Zabbix 8.0.0 server (Ubuntu 24.04, upgraded from 7.4.14
on 2026-11-06) creates no alerts at all - for any action. The action log is empty and the
alerts table has no row after alertid 1410. Events and problems are still created normally.
Already 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().
- media type enabled, user media active (severity 56), Admin is Super admin, actions
enabled with correct conditions, 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.
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.
One anomaly: the database is not the stock Zabbix schema - 299 foreign keys and no
AUTO_INCREMENT anywhere. INSERT INTO alerts failed with "ERROR 1364: Field 'alertid'
doesn't have a default value". After ALTER TABLE alerts MODIFY alertid bigint unsigned
NOT NULL AUTO_INCREMENT, a manual insert works, but alerts are still never created.
Questions:
1. Why does the alert manager receive no events while events are created in the database?
2. Do the "event processor thread stopped" messages indicate an abnormal termination, and
could they be the missing link between event creation and the alert manager?
3. Can a non-standard schema (FK constraints, missing AUTO_INCREMENT) break the event ->
alert path in 8.0?
Full logs, the FK list or a sanitized schema dump available on request. Thanks in advance.