based on user reports and queries over the last 24 hours
Zabbix outage statistics
-Check if database services like MySQL or PostgreSQL are up and running.
-Review the server log at /var/log/zabbix/zabbix_server.log for clues on what went wrong.
-Try restarting with systemctl restart zabbix-server or the equivalent for your setup.
-Make sure your browser isn''t clogged with old cache; clear it out.
-Test from another device or browser to rule out local glitches.
-Reduce widgets or items shown to lighten the load.
-Double-check your username and password haven''t changed.
-Ensure PHP session settings allow cookies properly.
-Look at Apache or Nginx logs for auth failures.
-Verify the agent config file has the right ServerActive pointing to your host.
-Ping the server from the agent machine to confirm connectivity.
-Restart agent with systemctl restart zabbix-agent.
-Check if items are enabled and have correct keys.
-Run the housekeeper process manually if it''s lagging.
-Use zabbix_get utility to fetch a test value.
-Examine the trigger expression for typos or bad functions.
-Confirm enough history periods are kept in trends.
-Test by simulating the condition in the frontend.
-Tune network interfaces or switch to bulk data sending.
-Increase queue size in server config if overwhelmed.
-Check for proxy bottlenecks if distributed setup.
-Validate media configs like SMTP for email.
-Ensure user has correct media linked and enabled.
-Run a test notification from user settings.
-Boost max connections in DB config.
-Run vacuum or optimize on tables regularly.
-Monitor DB logs for deadlocks or overflows.
Zabbix
Your message will be published in about
5 minutes
Service administration will see your message