Systemd by Zabbix Agent 2 Discovery Not Supported (Timeout Occurred)

[FromDaMud]

Hello All,

Quite new to Zabbix...

I've been trying to setup service monitoring for a few of our Linux Servers (Ubuntu 22.04.5 LTS).

But I run into an issue when trying to discover SystemD services, when I go to execute the rules to see what services are active on my server it says under status "Not Supported" and there's an info icon right beside it saying "Timeout occurred while gathering data".

I have it working for a few test VM's and it works great, but when I try to use on our corporate servers it doesn't bring up any items and gives that message.

I believe it's something with our corporate servers as it works fine with a test VM. I have the server set, the PSK options set, etc. Like I said got it working quite quick on the test VM's so I don't think it's a standard configuration issue.

I know haven't given much information on our servers but just thought I'd ask to see if anyone else ran into a similar issue.

Thanks,

[cyber]

Is there something in agent logfile on those corp servers? Do you have access to those servers, you could increase logging level and try to find out what it is doing there... What can your admins tell you about selinux errors? I would say, it sounds more like something you should look up together with server admins...

[FromDaMud]

Hey there,

Thanks for the reply, I checked within the log files of the corp servers and it seems the reporting is working, no errors, if I trigger it manually I can see the JSON. It seems the actual sending of the JSON isn't working.

Locally this works on the agents "zabbix_agent2 -t "systemd.unit.discovery[service]" and reports back the list of services.

When I try to trigger the agents remotely I receive "zabbix_get [3772]: Get value error: cannot read from socket: [104] Connection reset by peer"

When I try I aim it towards the server, I know this is not how zabbix _get functions but maybe give more information, I get "ZBX_NOTSUPPORTED: Received empty response from Zabbix Agent at [x.x.x.x]. Assuming that agent dropped connection because of access permissions."

I've tested the firewalls on both the agents and server and everything is open and works.

I just tried building one for 24.04 Noble and it worked fine. I tried it another 22.04 Jammy and it didn't work, but it did say the socket unit discovery rule was supported but not the services.

So it seems it's a versioning issue or something with 22.04 Jammy.

Thanks,

[FromDaMud]

First two are aimed at the different agents and the last one was aimed at the zabbix server, I know it's typically not set up like that but just thought the last entry may give a hint.