Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated templates to fix issue with Unsupported Key Item error #53

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

astrugatch
Copy link

Current template causes Unsupported Key Item error when following README instructions. I've updated the file locations recommended to match resolutions in several issue threads.

Updated where ssl_cert_check.sh should be stored.
Modified location for ssl_cert_check.sh to match updated README
@selivan
Copy link
Owner

selivan commented Nov 11, 2024

Nice catch!

But I don't like the idea of placing executable script somewhere in zabbix configs directory. First, <something>.d usually means that everything inside is included in resulting config, second, the script may be used without zabbix too.

I suggest not to change userparameters, but to add this line for basic and advanced templates in zabbix_integration_examples/README.md:

  • copy ssl_cert_check.sh file into /usr/local/bin on host

@astrugatch
Copy link
Author

I was running into an issue where if the script was in /usr/local/bin I received an Unsupported Key Item error in Zabbix when it tried to run discovery. The resolution for me was the same as found in #47 to move the file to the .d location. Not sure if there is a better spot for it to still function as expected.

@selivan
Copy link
Owner

selivan commented Nov 11, 2024

Weird. Either /usr/local/bin was not in PATH or zabbix user did not have access to that path or to the script(wrong permissions), or something like AppArmor/SELinux did not allow that.

Then let's write it like that:

  • copy ssl_cert_check.sh file into /usr/local/bin on host (note: make sure that zabbix user can execute the script)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants