Ad Widget

Collapse

Zabbix database down after (system automatic?) update

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • gessel
    Junior Member
    • Mar 2017
    • 24

    #1

    Zabbix database down after (system automatic?) update

    I'm running the database appliance as a VM. I've been running it long enough to have updated it (successfully). Today I started getting the following errors via email alerts and was greeted with a nearly blank page from the web interface. There's one (of many) map available (unconfigured experiment), the status of zabbix pane has correct stats, saying that the server is running, that there are 437 hosts, 17774 items, 8890 triggers, etc. phpMyAdmin can log into the database and it looks healthy. However there's no other data visible from the web interface (everything is blank - just the UI.

    I got this alert: Zabbix database is down.

    Date Today 06:42
    Zabbix database is down.


    checking the logs, I see nothing remarkable except in the apt log:
    Start-Date: 2018-07-31 06:42:39
    Upgrade: mysql-server-core-5.5:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), mysql-server-5.5:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), mysql-client-core-5.5:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), mysql-client-5.5:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), mysql-common:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), libmysqlclient18:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1), mysql-server:amd64 (5.5.60-0ubuntu0.14.04.1, 5.5.61-0ubuntu0.14.04.1)
    End-Date: 2018-07-31 06:43:13

    AFAIK nobody was on a console at 06:42.39, last suggests this was the case.


    I followed http://www.michaelfoster82.co.uk/zab...abase-is-down/ to no avail (and no harm)

    I've backed up the database from phpMyAdmin just in case, but this is very odd. Any advice for getting zabbix to reconnect to the database?

    I've rebooted the server to no avail.
  • gessel
    Junior Member
    • Mar 2017
    • 24

    #2
    well.... strange, second reboot fixed it.

    Comment

    Working...