zabbix server not starting

[james.shaw]

Have you tried a different browser? Or from a completely different client?

Are you comfortable using tcpdump on the server, to watch for traffic on port 80?

Based on nothing getting logged in the access_log, despite Apache httpd running, it seems like there's a problem even getting to the server.

I have resolved it now, although it was letting traffic through etc on the firewall, the IP it was assigned was conflicting with another domain, so I changed the IP and now able to access. Lol, oh well, learnt something new in the process!

Thank you for all your help though Tim, I really appreciate it.

Stay safe.

[FaheemKhan]

[root@localhost ~]# systemctl status -l zabbix-server.service
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-04-07 15:48:20 PKT; 3s ago
Process: 9289 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 9279 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 9281 (code=exited, status=0/SUCCESS)

Apr 07 15:48:20 localhost.localdomain kill[9289]: -q, --queue <sig> use sigqueue(2) rather than kill(2)
Apr 07 15:48:20 localhost.localdomain kill[9289]: -p, --pid print pids without signaling them
Apr 07 15:48:20 localhost.localdomain kill[9289]: -l, --list [=<signal>] list signal names, or convert one to a name
Apr 07 15:48:20 localhost.localdomain kill[9289]: -L, --table list signal names and numbers
Apr 07 15:48:20 localhost.localdomain kill[9289]: -h, --help display this help and exit
Apr 07 15:48:20 localhost.localdomain kill[9289]: -V, --version output version information and exit
Apr 07 15:48:20 localhost.localdomain kill[9289]: For more details see kill(1).
Apr 07 15:48:20 localhost.localdomain systemd[1]: zabbix-server.service: control process exited, code=exited status=1
Apr 07 15:48:20 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
Apr 07 15:48:20 localhost.localdomain systemd[1]: zabbix-server.service failed.


this is my status details. my zabbix server's services stopped and not running . please help me

[james.shaw]

[root@localhost ~]# systemctl status -l zabbix-server.service
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2020-04-07 15:48:20 PKT; 3s ago
Process: 9289 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 9279 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 9281 (code=exited, status=0/SUCCESS)

Apr 07 15:48:20 localhost.localdomain kill[9289]: -q, --queue <sig> use sigqueue(2) rather than kill(2)
Apr 07 15:48:20 localhost.localdomain kill[9289]: -p, --pid print pids without signaling them
Apr 07 15:48:20 localhost.localdomain kill[9289]: -l, --list [=<signal>] list signal names, or convert one to a name
Apr 07 15:48:20 localhost.localdomain kill[9289]: -L, --table list signal names and numbers
Apr 07 15:48:20 localhost.localdomain kill[9289]: -h, --help display this help and exit
Apr 07 15:48:20 localhost.localdomain kill[9289]: -V, --version output version information and exit
Apr 07 15:48:20 localhost.localdomain kill[9289]: For more details see kill(1).
Apr 07 15:48:20 localhost.localdomain systemd[1]: zabbix-server.service: control process exited, code=exited status=1
Apr 07 15:48:20 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
Apr 07 15:48:20 localhost.localdomain systemd[1]: zabbix-server.service failed.


this is my status details. my zabbix server's services stopped and not running . please help me

Did you ever get this resolved Faheem?

Usually, moderators or community members would recommend creating a new post. I'll try my best to assist to as I am starting to get my head round it all again.

What OS are you using? The system status doesn't give much, try using journalctl -u zabbix-server and this will give you more details. Is it built around an internal network or external? Or both?

Also, what do the logs say? Should be in /var/log/zabbix/

[rinkymehra]

Any time you add SELinux to the mix, you increase the difficulty. I'm not saying you shouldn't use SELinux, just that the problem isn't purely Zabbix, it's probably Zabbix with SELinux. 9xmovies , mobdro & tubemate

[tim.mooney]

So this is a repeat of something I said earlier in the thread.

I've noticed that happen in a bunch of threads in the past few weeks. So much so that I wonder if the accounts posting these are bots.

[james.shaw]

Any time you add SELinux to the mix, you increase the difficulty. I'm not saying you shouldn't use SELinux, just that the problem isn't purely Zabbix, it's probably Zabbix with SELinux. 9xmovies , mobdro & tubemate

Agree'd, after taking Tims advice, I completely rebuilt, but disable SELinux altogether before installing Zabbix, simply because I use FirewallD and WG Firewalls.

[shred00]

Agree'd, after taking Tims advice, I completely rebuilt, but disable SELinux altogether before installing Zabbix, simply because I use FirewallD and WG Firewalls.

Firewalls are not a replacement for SELinux. They have completely different protection surfaces. You really should not [have to] disable SELinux. You are only weakening the security of the system you run Zabbix on.