Michael,

here is the /etc/group  file

...
icinga-cmd:x:5003:icinga,apache
...


Thanks


On Tue, Sep 17, 2013 at 4:34 PM, Kenny Noe <knoe...@gmail.com> wrote:

> Micheal.
>
> ls -la of /usr/local/icinga/var/
>
> # ls -la
> total 1156
> drwxrwxr-x.  5 icinga icinga       4096 Sep 17 16:31 .
> drwxr-xr-x. 11 icinga icinga       4096 Sep 17 10:28 ..
> drwxrwxr-x.  2 icinga icinga       4096 Sep  5 00:00 archives
> -rw-r--r--   1 icinga icinga          6 Sep 17 15:08 icinga.lock
> -rw-r--r--   1 icinga icinga       2122 Sep  3 13:04 icinga.log
> -rw-r--r--   1 icinga icinga          5 Sep 17 12:54 ido2db.lock
> -rw-rw-r--   1 icinga icinga          0 Sep 17 15:08 idomod.tmp
> srwxr-xr-x   1 icinga icinga          0 Sep 17 12:54 ido.sock
> -rw-r--r--.  1 icinga icinga     280780 Sep 17 15:08 objects.cache
> -rw-------   1 icinga icinga     432902 Sep 17 16:08 retention.dat
> drwxrwsr-x.  2 icinga icinga-cmd   4096 Sep 17 15:08 rw
> drwxr-xr-x.  3 icinga icinga       4096 Aug 26 11:09 spool
> -rw-rw-r--   1 icinga icinga     433199 Sep 17 16:31 status.dat
>
>
> ls -la of /usr/local/icinga/var/rw
>
>  ls -la
> total 8
> drwxrwsr-x. 2 icinga icinga-cmd 4096 Sep 17 15:08 .
> drwxrwxr-x. 5 icinga icinga     4096 Sep 17 16:33 ..
> prw-rw----  1 icinga icinga-cmd    0 Sep 17 15:08 icinga.cmd
>
>
> Thanks for the reply.
>
> --Kenny
>
>
>
>
>
>
> On Tue, Sep 17, 2013 at 3:18 PM, Kenny Noe <knoe...@gmail.com> wrote:
>
>> More info...  Finally found the log where the error is reported.   The
>> error states:
>>
>> [Tue Sep 17 19:08:56 2013] [info] Sending command failed Could not send
>> command. Check if your webserver's user has correct permissions for writing
>> to the command pipe
>>
>> Can anyone tell me who this "webserver's user" is suppose to be??   Is it
>> hte user that is logged into Icinga-web console?  Is it a user that I
>> created when I installed icinga?  Help!!
>>
>> Thanks --Kenny
>>
>>
>> On Tue, Sep 17, 2013 at 11:30 AM, Kenny Noe <knoe...@gmail.com> wrote:
>>
>>> OK....   I discovered that I had the wrong permission set on the
>>> /usr/local/icinga/var/rw directory and Iicinga.cmd file.  I set these back
>>> to icinga user and icinga-cmd group.  Restarted Icinga-Web but still cannot
>>> run command from GUI.   I'm getting the same error.
>>>
>>> Icinaga-Web 1.9.0
>>> OS - CentOS 6.4
>>>
>>>
>>> Any help?
>>>
>>> Thanks    --Kenny
>>>
>>> ---------- Forwarded message ----------
>>> From: Kenny Noe <knoe...@gmail.com>
>>> Date: Mon, Sep 16, 2013 at 5:52 PM
>>> Subject: Error in Icinga Web GUI
>>> To: icinga-users@lists.sourceforge.net
>>>
>>>
>>> All,
>>>
>>> I'm getting the following error when I'm trying to use the Icinga-Web
>>> Gui to run a command like "Scheduled force service checks"  The error is
>>>
>>> "Could not send command. Check if your webserver's user has correct
>>> permissions for writing to the command pipe."
>>>
>>> I Googled and found references to the Access.xml configuration file and
>>> honestly don't see anything to change.  There is a line referencing the
>>> "/usr/local/icinga/etc/objects" directory.  However I am using the conf.d
>>> directory to hold my different client cfg files.  I have the entries for
>>> "/usr/local/icinga/etc/objects" still commented out.  I changed the
>>> Access.xml to point tot he conf.d dir, restarted Icinga but still could not
>>> run a command from the GUI.
>>>
>>>
>>> What am I missing?   Help!
>>>
>>> Thanks in advance!
>>>
>>> --Kenny
>>>
>>>
>>
>
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to