-
Notifications
You must be signed in to change notification settings - Fork 5
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
No Output. Status=unknown, Message= #2
Comments
I was able to fix it by removing the [0] option in the "check_module" function
|
Hi Niel! I will also edit the README to accept your proposal. :) |
Hi @nieldejonghe , I just found out that my GitLab Server responds differently than yours. On my GitLab Server the response is: I currently use GitLab Enterprise Edition 13.9.1-ee. May I ask you what version you are using? (Just check your server's help page at However, thank you very much for bringing up this issue! |
Hello @KevinKrumbiegel, I just checked my gitlab server today, current version is pretty old 'GitLab Enterprise Edition 12.2.4-ee ' Kind Regards, |
Hi Folks,
|
Hello Kevin,
I've struggled with whitelisting my nagios servers IP in the monitoring whitelist IP in gitlab, maybe it could be good if you put that in your doc as prereq?
I've tried out your plugin in our nagios configuration but i'm not receiving any output.
If I run a curl to my gitlab url I do receive output.
root@:/srv/nagios/libexec# curl -k https:///-/readiness?all=1
{"db_check":{"status":"ok"},"redis_check":{"status":"ok"},"cache_check":{"status":"ok"},"queues_check":{"status":"ok"},"shared_state_check":{"status":"ok"},"gitaly_check":{"status":"ok","labels":{"shard":"default"}}}
Output from check_gitlab
root@:/srv/nagios/libexec# ./check_gitlab -s https:/// --check-all
Cache check: Status=unknown, Message=
Database check: Status=unknown, Message=
Gitaly check: Status=unknown, Message=
Queues check: Status=unknown, Message=
Redis check: Status=unknown, Message=
Shared state check: Status=unknown, Message=
6 checks done.
Any Idea in how to troubleshoot this?
Kind Regards,
Niel
The text was updated successfully, but these errors were encountered: