See the installation_from_source section for full details.
Older agents from Zabbix 1.0, Zabbix 1.1.x, Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix 1.8. It does not require any configuration changes on agent side.
Listener failed with error: socket() for [[(null)]:10051] failed with error 97: Address family not supported by protocol.
socket() for [[-]:10050] failed with error 22: Invalid argument
The shutdown upon detection of duplicate hosts, introduced in 1.8.8, has been removed.
Accepted data limit of 128MB was introduced when using Zabbix protocol. Any other data (including older Zabbix protocols) stays limited at 16MB.
Zabbix server now correctly enables SSL host verification when using Ez Texting service to send alerts.
If Zabbix is logging to syslog then after an upgrade to Zabbix 1.8.20 you will see changes in the application names appearing in syslog:
Zabbix Agent -> zabbix_agent Zabbix Agent -> zabbix_agentd Zabbix Proxy -> zabbix_proxy Zabbix Server -> zabbix_server Zabbix Get -> zabbix_get Zabbix Sender -> zabbix_sender
The old, incorrect names (on the left) contained a space which is not allowed by RFC 5424 for APP-NAME. If you are using regular expressions in monitoring of syslog you may want to adjust them for the new application names.
Additional or increased system requirements:
Because of frontend changes, some installations might see incorrect older data appear in frontend. These include:
The following steps have to be performed for successful upgrade from Zabbix 1.6.x to 1.8. The whole upgrade procedure may take several hours depending on size of Zabbix database.
Stop Zabbix server to make sure that no new data is inserted into database.
This is very important step. Make sure that you have backup of your database. It will help if upgrade procedure fails (lack of disk space, power off, any unexpected problem).
Make a backup copy of Zabbix binaries, configuration files and PHP files.
You may use pre-compiled binaries or compile your own.
Some parameters of zabbix_server.conf were changed in 1.8, new parameters added. You may want to review them.
Before running upgrade scripts drop the following indexes:
alter table dhosts drop index dhosts_1; alter table dservices drop index dservices_1; alter table httptest drop index httptest_2; alter table httptest drop index httptest_3; alter table history_log drop index history_log_2; alter table history_text drop index history_text_2; alter table actions drop index actions_1; alter table escalations drop index escalations_2; alter table graphs_items drop index graphs_items_1; alter table graphs_items drop index graphs_items_2; alter table services drop index services_1;
Oracle or PostgreSQL
drop index dhosts_1; drop index dservices_1; drop index httptest_2; drop index httptest_3; drop index history_log_2; drop index history_text_2; drop index actions_1; drop index escalations_2; drop index graphs_items_1; drop index graphs_items_2; drop index services_1;
Ignore any warning messages about non-existent indexes!
Database upgrade scripts are located in directory upgrades/dbpatches/1.8/<db engine>:
Database upgrade should take around 10-15 minutes, for PostgreSQL it may take several hours or more because of conversion of existing historical data. It is recommended to test the upgrade procedure in a non-production environment.
Make sure that you have enough permissions (create table, drop table, create index, drop index). Also make sure that you have enough free disk space.
These scripts are for upgrade from Zabbix 1.6.x to 1.8 only! For upgrade from earlier versions use also upgrade scripts from Zabbix 1.6.x.
Follow installation instructions.
Start new binaries. Check log files to see if the binaries have started successfully.