Zabbix Documentation 1.8 (current)| In development:5.2 (devel)| Unsupported:

User Tools

Site Tools



3 インストールとアップグレードに関する注意事項

3.1 インストール


3.2 バージョンの互換性



3.3 重要な注意事項

3.3.1 For version 1.8
  • All hosts now are required to belong to at least one group.
  • CPU index for system.cpu.util key on Linux now starts with 0.
  • Key vfs.fs.size returns data in bytes for all operating systems now.
  • Key vfs.fs.size now takes into account reserved diskspace for root user.
  • Comment at the end of a configuration file line is not allowed anymore (this worked for numeric parameters only before).
3.3.2 For version 1.8.3
  • Parameter service.ntp for item keys net.tcp.service and net.tcp.service.perf renamed to ntp. Old syntax is still supported.
  • Trying to run IPv6-enabled daemon on a system without IPv6 support fail:
    Listener failed with error: socket() for [[(null)]:10051] failed with error 97: Address family not supported by protocol.
3.3.3 For version 1.8.5
  • The method of external command invocation for Zabbix daemons has been changed to allow terminating runaway processes. Instead of using standard popen method as before, Zabbix now explicitly calls /bin/sh to execute desired command.
  • Trying to run a Zabbix daemon, compiled on Linux kernel 2.6.27 or later on a system with kernel 2.6.26 or older will fail:
    socket() for [[-]:10050] failed with error 22: Invalid argument
3.3.4 For version 1.8.6
  • Zabbix daemons now refuse to start up if configuration file contains incorrect parameters. If old parameters have accumulated in the configuration files, this will result in inoperable daemons after the upgrade until the parameters are fixed.
3.3.5 For version 1.8.8
  • In some cases hosts and proxies with identical name might have appeared in the Zabbix database. In 1.8.8, Zabbix server will shut down if it detects such a situation. This check was removed in 1.8.9.
3.3.6 For version 1.8.9
  • The shutdown upon detection of duplicate hosts, introduced in 1.8.8, has been removed.
3.3.7 For version 1.8.16
  • Accepted data limit of 128MB was introduced when using Zabbix protocol. Any other data (including older Zabbix protocols) stays limited at 16MB.

3.4 システム要件の変更


  • サポート対象からPHP4を除外
  • PHPの最大メモリサイズは、少なくとも128MB (memory_limitオプション)
  • PHPの最大POSTサイズは、少なくとも16MB (post_max_sizeオプション)

また、 および1.8.9の要件の変更を参照してください。

3.5 既知の問題

3.5.1 For version 1.8
  • PHP mbstring check may fail with PHP < 5.2 in Zabbix 1.8. To avoid this issue, copy zabbix.conf.php.example file to zabbix.conf.php and modify parameters, including database access parameters.
  • For IPMI support you need a recent OpenIPMI version - 2.0.14 and later is known to work.
  • Sorting in frontend is not performed for entities with positional variables (like item names with $1 etc).
  • XML export includes SNMP and other information for all items.
  • Hostnames with spaces do not work when sending data from a file with zabbix_sender (fixed in 1.8.2).
  • Uploading of images for network maps may fail if database is not configured properly. Make sure database, tables and fields are set to UTF-8 encoding.
  • Precompiled binaries (agent, sender, get) might not work on 64bit systems with glibc versions older than 2.5. Common symptom is failing to start with the error message: Floating point exception. Use older versions, or compile from the scratch on the target system.
3.5.2 For version 1.8.2

Because of frontend changes, some installations might see incorrect older data appear in frontend. These include:

  • Incorrect trigger appearing, with name **ERROR**, usually in Monitoring → Triggers section, when showing all hosts from all groups. This trigger can be deleted by clicking on it, choosing Configuration of triggers, then clicking on Delete in the trigger editing form and confirming the deletion.
You might have to remove groupid=&hostid=& part from the URL when attempting to delete the trigger.
  • Depending on the installation time of your Zabbix server, default graphs might have incorrect configuration. This only affects you if those graphs are being used. Opening such a graph usually will swap working time and trigger showing with percentile values. If that is the case, simply fixing and saving the graph will solve the problem.

3.6 アップグレード手順

Zabbixの1.6.xのから1.8に正常にアップグレードするために次の手順を実行する必要があります。 Zabbixのデータベースのサイズによってアップグレード手順に数時間かかることがあります。

3.6.1 Zabbixサーバ停止


3.6.2 既存のZabbixデータベースのバックアップ


3.6.3 設定ファイル、PHPファイルとZabbixバイナリのバックアップ


3.6.4 新しいZabbixサーバ(バイナリ)のインストール


3.6.5 サーバ設定パラメータの確認


  • Zabbixサーバとプロクシ設定ファイルからStartDBSyncersオプションは削除されました。
3.6.6 データベースのアップグレード
1.6から1.8などのメジャーなZabbixバージョンをアップグレードする場合、データベースのアップグレードは必須のステップです。 特にリリースノートに明記しない限り、1.8.xからは1.8.xのようなマイナーバージョンのアップグレードにはデータベースのアップグレードは必要ありません。



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; 


データベースのアップグレードスクリプトは、ディレクトリ upgrades/dbpatches/1.8/<db engine> に配置されています:

  • MySQL: upgrades/dbpatches/1.8/mysql/patch.sql
  • Oracle: upgrades/dbpatches/1.8/oracle/patch.sql
  • PostgreSQL: upgrades/dbpatches/1.8/postgresql/patch.sql





3.6.7 新しいZabbix GUIのインストール


3.6.8 新しいZabbixの起動