Am 13.10.2014 21:42 schrieb "Daniel Bareiro" <daniel-lis...@gmx.net>:
>
> Hi all!
>
> I'm using Icinga-web and Icinga2 from the snapshots repositories of
Icinga.
>
> Now I'm trying to test the functionality of schedule next/forced service
> check.
>
> I understand that this requires to have configured the external command
> file that I had not configured during the installation of the package. I
> was reading the Icinga2 documentation regarding it [1]. So I made sure
> to do the following:
>
> # icinga2-enable-feature command
> # usermod -a -G nagios www-data
> # service icinga2 restart
>
> I also made sure to have created the file in the expected location,
> which I understand would be this:
>
> vim /usr/share/icinga-web/app/modules/Api/config/access.xml
> [...]
> <!-- allowed to be written to -->
> <write>
> <files>
> <resource
> name="icinga_pipe">/var/lib/icinga/rw/icinga.cmd</resource>
> </files>
> </write>
> <!-- allowed to be executed -->
> [...]
Why? The docs tell otherwise!
>
> Then:
>
> # mkfifo /var/lib/icinga/rw/icinga.cmd
> # chown nagios.nagios /var/lib/icinga/rw/icinga.cmd
> # chmod g+w,o-r /var/lib/icinga/rw/icinga.cmd
Where did you get that from? Icinga 2 creates the command pipe by itself.
>
> # ll /var/lib/icinga/rw/icinga.cmd
> prw-rw---- 1 nagios nagios 0 oct 13 16:25 /var/lib/icinga/rw/icinga.cmd
>
> But when I try schedule the next service check, after clicking on "OK",
> Icinga-web is permanently in a dull gray color as if it not finished
> processing the request.
>
> Although the log does not seem to show any error:
>
> ------------------------------------------------------------------
> # tail -F /var/log/icinga-web/debug-2014-10-13.log
> [...]
> [Mon Oct 13 16:32:36 2014] [info] SendCommandAction: Prepare to send
> command (command=SCHEDULE_SVC_CHECK)
> [Mon Oct 13 16:32:36 2014] [debug] SendCommandAction: Successfull
> authentication (hmac=5cd9ec9f155e56c0d4d2d731898e229532225e01)
> [Mon Oct 13 16:32:36 2014] [info] Array
> (
> [0] => Array
> (
> [host] => ss01
> [service] => Temp1
> [instance] => default
> )
>
> )
>
> [Mon Oct 13 16:32:36 2014] [info] Array
> (
> [0] => Array
> (
> [host] => ss01
> [service] => Temp1
> [instance] => default
> )
>
> )
>
> [Mon Oct 13 16:32:36 2014] [debug] Trying to send commands, targets:
> [{"host":"ss01","service":"Temp1","instance":"default"}] , data:
> {"checktime":"2014-10-13 16:32:30"}
> (Cronks_System_CommandSenderModel::dispatchCommands(), line 69)
> [Mon Oct 13 16:32:36 2014] [debug] Setting up console for instance
> default (Cronks_System_CommandSenderModel::getConsoleInstance(), line 79)
> [Mon Oct 13 16:32:36 2014] [debug] Submitting command SCHEDULE_SVC_CHECK
> to {"host":"ss01","service":"Temp1","instance":"default"}
> (Cronks_System_CommandSenderModel::dispatchCommands(), line 69)
> [Mon Oct 13 16:32:36 2014] [debug] Sending icinga-command [1413228756]
> SCHEDULE_SVC_CHECK;ss01;Temp1;1413228750
> (Api_Commands_CommandDispatcherModel::submitCommand(), line 83)
> ------------------------------------------------------------------
>
> Any clue what could be happening?
You're writing to your own custom created command pipe where no process is
reading from.
Just follow the official docs on setting up icinga web.
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/getting-started#setting-up-icinga-web
>
>
> Thanks in advance.
>
> Best regards,
> Daniel
>
> [1]
>
http://docs.icinga.org/icinga2/latest/doc/module/icinga2/chapter/getting-started#setting-up-external-command-pipe
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
