New install: "Zabbix server is not running: the information displayed may not be curr

[catdude]

I just installed zabbix 2.2:
[root@wowza conf.d]# rpm -qa | grep zab
zabbix22-web-2.2.1-5.el6.noarch
zabbix22-2.2.1-5.el6.x86_64
zabbix22-server-mysql-2.2.1-5.el6.x86_64
zabbix22-server-2.2.1-5.el6.noarch
zabbix22-web-mysql-2.2.1-5.el6.noarch
zabbix22-dbfiles-mysql-2.2.1-5.el6.noarch
zabbix22-agent-2.2.1-5.el6.x86_64

When I do "service start zabbix-server" and "service httpd restart" and go to http://<my server>/zabbix I'm able to log in fine as Admin, but as I'm working I get an error bar reading "Zabbix server is not running: the information displayed may not be current". However,
[B][root@wowza conf.d]# service zabbix-server status
zabbix_server (pid 1802) is running...
[root@wowza conf.d]# ps aux | grep 1802
495 1802 0.0 0.0 164916 3112 ? S 16:01 0:00 /usr/sbin/zabbix_server -c /etc/zabbix_server.conf


When I look at /var/log/zabbixsrv/zabbix_server.log I see:
[root@wowza zabbix]# tail -f /var/log/zabbixsrv/zabbix_server.log
1802:20141031:160140.175 Starting Zabbix Server. Zabbix 2.2.1 (revision 40808).
1802:20141031:160140.175 ****** Enabled features ******
1802:20141031:160140.175 SNMP monitoring: YES
1802:20141031:160140.175 IPMI monitoring: YES
1802:20141031:160140.175 WEB monitoring: YES
1802:20141031:160140.175 VMware monitoring: YES
1802:20141031:160140.176 Jabber notifications: YES
1802:20141031:160140.176 Ez Texting notifications: YES
1802:20141031:160140.176 ODBC: YES
1802:20141031:160140.176 SSH2 support: YES
1802:20141031:160140.176 IPv6 support: YES
1802:20141031:160140.176 ******************************
1802:20141031:160140.176 using configuration file: /etc/zabbix_server.conf
1802:20141031:160140.179 current database version (mandatory/optional): 02020000/02020000
1802:20141031:160140.179 required mandatory version: 02020000
1806:20141031:160140.181 server #1 started [configuration syncer #1]
1807:20141031:160140.182 server #2 started [db watchdog #1]
1815:20141031:160140.189 server #9 started [trapper #1]
1816:20141031:160140.191 server #10 started [trapper #2]
1818:20141031:160140.191 server #12 started [trapper #4]
1820:20141031:160140.192 server #14 started [icmp pinger #1]
1822:20141031:160140.192 server #16 started [housekeeper #1]
1822:20141031:160140.192 executing housekeeper
1817:20141031:160140.194 server #11 started [trapper #3]
1819:20141031:160140.194 server #13 started [trapper #5]
1821:20141031:160140.199 server #15 started [alerter #1]
1823:20141031:160140.199 server #17 started [timer #1]
1824:20141031:160140.199 server #18 started [http poller #1]
1826:20141031:160140.202 server #20 started [history syncer #1]
1828:20141031:160140.202 server #22 started [history syncer #3]
1827:20141031:160140.203 server #21 started [history syncer #2]
1802:20141031:160140.204 server #0 started [main process]
1829:20141031:160140.206 server #23 started [history syncer #4]
1822:20141031:160140.215 housekeeper [deleted 0 hist/trends, 0 items, 0 events, 0 sessions, 0 alarms, 0 audit items in 0.008522 sec, idle 1 hour(s)]
1843:20141031:160140.216 server #24 started [escalator #1]
1844:20141031:160140.219 server #25 started [proxy poller #1]
1845:20141031:160140.219 server #26 started [self-monitoring #1]
1809:20141031:160140.288 server #3 started [poller #1]
1813:20141031:160140.292 server #7 started [poller #5]
1825:20141031:160140.294 server #19 started [discoverer #1]
1810:20141031:160140.304 server #4 started [poller #2]
1811:20141031:160140.304 server #5 started [poller #3]
1814:20141031:160140.307 server #8 started [unreachable poller #1]
1812:20141031:160140.307 server #6 started [poller #4]


So at this point I'm at a loss as to why I'm getting that error bar. Any suggestions? This is on a box running Centos 6.5

[ZabbixFun]

Try on terminal:

getsebool httpd_can_network_connect

If the result is:

httpd_can_network_connect --> off

run in terminal:

setsebool -P httpd_can_network_connect on

This should fix it...
Also check selinux status with "sestatus" and disable it if necessary

[catdude]

That was the problem

That was it, thanks.

I've been running Linux machines for a long time, but so far I've been able to avoid learning much about SELinux. I guess it's time to correct that deficit!