Server says down, agent says up (https)

[deunan]

Hello everyone

I have a server running apache webserver that needs monitoring.

My Zabbix server is running zabbix 3.2.3 on Centos 7.

The Agent is is running zabbix 3.2.3 on Centos 6.

I'm using the standard default templates found on the server for HTTP and HTTPS.

While HTTP template works fine and the service was detected as up, the HTTPS template was not. It was detected as down.

I've tried using zabbix_get on the server and sent out the query key net.tcp.service[https] and successfully got back a "1"

I've tried also other variations - net.tcp.port[,443] and net.tcp.listen[443] - all results in "1".

I tried also testing on the client-side using zabbix_agentd on alll three item key - net.tcp.port[,443], net.tcp.listen[443], net.tcp.service[https] - all results in '[u|1]'.

I tried cloning the existing HTTPS Template on the server's web ui for the trigger of host in question, replacing net.tcp.service[https] which results in 'down' with net.tcp.port[,443] or net.tcp.listen[443], both instead results with 'Unsupported Item Key'.

I hope someone might be kind enough to point out where I go wrong in cinfiguring the agents.

Thank you

[batchenr]

Hello everyone

I have a server running apache webserver that needs monitoring.

My Zabbix server is running zabbix 3.2.3 on Centos 7.

The Agent is is running zabbix 3.2.3 on Centos 6.

I'm using the standard default templates found on the server for HTTP and HTTPS.

While HTTP template works fine and the service was detected as up, the HTTPS template was not. It was detected as down.

I've tried using zabbix_get on the server and sent out the query key net.tcp.service[https] and successfully got back a "1"

I've tried also other variations - net.tcp.port[,443] and net.tcp.listen[443] - all results in "1".

I tried also testing on the client-side using zabbix_agentd on alll three item key - net.tcp.port[,443], net.tcp.listen[443], net.tcp.service[https] - all results in '[u|1]'.

I tried cloning the existing HTTPS Template on the server's web ui for the trigger of host in question, replacing net.tcp.service[https] which results in 'down' with net.tcp.port[,443] or net.tcp.listen[443], both instead results with 'Unsupported Item Key'.

I hope someone might be kind enough to point out where I go wrong in cinfiguring the agents.

Thank you

do you see some logs on zabbix server\agent ?
when you see unsupported item usually on the zabbix GUI you will see on the item red X the reason why it is unsupported. what does it say ?

[deunan]

Hello

Thank you for the reply.

I've enable debug-level and attempted to tail the logs... I tried grepping the both agent and server logs with "net.tcp" string but I did not capture anything.

It seems from my observation, the trigger was totally disabled and thus not polled.

Furthermore, the red icon you mention on the server web UI, hovering the mouse pointer shows it says "Unsupported Item Key"

Appreciate more feedback please, so I can continue troubleshooting.


Regards

[batchenr]

Hello

Thank you for the reply.

I've enable debug-level and attempted to tail the logs... I tried grepping the both agent and server logs with "net.tcp" string but I did not capture anything.

It seems from my observation, the trigger was totally disabled and thus not polled.

Furthermore, the red icon you mention on the server web UI, hovering the mouse pointer shows it says "Unsupported Item Key"

Appreciate more feedback please, so I can continue troubleshooting.


Regards

when you have unsupported you have like a red X- it should tell you why..