Status of Zabbix. Running? No

[bernt]

Hi!

I have installed zabbix 1.0 and started zabbix with the command ./zabbix_suckerd.

The command ps-aux gives
zabbix 10070 0.0 1.1 4276 1408 ? S 12:00 0:00 ./zabbix_suckerd
zabbix 10072 0.0 1.1 4276 1396 ? S 12:00 0:00 ./zabbix_suckerd
zabbix 10073 0.0 1.1 4276 1392 ? S 12:00 0:00 ./zabbix_suckerd
zabbix 10074 0.0 1.1 4276 1404 ? S 12:00 0:00 ./zabbix_suckerd
zabbix 10081 0.0 1.2 4332 1532 ? S 12:00 0:00 ./zabbix_suckerd

So I guess it's running. Or?

In the webbinterface, STATUS OF ZABBIX i get.
Is zabbix_trapperd running ? No

I added a host and set it up to test http as simple test but nothing happens.

I'm new to Zabbix and fairly new to Linux.

Best Regards
/Bernt

[Alexei]

Start zabbix_trapperd to get rid of this problem

[bernt]

ups, I mean
Is zabbix_suckerd running ? No

Sorry.

[bernt]

Hi again!

Still got "Is zabbix_suckerd running ? No" in STATUS OF ZABBIX.
But it's no problem to monitor hosts, get statistics and alerts so everything is working.

Best Regards
/Bernt

[avenger]

Still got "Is zabbix_suckerd running ? No" in STATUS OF ZABBIX.
But it's no problem to monitor hosts, get statistics and alerts so everything is working.

I have the same problem on few linux servers running Zabbix.
In my case this is caused by GRSecurity patch on the kernel - it makes impossible for non-root account to view processes that it does not own.
So, please check if the user from which apache is running can view processes correctly

In my case - I am using crossmonitoring of all Zabbix servers - and making "ps" command from agentd conf file.

[Rudolf]

Same problem

Hi there,

I have the same problem. Zabbix is running correctly, but I get the status message "No". I run Fedora Core 3 Linux. The problem is the permission for the exec command in report1.php. Instead of experimenting with permissions I just changed the php file, so no matter if zabbix is running or not, I get status Yes. Not the best solution, but it doesnt scare all people.

[bernt]

Hi!

I got it to work. Just change safe_mode to off in php.ini and restart apache.

Thanks for your help.

Best Regards
/Bernt

[denso]

Sugestion

I have seen this problem on redhat machines (RHEL & FC) and it makes a world of difference if you turn off SEL linux by opening an xterminal and typing system-config-secyritylevel and turning off SELlinux and rebooting once. then the processes work because sel is not blocking them similar to GRSec