-
Notifications
You must be signed in to change notification settings - Fork 582
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
[dev.icinga.com #10495] Incorrect JSON-RPC message causes Icinga 2 to crash #3569
Comments
Updated by jflach on 2015-10-30 11:21:24 +00:00 I was not able to reproduce this. Could you provide a debug log snippet? It looks like the crash occurs when the connection is shut down, I would like to confirm this. |
Updated by mfriedrich on 2015-10-30 13:33:08 +00:00 Obviously the example needs to be updated. It"s in a different format compared to the other commands. |
Updated by mfriedrich on 2015-10-30 13:35:15 +00:00
Please run icinga2 with gdb/lldb (details in the documentation) and retry your curl request. Then generate a backtrace and attach the backtrace to this ticket. |
Updated by netphantm on 2015-11-01 11:52:50 +00:00
backtrace attached |
Updated by gbeutner on 2015-11-02 16:32:00 +00:00 I can reproduce this here.
|
Updated by gbeutner on 2015-11-02 16:32:43 +00:00 Also, FWIW, 2.3.x does not support HTTP requests. |
Updated by gbeutner on 2015-11-02 16:45:26 +00:00
|
Updated by Anonymous on 2015-11-02 16:50:03 +00:00
Applied in changeset 9c57589. |
Updated by gbeutner on 2015-11-06 16:33:00 +00:00
|
Updated by mfriedrich on 2015-11-12 15:34:44 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10495
Created by netphantm on 2015-10-30 09:32:33 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2015-11-02 16:50:03 +00:00)
Target Version: 2.4.0
Last Update: 2015-11-12 15:34:44 +00:00 (in Redmine)
I tried to acknowledge a check with curl and each time I sent the POST with curl, the icinga2 daemon crashes with this attached report.
the command I try is this:
curl --tlsv1 --cacert /var/lib/icinga2/ca/ca.crt --key /etc/icinga2/pki/de-nue-monitoring-staging.censhare.de.key --cert /etc/icinga2/pki/de-nue-monitoring-staging.censhare.de.crt --anyauth -v -u icingaadmin:pass4icinga -k -s -X POST "https://localhost:5665/v1/actions/acknowledge-problem?type=Service&filter=service.name"ping4"&filter=host.name"sn-svc-vm-02"" -d "{\author\. D. Salinger\",\comment\ thought what I"d do was I"d pretend I was one of those deaf-mutes\",\notify\ }"
I"m not sure if it"s the right command or even a bug, didn"t find to much examples out there on how to acknowledge through the API. without specifying the cert, ca and key, I coudn"t get any results from the API. here is the output:
CApath: /etc/ssl/certs
> POST /v1/actions/acknowledge-problem?type=Service&filter=service.name"ping4"&filter=host.name"sn-svc-vm-02" HTTP/1.1
> User-Agent: curl/7.38.0
> Host: localhost:5665
> Accept: /
> Content-Length: 122
> Content-Type: application/x-www-form-urlencoded
>
if you need more info, please ask.
Attachments
Changesets
2015-11-02 16:45:44 +00:00 by (unknown) 9c57589
The text was updated successfully, but these errors were encountered: