-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Cannot receive topic='nagios' #211
Comments
Below are some more details: define command{ check_command check_kafka!9092!nagios!ISR |
Have you tried the Python version for comparison? It may yield a different error message as this is generated from the underlying library. I personally prefer the python version now. |
Hey Hari, I have tried Python version, it doesn't show same error again but there is another status info, below is the same: Status Info: Initial Service Pseudo-State Could you please confirm if we need to worry about this message. If you can give some details like when this message appears, will be great help for us. Thanks |
Please run it on the command line with the You can use anonymize.py from DevOps Python Tools repo if you want to redact your hostname/IP addresses from the text before pasting it here. |
Hi Hari, Thanks for the response Here is the output for Python version: user@788252a7:/usr/local/nagios/libexec/nagios-plugins# ./check_kafka.py -v -v -v -H IBUS-ibus-1 -P 9092 -T nagios And here is for Perl Version: user@8122a7:/usr/local/nagios/libexec/nagios-plugins# ./check_kafka.pl -v -v -v -H IBUS-ibus-1 -P 9092 -T nagios check_kafka.pl version 0.3 => Hari Sekhon Utils version 1.19.2 host: IBUS-ibus-1 setting timeout to 10 secs connecting to Kafka broker at IBUS-ibus-1:9092 Metadata: Kafka topic 'AC_ADAPTER_COMMAND_RESPONSE_SMS_FINCH' partitions: Kafka topic 'SP.CVPECUNOREQ' partitions: |
Having the same issue with our production check, although it only appears to be happening on one host. Will paste debugging output here when I can reproduce it from the cli. |
|
the port is definitely online, service is responsive |
@ethan-riskiq Did you try the python check_kafka.py plugin to see if it gives a more informative error than the Perl API is returning? |
Also, I think you should use one more |
I have not been a able to reproduce the issue via the python version of the script. I've added a "-new" check that's using the python verison of the script and will see if similar issues occur when the perl script returns this error. |
https://gist.github.com/ethan-riskiq/25a2168b8143c8a59c807c41344154dc gist of python debug output. got UnknownError: failed to find matching consumer record with key error |
That's an old version of check_kafka.py - 0.3.9, current is 0.5.3. Can you please |
Hi Hari,
we are using perl nagios plugin in our environment. we have recently deployed it. however we have observed some blips in nagios trends for kafka brokers, we thought that plugin went critical because kafka is having issue, but that's not the case, these blips are coming frequntly and pluging reports below error:
State info: CRITICAL: Error: Cannot receive: topic='nagios'
Not sure if this is known error in plugin, could you please suggest
The text was updated successfully, but these errors were encountered: