Hello Markus and community,
English in the second part of my mail.
---DEUTSCH---
ich habe mittlerweile die access.xml
(icinga-web/etc/conf.d/access.xml) folgendermaßen angepasst und den
Cache gelöscht:
<instances>
<!-- For slave commands seperate hosts with ';'
<instance
name="default">localhost;host1;host15</instance> -->
<instance name="default">localhost</instance>
<instance name="umgebung1">localhost</instance>
<instance name="umgebung2">localhost</instance>
<instance name="umgebung3">localhost</instance>
<instance name="umgebung4">localhost</instance>
<instance name="umgebung5">localhost</instance>
<instance name="umgebung6">localhost</instance>
</instances>
<access>
...
<write>
<files>
<resource
name="umgebung1_pipe">/apps/nagios/instances/umgebung1/var/rw/icinga.cmd</resource>
<resource
name="umgebung2_pipe">/apps/nagios/instances/umgebung2/var/rw/icinga.cmd</resource>
<resource
name="umgebung3_pipe">/apps/nagios/instances/umgebung3/var/rw/icinga.cmd</resource>
<resource
name="umgebung4_pipe">/apps/nagios/instances/umgebung4/var/rw/icinga.cmd</resource>
<resource
name="umgebung5_pipe">/apps/nagios/instances/umgebung5/var/rw/icinga.cmd</resource>
<resource
name="umgebung6_pipe">/apps/nagios/instances/umgebung6/var/rw/icinga.cmd</resource>
</files>
</write>
...
</access>
Der Rest wurde original so gelassen bzw. es wurden nur die Pfade geändert.
Ich habe nun versucht einen Befehl abzusetzen und im Log gesehen, dass
Icinga dem jeweiligen Host die richtige Instanz zuordnet. Aber es ist
folgender Eintrag im Log vorhanden:
Sending command failed icinga_pipe is not write enabled
Dh. Icinga greift nicht auf meine access.xml zu, denn da ist diese
Pipe ja nicht mehr definiert?!
Ich habe die globale access.xml im icinga-web/etc/conf.d editiert.
Es gibt aber auch noch eine unter icinga-web/app/modules/Api/config/
Welche ist denn jetzt die Richtige?
---ENGLISH---
i've edited the access.xml (icinga-web/etc/conf.d/access.xml) as following:
<instances>
<!-- For slave commands seperate hosts with ';'
<instance
name="default">localhost;host1;host15</instance> -->
<instance name="default">localhost</instance>
<instance name="umgebung1">localhost</instance>
<instance name="umgebung2">localhost</instance>
<instance name="umgebung3">localhost</instance>
<instance name="umgebung4">localhost</instance>
<instance name="umgebung5">localhost</instance>
<instance name="umgebung6">localhost</instance>
</instances>
<access>
...
<write>
<files>
<resource
name="umgebung1_pipe">/apps/nagios/instances/umgebung1/var/rw/icinga.cmd</resource>
<resource
name="umgebung2_pipe">/apps/nagios/instances/umgebung2/var/rw/icinga.cmd</resource>
<resource
name="umgebung3_pipe">/apps/nagios/instances/umgebung3/var/rw/icinga.cmd</resource>
<resource
name="umgebung4_pipe">/apps/nagios/instances/umgebung4/var/rw/icinga.cmd</resource>
<resource
name="umgebung5_pipe">/apps/nagios/instances/umgebung5/var/rw/icinga.cmd</resource>
<resource
name="umgebung6_pipe">/apps/nagios/instances/umgebung6/var/rw/icinga.cmd</resource>
</files>
</write>
...
</access>
The rest of the access.xml is original or only the paths to the files
are edited. An cleared the cache.
I tried to send a command and found in the logs that icinga matches
the right instances to the hosts.
But there was the following info:
Sending command failed icinga_pipe is not write enabled
That means, that icinga is not accessing my editied access.xml?
Because this pipe is no longer defined in my access.xml.
I edited the global access.xml in icinga-web/etc/conf.d.
But there is another one in icinga-web/app/modules/Api/config/
Which one is the correct one?
Thank you.
Vielen Dank.
Manni
Zitat von Markus Frosch <mar...@lazyfrosch.de>:
> Hello Sascha,
>> We are using in our icinga-cluster the new icinga-web. In the old web-ui
>> there are different instances with specific command-pipes. The web-ui knows
>> which host belongs to which pipe.
>>
>> But in the new icinga-web I got the problem, that the web-ui don?t know
>> which host belongs to which pipe.
>>
>> I tried to configure the pipes in the access.xml, but I cant get the web-ui
>> to execute for instance the reschedule-command.
>>
>> Unfortunately is this configuration not covered by the icinga documentation.
>
> Icinga Web is well aware of the instances inside the IDO - only the
> info is hidden by default. The access.xml allows you the pipes per
> instance - directly or by SSH.
>
> Please see here:
> http://docs.icinga.org/latest/en/icinga-web-config.html#configweb-access
>
> And please always make sure to clear the cache afterwards!
>
> -Markus
>
> --
> Markus Frosch
> mar...@lazyfrosch.de
> http://www.lazyfrosch.de
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> icinga-users mailing list
> icinga-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
