-
Notifications
You must be signed in to change notification settings - Fork 60
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
Error sending process list #1
Comments
Do you mean you are getting that in agent logs? The process that you run in the CLI above is not the one responsible for discovery. Could you please paste what |
No its in the console , agent logs are not saying anything out of the ordinary here's the
|
Can you confirm there is no ending If it works, then the JSON is okay (it looks good on your paste, except for the missing trailing curly bracket), and the problem is elsewhere. Also, can you paste your UserParameters from the agent that you are using for discovery? |
I'm sorry there is an ending
Running |
From the zabbix user? If the zabbix user has no permissions for sudo, then sudo would just print an error message, which looks nothing like JSON. Clearly, the output produced is correct, so it must be something at a different layer. |
That fixed IT ! Running
Then commented |
Glad to help! I should probably add a note on this kind of issue to the UserParameters example file. |
…the example sudoers file, and a notice that should help debug problems similar to issue #1 to the sample agent config.
Okay. I have modified the example sudoers file to include this:
Users of RHEL and CentOS should no longer encounter problems such as yours. |
I'm having a problem sending pm2 process information to zabbix 3.0.1
PM2 Status is OK in zabbix but PM2 Processes discovery rule does not trigger stating "Value should be a JSON object"
Running on CentOS 7.2.1511 (Core)
The text was updated successfully, but these errors were encountered: