Query failed:Table 'zabbix.escalation_log' doesn't exist

[rootlinux]

I upgraded from 1.1alpha5 to 1.1beta8 and I got the following error messages in /var/log/zabbix.log

015743:20060414:025024 Query::update escalation_log set status=1 where triggerid=12265 and status=0
015743:20060414:025024 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]
015743:20060414:025024 Query::update escalation_log set status=1 where triggerid=12266 and status=0
015743:20060414:025024 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]
015743:20060414:025025 Query::update escalation_log set status=1 where triggerid=12211 and status=0
015743:20060414:025025 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]
015743:20060414:025025 Query::update escalation_log set status=1 where triggerid=12212 and status=0
015743:20060414:025025 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]
015743:20060414:025026 Query::update escalation_log set status=1 where triggerid=12255 and status=0
015743:20060414:025026 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]


How can I solve it?

Rgds,
rootlinux

[markpr]

That's a big jump between releases - did you run all the db update scripts for each incremental release between A5 and B8 ?

Given the amount of changes between those releases, plus the new templating system & and feature freeze close to this 1.1 release - I would look at a fresh installation if I were you (When I upgraded from A10 to B5 I did this).

Figure out the new templates on a fresh installation with B8 and then when B9 is released (hopefully with a fixed bulkloader) perform a bulkload of all your devices again. At least this is my plan for B8 and B9 (I'm on B6 at the moment).

Mark

[rootlinux]

I did all the db upgrade from A5 to B8

[btriem]

New installation

I am seeing these same messages repeated over and over. I did not upgrade, but did a new installation of the latest beta release.

013570:20060425:084010 Query::update escalation_log set status=1 where triggerid=12367 and status=0013570:20060425:084010 Query failed:Table 'zabbix.escalation_log' doesn't exist [1146]

the mysql create script only contains history_log, but no escalation_log.

[jhiatt]

The sql file that creates the tables seems to be missing the escalation ones. I found them in the 1.1beta8 release. I just copied out the escalation tables and made a new sql file with them, and then added them into the database.


Hope that helps.


Jason

[smokey]

the missing definitions

Here are the missing table definitions in 1.1beta9's mysql schema.sql. Gotten by diff'ing create/mysql/schema.sql for beta8 and beta9.

--
-- Table structure for table 'escalations'
--

CREATE TABLE escalations (
  escalationid          int(4)          NOT NULL auto_increment,
  name                  varchar(64)     DEFAULT '0' NOT NULL,
  dflt                  int(2)          DEFAULT '0' NOT NULL,
  PRIMARY KEY (escalationid),
  UNIQUE (name)
) type=InnoDB;

--
-- Table structure for table 'escalation_rules'
--

CREATE TABLE escalation_rules (
  escalationruleid      int(4)          NOT NULL auto_increment,
  escalationid          int(4)          DEFAULT '0' NOT NULL,
  level                 int(4)          DEFAULT '0' NOT NULL,
  period                varchar(100)    DEFAULT '1-7,00:00-23:59' NOT NULL,
  delay                 int(4)          DEFAULT '0' NOT NULL,
  actiontype            int(4)          DEFAULT '0' NOT NULL,
  PRIMARY KEY (escalationruleid),
  KEY (escalationid)
) type=InnoDB;

--
-- Table structure for table 'escalation_log'
--

CREATE TABLE escalation_log (
  escalationlogid       int(4)          NOT NULL auto_increment,
  triggerid             int(4)          DEFAULT '0' NOT NULL,
  alarmid               int(4)          DEFAULT '0' NOT NULL,
  escalationid          int(4)          DEFAULT '0' NOT NULL,
  actiontype            int(4)          DEFAULT '0' NOT NULL,
  level                 int(4)          DEFAULT '0' NOT NULL,
  adminlevel            int(4)          DEFAULT '0' NOT NULL,
  nextcheck             int(4)          DEFAULT '0' NOT NULL,
  status                int(4)          DEFAULT '0' NOT NULL,
  PRIMARY KEY (escalationlogid),
  KEY (alarmid,escalationid),
  KEY (triggerid)
) type=InnoDB;

Hopefully this saves someone 2 minutes.

[Alexei]

Here are the missing table definitions in 1.1beta9's mysql schema.sql. Gotten by diff'ing create/mysql/schema.sql for beta8 and beta9.

All escalations* tables are not used since 1.1beta9 anymore. Ignore this patch!

[gbaratto]

> Here are the missing table definitions in 1.1beta9's mysql schema.sql. Gotten by diff'ing create/mysql/schema.sql for beta8 and beta9.

But I was getting this error msg with a fresh install of 1.1beta9, as well... any ideas?

[Alexei]

But I was getting this error msg with a fresh install of 1.1beta9, as well... any ideas?

Indeed! There are several unnecessary references to the escalation tables in the ZABBIX sources. Will be fixed in 1.1beta10.

Meanwhile you may ignore the warning messages.

[rootlinux]

Thank you all...I will download the latest 1.1beta10 and test it.

[rootlinux]

I upgraded my Zabbix 1.1beta8 to 1.1beta10 and the escalation error has gone...