You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run the API action restart-process, Icinga2 won't restart. The same happens when curl -k -s -u user:password -H 'Accept: application/json' -X POST \ 'https://localhost:5665/v1/config/packages/example-cmdb?pretty=1' tries to restart Icinga2.
[2019-01-16 10:52:38 +0100] critical/TcpSocket: Invalid socket: Address already in use
Context:
(0) Activating object 'api' of type 'ApiListener'
[2019-01-16 10:52:38 +0100] critical/ApiListener: Cannot bind TCP socket for host '172.17.28.120' on port '5665'.
Context:
(0) Activating object 'api' of type 'ApiListener'
[2019-01-16 10:52:38 +0100] critical/ApiListener: Cannot add listener on host '172.17.28.120' for port '5665'.
Context:
(0) Activating object 'api' of type 'ApiListener'
If I run the API action
restart-process
, Icinga2 won't restart. The same happens whencurl -k -s -u user:password -H 'Accept: application/json' -X POST \ 'https://localhost:5665/v1/config/packages/example-cmdb?pretty=1'
tries to restart Icinga2.Expected Behavior
should restart Icinga2
Current Behavior
does not restart Icinga2. Icinga2 log says:
Context
I want to avoid ssh access to Icinga2 master for dedicated hosts, that should be allowed to modify the Icinga2 configuration. As https://icinga.com/docs/icinga2/latest/doc/12-icinga2-api/#configuration-management tells me, access control and authorization via Icinga2 API is the way to go.
My Environment
icinga2 --version
):r2.10.2-1
FreeBSD 11.2-RELEASE-p7
icinga2 feature list
):icinga2 daemon -C
): is validThe text was updated successfully, but these errors were encountered: