Hi, It's the fact that Nagios uses the nagios user and the user uses Shinken Shinken. To solve the problem it is necessary to operate with the user nagios.
Best regard Le 28/09/2011 12:02, Jörg Schulz a écrit : > Hi > > I got the following message when i stop the "nagios" process and only > running shinken > > You are not authorized to submit the specified command. > > Read the section of the documentation that deals with authentication and > authorization in the CGIs for more information. > > Return from whence you came > > I know we cant use the cgi.cfg or is this a problem with the nagios.cmd ? > > /var/lib/shinken/rw/* has shinken user and group as the rights > > Version > shinken-arbiter : 0.6.5+ with pyro : 3.15 > > Greetings > /Jörg > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Shinken-devel mailing list > Shinken-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shinken-devel > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
