-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
2.0.15, 2.2.10, 2.4.6
Sometimes we need to know what is architecture of a zabbix agent binary (.exe) is running on a windows x64 host.
It's important for example for some performance counters, processes monitoring etc.
If you try to google the question how to check architecture for an exe file - you will be surprised that it's not so easy on windows.
Good thing that agent will show it when you run it with -V option.
c:\>zabbix_agentd.exe -V Zabbix Agent Win32 (service) v2.4.6 (revision 54782) (10 August 2015) Compilation time: Aug 10 2015 10:15:18
c:\>zabbix_agentd-trunk.exe -V
zabbix_agentd Win32 (service) (Zabbix) 3.0.0alpha4
Revision 56587 6 November 2015, compilation time: Nov 6 2015 13:42:39
Copyright (C) 2015 Zabbix SIA
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it according to
the license. There is NO WARRANTY, to the extent permitted by law.
not sure why do we add a "(service)" text here ...
But bad thing that this information is not included to log file:
2248:20151002:192932.707 Starting Zabbix Agent [it0]. Zabbix 2.4.6 (revision 54782). 2248:20151002:192932.707 using configuration file: C:\zabbix_agentd.conf
2332:20151128:111705.217 Starting Zabbix Agent [it0]. Zabbix 3.0.0alpha4 (revision 56587). 2332:20151128:111705.217 **** Enabled features **** 2332:20151128:111705.217 TLS support: NO 2332:20151128:111705.217 ************************** 2332:20151128:111705.217 using configuration file: C:\zabbix_agentd.conf
Suggestion is to add the arch details to the log too, in the first line when agent is starting.