This was reported a few times in GitHub but no fix for my problem.
This is a CentOS6 install of Icinga version 2.10.4
The command feature is enabled and the socket file exists. Apache is a member of the icingacmd group and the permissions on the socket are rw- for icinga owner and icingacmd group. The directory is rwxr-s— (2750) and the group is icingacmd. I am not getting any violations in seLinux, it is enabled.
[root@Icinga2 ~]# icinga2 object list --type ExternalCommandListener
Object ‘command’ of type ‘ExternalCommandListener’:
% declared in ‘/etc/icinga2/features-enabled/command.conf’, lines 6:1-6:40
That’s a good idea, since the external command pipe will be deprecated with 2.11. This one sources from the 1.x world and the many problems with file permissions and what not. Btw - the command pipe has no error feedback, in contrast to the REST API.
Not sure if I am reading your message correctly, but external command pipe still exists in 2.11 icinga2. To add to it, the icinga2-selinux package is also there and part of Install/Configure docs for Icinga2, including option of command pipeline, configured as default.
Can you please provide some details or clarification, in case I misunderstood?