Upgrading RH7 linux system from zabbix 5.2 to zabbix 6.0 question

[tim.mooney]

The zabbix_agent2 plugin documentation for Zabbix 5.2 is here: https://www.zabbix.com/documentation.../zabbix_agent2

The zabbix_agent2 distribution comes with a default set of plugins, which might change at various versions of agent2, but it appears that even the 5.2 zabbix_agent2 has the docker plugin included by default: https://www.zabbix.com/documentation.../items/plugins

At zabbix_agent 5.2, it looks like there's only one plugin-specific config parameter (later versions have more), search for "Plugins.Docker" in the zabbix_agent2 plugin config documentation: https://www.zabbix.com/documentation.../zabbix_agent2

You probably don't need it, but the upstream for the plugin source is here: https://git.zabbix.com/projects/ZBX/...plugins/docker

[pmurtey]

Hi Tim, We were able to download a copy of the Linux agent2 for 5.2. In order to test out what we are doing, we installed a version of 6.2.5 zabbix management server for testing purposes. Then we downloaded a regular zabbix agent, and a zabbix_agent2. Using windows devices we installed the regular zabbix agent and configured and it connected to the zabbix management server just fine. However, the second windows device we installed with the zabbix_agent2 we configured the .conf just the same as the other. But when we tried to get it to connect to the Zabbix management server it would not connect. Looking at the docs in more detail it says "Agent 2 is written in Go programming language (with some C code of Zabbix agent reused). A configured Go environment with a currently supported Go version is required for building Zabbix agent 2. On Windows, the agent 2 is supported on all desktop and server versions, on which an up-to-date supported Go version can be installed. " We dont quite understand what "required for building Zabbix agent 2" means. We added a most recent version of GO to the system but it did not seem to make any difference. IS there something we are missing here?

[tim.mooney]

We dont quite understand what "required for building Zabbix agent 2" means

That doesn't apply when you're using the pre-built packages. "Building" is another way of saying "compiling the source code to produce a binary executable". You're not doing that, you're taking binaries that were already produced for you by the developers.

Whatever problem you're running into, it's not related to that comment about "building".

I would try increase the log_level for the agent2 and see if you get any useful information in the logs. Have you checked to make sure the Windows firewall on the second system has the same exceptions as the firewall on the first system?

[pmurtey]

Got it, it was really ridiculous. The hostname in the config file was spelled in upper case, and the host spelled in the management server was lower case. Didn't believe there would be a case sensitively between the two.

[cyber]

Why do you copy question from someone else.... ?

[pmurtey]

Hi All, We managed to get the Agent2 installed on one of our servers, and added the zabbix user to the docker group. But when we discover the device, we get all the regular performance metrics but not the docker metrics, So we went down in to Items>discovery on the device and we see the attached message. Any ideas what may be going on?

[Atsushi]

It's hard to read because the letters are small, but isn't the zabbix user unable to access the socket (default: /var/run/docker.sock) for calling the Docker API? Check the socket permissions and try setting the user group as shown in the URL below.

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/400109-zabbix-5-0-0beta1-ubuntu-18-04-i-add-template-app-docker-get-error-not-supported#post400163

https://www.zabbix.com/forum/zabbix-...docker-offline

[pmurtey]

The two links provided did the Job, Thank you very much.

[pmurtey]

Hi All, We got the docker working with Agent2 and we noticed that the cpu metric information being reported was in milliseconds. So we found a link to a template which provided the metric in percentage. https://support.zabbix.com/browse/ZBXNEXT-6677 . So we replaced thedocker template with the one shown on the web page and we started getting percent. The new problem is now, the percent is being reported in a 100th of a percent. As an example the chart shows the percent utilization as .010 %, when in actuality the command line display shows the cpu at 10%. In the information presented in the link above they mention the formula as being: "CPU usage % = (cpu_delta / system_cpu_delta) * number_cpus * 100.0 ". However, when I examine the the .xml file of the template it shows the formula of : (last(docker.container_stats.cpu_usage.delta.syste m.rate[&quot;{#NAME}&quot;])/last(docker.container_stats.cpu_usage.delta.total. rate[&quot;{#NAME}&quot;]))*last(docker.container_stats.online_cpus[&quot;{#NAME}&quot;])*100</params>
Should that last number in the formula of *100 be *100.0 or does it make a difference?

[LenR]

Zabbix is pretty easy to upgrade, I've been a user since the 1.8 era, sometimes we did a fresh install, sometimes we upgraded. I suspect we did a fresh install at times when my current knowledge would have allowed an upgrade. Company didn't fund training, so funds were found in project delays :-)

The issue with choosing Redhat based host distro's is they don't support version-to-version upgrade. That is our OS platform choice, at least RHEL based. Personally, it seems that Ubuntu does support version-to-version update, so I suspect some Zabbix users of those OS hosts, don't need to do OS fresh installs.

[stademock]

I don't see any export option for host groups or users, so my guess is you would need to recreate those manually, although looking at what's in the "hosts" XML export, it's possible the host groups will be recreated, but I'm not certain. Again, I've never tried it.