How to add logger tables: Difference between revisions
Line 6: | Line 6: | ||
==Problem== | ==Problem== | ||
Zimbra includes the logger service, that collects data from different servers for the state of the different services. If multiserver installation is in place, there must be only one logger server, and the rest of the server are viewed as clients. Each client and the logger server keep a database for the known servers in the setup, placed in SQLite3 database. Sometimes, due to power outage or different reasons, | Zimbra includes the logger service, that collects data from different servers for the state of the different services. If multiserver installation is in place, there must be only one logger server, and the rest of the server are viewed as clients. Each client and the logger server keep a database for the known servers in the setup, placed in SQLite3 database. Sometimes, due to power outage or different reasons, one or more tables might be missing. In this wiki we will see how to recreate tables from the logger DB. | ||
==Resolution== | ==Resolution== | ||
1. Enter the | 1. Enter the SQLite3 database: | ||
$ sqlite3 /opt/zimbra/logger/db/data/logger.sqlitedb | $ sqlite3 /opt/zimbra/logger/db/data/logger.sqlitedb | ||
2. Once inside confirm which tables exist: | 2. Once inside confirm which tables exist: | ||
sqlite> .tables | sqlite> .tables | ||
'''config hosts rrd_column_type rrds''' | |||
3. If tables are missing, recreate them with the following lines. For each table, | 3. If tables are missing, recreate them with the following lines. For each table, copy and paste the text to the sqlite command line: | ||
CREATE TABLE hosts ( | CREATE TABLE '''hosts''' ( | ||
id INTEGER PRIMARY KEY, | id INTEGER PRIMARY KEY, | ||
dns_hostname VARCHAR(255) NOT NULL UNIQUE, | dns_hostname VARCHAR(255) NOT NULL UNIQUE, | ||
Line 25: | Line 28: | ||
CREATE TABLE config ( | CREATE TABLE '''config''' ( | ||
version INTEGER NOT NULL UNIQUE | version INTEGER NOT NULL UNIQUE | ||
); | ); | ||
CREATE TABLE rrds ( | CREATE TABLE '''rrds''' ( | ||
id INTEGER PRIMARY KEY, | id INTEGER PRIMARY KEY, | ||
host_id INTEGER NOT NULL REFERENCES hosts(id) ON DELETE CASCADE, | host_id INTEGER NOT NULL REFERENCES hosts(id) ON DELETE CASCADE, | ||
Line 41: | Line 44: | ||
CREATE TABLE rrd_column_type ( | CREATE TABLE '''rrd_column_type''' ( | ||
csv_file varchar(255) not null, | csv_file varchar(255) not null, | ||
col_name varchar(255) not null, | col_name varchar(255) not null, | ||
Line 49: | Line 52: | ||
CONSTRAINT unqcoltype UNIQUE (csv_file, col_name) | CONSTRAINT unqcoltype UNIQUE (csv_file, col_name) | ||
); | ); | ||
Exit the db with: | |||
.quit | |||
Line 59: | Line 66: | ||
/opt/zimbra/bin/zmloggerhostmap -d server1. domain.com server1. domain.com | /opt/zimbra/bin/zmloggerhostmap -d server1. domain.com server1. domain.com | ||
The hostmap rely on | The hostmap rely on correct values set in the hosts file, DNS and the zimbra hostname. You need to make sure all is correct for proper functioning. | ||
Revision as of 13:00, 1 October 2019
How to add logger tables
Problem
Zimbra includes the logger service, that collects data from different servers for the state of the different services. If multiserver installation is in place, there must be only one logger server, and the rest of the server are viewed as clients. Each client and the logger server keep a database for the known servers in the setup, placed in SQLite3 database. Sometimes, due to power outage or different reasons, one or more tables might be missing. In this wiki we will see how to recreate tables from the logger DB.
Resolution
1. Enter the SQLite3 database:
$ sqlite3 /opt/zimbra/logger/db/data/logger.sqlitedb
2. Once inside confirm which tables exist:
sqlite> .tables config hosts rrd_column_type rrds
3. If tables are missing, recreate them with the following lines. For each table, copy and paste the text to the sqlite command line:
CREATE TABLE hosts ( id INTEGER PRIMARY KEY, dns_hostname VARCHAR(255) NOT NULL UNIQUE, zm_hostname VARCHAR(255) );
CREATE TABLE config ( version INTEGER NOT NULL UNIQUE );
CREATE TABLE rrds ( id INTEGER PRIMARY KEY, host_id INTEGER NOT NULL REFERENCES hosts(id) ON DELETE CASCADE, col_name VARCHAR(255) NOT NULL, col_name_19 VARCHAR(20) NOT NULL, -- due to rrd 19 char limit col_num INTEGER NOT NULL, csv_file VARCHAR(255) NOT NULL, rrd_file INTEGER NOT NULL DEFAULT 0 );
CREATE TABLE rrd_column_type ( csv_file varchar(255) not null, col_name varchar(255) not null, -- G-AUGE, C-OUNTER, A-BSOLUTE or D-ERIVED col_type char(1) not null, col_interval integer, col_unit varchar(64), CONSTRAINT unqcoltype UNIQUE (csv_file, col_name) );
Exit the db with:
.quit
4. Once recreated you can populate them with the /opt/zimbra/bin/zmloggerhostmap command line tool.
To add mapping use the -a switch at the end as follows:
/opt/zimbra/bin/zmloggerhostmap -a server1. domain.com server1. domain.com
To delete use -d switch:
/opt/zimbra/bin/zmloggerhostmap -d server1. domain.com server1. domain.com
The hostmap rely on correct values set in the hosts file, DNS and the zimbra hostname. You need to make sure all is correct for proper functioning.