"Too many parameters" on item

[sxzssxxs]

Hi,

I have an item that doesn't work because of the error: "Too many parameters". The key I'm using is:

vfs.file.cksum[/etc/passwd,sha256]

When I use the same key without the 'sha256' part, so like this:

vfs.file.cksum[/etc/passwd]

, the item does work. Deleting and re-adding the item doesn't make any difference. Any idea why this error shows? Looking at the key selector the syntax of my key seems to be correct.
Item:

Error:

While Googling I found another user that seems to have the same issue (last comment in this thread): https://www.zabbix.com/forum/zabbix-...584#post478584

[kyus]

Have you tried to use zabbix_get on your server and check the agent logs to see if there's anything there?

Oh, and what's the version of your Server and Agent? The "mode" parameter is supported since Zabbix 6.0.

[kyus]

I tested this item in my Zabbix Server 6.0 on a host with Zabbix Agent 5.0 running and i got the same "Too many parameters" error. Maybe that's your case? Hope it helps.

[sxzssxxs]

Oh how silly of me. Server was running latest but agent was running 4.0.17. I reinstalled the agent to a newer version and now it works. Thank you very much!

[kyus]

Hey!

I'm not sure if this will help or not. But when you use sha256 the value returned is a string. Maybe you could try using a different type of information.

Again, it's just a guess, since for me, it worked just fine with any type of information set.

[sxzssxxs]

Hi, thanks for your help but I already tried that (I should've mentioned it) and unfortunately that doesn't make a difference.

[kyus]

Have you tried to use zabbix_get on your server and check the agent logs to see if there's anything there?

Oh, and what's the version of your Server and Agent? The "mode" parameter is supported since Zabbix 6.0.

[kyus]

I tested this item in my Zabbix Server 6.0 on a host with Zabbix Agent 5.0 running and i got the same "Too many parameters" error. Maybe that's your case? Hope it helps.

[sxzssxxs]

Oh how silly of me. Server was running latest but agent was running 4.0.17. I reinstalled the agent to a newer version and now it works. Thank you very much!