SOS!! zabbix fails after upgrade to 3.4

[arut55]

Hello.
upgraded from 3.0.x to3.4..
everything was fine during upgrade .
database pgsql, OS - Centos 7

after systmectl start zabbix-server

13382:20170823:162920.354 syncing history data...
13382:20170823:162920.354 syncing history data done
13382:20170823:162920.354 syncing trend data...
13382:20170823:162920.355 syncing trend data done
13382:20170823:162920.355 Zabbix Server stopped. Zabbix 3.4.0 (revision 71467).
14412:20170823:163003.076 Starting Zabbix Server. Zabbix 3.4.0 (revision 71467).
14412:20170823:163003.077 ****** Enabled features ******
14412:20170823:163003.077 SNMP monitoring: YES
14412:20170823:163003.077 IPMI monitoring: YES
14412:20170823:163003.077 Web monitoring: YES
14412:20170823:163003.077 VMware monitoring: YES
14412:20170823:163003.077 SMTP authentication: YES
14412:20170823:163003.077 Jabber notifications: YES
14412:20170823:163003.077 Ez Texting notifications: YES
14412:20170823:163003.077 ODBC: YES
14412:20170823:163003.077 SSH2 support: YES
14412:20170823:163003.077 IPv6 support: YES
14412:20170823:163003.077 TLS support: YES
14412:20170823:163003.077 ******************************
14412:20170823:163003.077 using configuration file: /etc/zabbix/zabbix_server.conf
14412:20170823:163003.089 current database version (mandatory/optional): 03040000/03040000
14412:20170823:163003.090 required mandatory version: 03040000
14412:20170823:163004.933 server #0 started [main process]
14416:20170823:163004.934 server #1 started [configuration syncer #1]
14417:20170823:163004.934 server #2 started [alerter #1]
14418:20170823:163004.934 server #3 started [alerter #2]
14419:20170823:163004.934 server #4 started [alerter #3]
14420:20170823:163004.935 server #5 started [housekeeper #1]
....
....
....
....
15399:20170823:163006.142 server #984 started [icmp pinger #89]
15411:20170823:163006.143 server #996 started [alert manager #1]
15412:20170823:163006.148 cannot start preprocessing service: Cannot bind socket to "/tmp/zabbix_server_preprocessing.sock": [13] Permission denied.
15411:20170823:163006.148 cannot start alert manager service: Cannot bind socket to "/tmp/zabbix_server_alerter.sock": [13] Permission denied.
14412:20170823:163006.150 One child process died (PID:15412,exitcode/signal:1). Exiting ...
14412:20170823:163007.092 syncing history data...
14412:20170823:163007.092 syncing history data done
14412:20170823:163007.092 syncing trend data...
14412:20170823:163007.092 syncing trend data done
14412:20170823:163007.093 Zabbix Server stopped. Zabbix 3.4.0 (revision 71467).

[kloczek]

15412:20170823:163006.148 cannot start preprocessing service: Cannot bind socket to "/tmp/zabbix_server_preprocessing.sock": [13] Permission denied.
15411:20170823:163006.148 cannot start alert manager service: Cannot bind socket to "/tmp/zabbix_server_alerter.sock": [13] Permission denied.
14412:20170823:163006.150 One child process died (PID:15412,exitcode/signal:1). Exiting

You have no permission to write to /tmp (check do you have 1777 on /tmp) or those socekets or file names already exist and they are owned not by zabbix.

[allexpetrov]

Do you have SELinux enforced?

[arut55]

Thank you very much problem solved

https://support.zabbix.com/browse/ZBX-12567

[N678]

Hello,

I have an identical problem, after the zabbix migration from version 3.2 to 3.4 the zabbix-server service starts and after a few seconds it stops.

I was checking the log and found the message:

can not connect to alert manager service: Can not connect to service "alerter": [2] No such file or directory.

I have SELinux disabled and I am running zabbix on CentOS 6

What could be causing this error?

[aigars.kadikis]

Hi, N678!

Please provide more output from zabbix_server.log. Does any other modules loads successfully?

Does SELinux is disabled in session level or integrated in config:

getenforce
cat /etc/selinux/config

[rk325]

Hi, I recently updated to 3.4.11 and after dealing with other issues like deleting zabbix semaphores, adding a SELinux policies to my Enforced SELinux, and getting the new zabbix db schema, my zabbix_server.log file now displays the error display in this thread:

cannot connect to service "alerter": [2] No such file or directory

Then it dies (stops reporting entries in zabbix_server.log) with the lines:

zabbix Server stopped. Zabbix 3.4.11 (revision 82160).

zabbix_server [18969]: [file:'log.c',line:246] lock failed: [22] Invalid argument

What else can I do?
Thanks,

Yes, I am running Centos 7, with SELinux ENforced but I applied the policy to allow it to run zabbix-server.

[Atsushi]

How did you add policies?
I think that there is probably a shortage of policy additions.
Check the log file(/var/log/audit/audit.log) and add necessary policies.

[rk325]

I created a te file:

module zabbix-server-add 1.0;

require {
type zabbix_t;
class process setrlimit;
}

#============= zabbix_t ==============
allow zabbix_t selfrocess setrlimit;

Then follow procedure to add it:
checkmodule -M -m -o zabbix-server-add.mod zabbix-server-add.te
semodule_package -m zabbix-server-add.mod -o zabbix-server-add.pp
semodule -i zabbix-server-add.pp

In this post https://support.zabbix.com/browse/ZBX-12567 I found another policy file that adds more policies:
module zabbix_server_add 1.1;

require {
type zabbix_var_run_t;
type tmp_t;
type zabbix_t;
class sock_file { create unlink write };
class unix_stream_socket connectto;
class process setrlimit;
}

#============= zabbix_t ==============

#!!!! This avc is allowed in the current policy
allow zabbix_t selfrocess setrlimit;

#!!!! This avc is allowed in the current policy
allow zabbix_t self:unix_stream_socket connectto;

#!!!! This avc is allowed in the current policy
allow zabbix_t tmp_t:sock_file { create unlink write };

#!!!! This avc is allowed in the current policy
allow zabbix_t zabbix_var_run_t:sock_file { create unlink write };

Is it necessary to add all of these?

Thanks,