Zabbix manual release 017 "errata"

[Neurotox]

Hi,

In section "3.5.2.Usage" of the manual release 017 some information are missing.

-------------
Functions:
-i --install Install ZABBIX agent as a service.
-d --uninstall Uninstall ZABBIX agent service.
-s --start Start ZABBIX agent service.
-x --stop Stop ZABBIX agent service.
-----------------

should also include

------------------
-m --multiple-agents service name will include hostname
------------------

This information is already include in zabbix_agentd.exe but not in the manual. It could be frustrating when you read the manual instead of the output of the file and you try to figure out how to install 2 agent on Windows at 02:00 am

[richlv]

btw, what good are two agents on single host for ?

[Alexei]

btw, what good are two agents on single host for ?

I see little sense of running two agents. However running of hundreds of the agents can be handy for testing...

BTW The manual is updated, thanks.

[aivarss]

Hi!

On page 108 of the Zabbix manual release 17 are 2 mistakes:
1)
------------------
web.page.get[host,<path>,<port>]

Return value: host - hostname, path - path to HTML document (default is /), port - port number (default is 80)
Parameters: WEB page source as text
------------------

should be

------------------
web.page.get[host,<path>,<port>]

Return value: WEB page source as text
Parameters: host - hostname, path - path to HTML document (default is /), port - port number (default is 80)
------------------

2)
------------------
web.page.regexp[host, <path>,<port>,<regexp>,<length>,]

Comments:
Returns EOF on fail.
Example: web.page.get[www.zabbix.com, index.php,80, OK, 2]
------------------

should be


------------------
web.page.regexp[host, <path>,<port>,<regexp>,<length>,]

Comments:
Returns EOF on fail.
Example: web.page.regexp[www.zabbix.com, index.php,80, OK, 2]
------------------

[Neurotox]

I see little sense of running two agents. However running of hundreds of the agents can be handy for testing...

BTW The manual is updated, thanks.

Maybe it's my mystake but my understanding is running multiple agent is the only way to have many Zabbix servers checking the same host with active check.

ZabbixS1 and ZabbixS2 are in 2 different physical location
ZabbixS1 and ZabbixS2 monitor host1.
Host1 is behind a firewall and using active checks
Host1 need to run 2 agents with 2 different config files to be able to answer to ZabbixS1 and ZabbixS2.

Thanks for the correction.

[richlv]

Maybe it's my mystake but my understanding is running multiple agent is the only way to have many Zabbix servers checking the same host with active check.

good point. i guess it also would make for a good feature request
that is, instead of using only the first server ip for active checks, a new parameter could be introduced, named 'activeservers' or similar. serverlist would be allowed to connect to the agent, active serverlist would get connected to by agent.

though one problem i can see with multiple active servers and single agent - how could agent determine which server to query for itemlist and which server would be authoritative if the returned data would differ ?

[Andreas Bollhalder]

Maybe it's my mystake but my understanding is running multiple agent is the only way to have many Zabbix servers checking the same host with active check.

ZabbixS1 and ZabbixS2 are in 2 different physical location
ZabbixS1 and ZabbixS2 monitor host1.
Host1 is behind a firewall and using active checks
Host1 need to run 2 agents with 2 different config files to be able to answer to ZabbixS1 and ZabbixS2.

Thanks for the correction.

Or when you have multiple IPs with different services bound, it would come handy too. For example, on our ZABBIX server itself, MySQL is running only on the loopback interface. I have a template which monitors the daemon and the port of MySQL with the dependency for the port on the daemon. A second ZABBIX agent listening on localhost can use this template without special modification.

Andreas