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 #11224] Socket Exceptions (Operation not permitted) while reading from API #3970
Comments
Updated by bashgeek on 2016-02-24 16:56:50 +00:00 The requests finish properly with correct data though. |
Updated by mfriedrich on 2016-02-24 19:24:41 +00:00 Is it specific to GET requests and/or /v1/objects/services (I guess not, just to be sure)? |
Updated by mfriedrich on 2016-02-24 22:35:07 +00:00 Just stumbled over this when testing a different patch.
|
Updated by bashgeek on 2016-02-25 04:55:46 +00:00 dnsmichi wrote:
Nope, seems to happen for every request here. |
Updated by tobiasvdk on 2016-03-07 16:42:21 +00:00 I get the same error when using the icingaweb2 director kickstart and no data is returned when trying to get "/v1/objects/zones". A manual "curl" command succeeds without an error
I'm using icinga 2 r2.4.3-229-gd14477c |
Updated by tobiasvdk on 2016-03-09 07:55:00 +00:00 After updating icinga 2 director no error message is shown during kickstart run. |
Updated by tobiasvdk on 2016-03-09 10:47:49 +00:00 I stumbled over this error again today while using Chrome to test some API GET requests. |
Updated by mfriedrich on 2016-03-18 11:10:34 +00:00
|
Updated by mfriedrich on 2016-03-29 11:09:54 +00:00
|
Updated by mfriedrich on 2016-03-29 11:49:29 +00:00
|
Updated by mfriedrich on 2016-03-29 11:55:03 +00:00
Applied in changeset 5dd685c. |
Updated by gbeutner on 2016-04-20 08:15:59 +00:00
|
Updated by mfriedrich on 2016-05-09 11:38:47 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11224
Created by bashgeek on 2016-02-24 16:54:38 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2016-03-29 11:55:03 +00:00)
Target Version: 2.4.5
Last Update: 2016-05-09 11:38:46 +00:00 (in Redmine)
This is happening since yesterdays upgrade to 2.4.2 (using the Debian Jessie package).
I'm not quite sure why this is happening, it didn't before but now these logs come up with every request made to the API (no client-certificates, just basic login):
It's a standalone setup without any satellites and/or special configurations.
If you need any more information I'm happy to provide it.
Changesets
2016-03-29 11:52:37 +00:00 by mfriedrich 5dd685c
2016-04-20 08:07:24 +00:00 by mfriedrich 98eef33
The text was updated successfully, but these errors were encountered: