-
Documentation task
-
Resolution: Fixed
-
Trivial
-
3.4.1
-
None
-
RHEL6 x64 (Red Hat Enterprise Linux Server release 6.9 (Santiago))
-
Sprint 17, Sprint 18, Sprint 19, Sprint 20, Sprint 21
-
4
Following: https://www.zabbix.com/documentation/3.4/manual/installation/install_from_packages/rhel_centos
and installing zabbix-server-pgsql and zabbix-web packages.
1: by default, root does not have access permissions for pgsql, even if invoking as "psql -U postgres" - one must "su - postgres" before attempting to create or modify databases or users (user postgres doesn't need to use a -U argument when invoking psql))
2: In DB creation page
- for pgsql no mention of creating a zabbix user, setting password, or setting access permissions (there are instructions for mysql)
- "su - postgres", then "createuser --pwprompt zabbix",
3: packaged db creation scripts will create database and tables owned by user postgres instead of user zabbix, if followed as-is
- Instead, as user postgres, "createdb -O zabbix zabbix" (not inside psql!)
- then exit back to root, and "su - -s /bin/bash zabbix"
- then run the package scripts "zcat /usr/share/doc/zabbix-server-pgsql-3.4.1/create.sql.gz | psql zabbix"
4: webpage refers to /etc/httpd/conf.d/zabbix - which isn't provided in the el6 3.4.1 zabbix-web package (yum search shows it in EPEL zabbix 1.8/2/0/2.2 packages, so this is likely an oversight)
5: webpage talks about using "systemctl" for management - systemd commands are RHEL7 specific. RHEL6 uses "service" and "chkconfig" commands only (these commands work on RHEL7 but are deprecated)
6: "setsebool -P httpd_can_connect_zabbix on" as root
results in:
"Boolean httpd_can_connect_zabbix is not defined"
7: Package installer doesn't verify canonical paths, so if /var/log/ is a symlink to another area (like a large spooler disk) then selinux permissions are not set properly and startup fails due to permission denied for /var/log/zabbix
8: package sets user zabbix home directory to /var/lib/zabbix - which doesn't exist.