Also you have a problem with mysql user permissions, it's refusing the 
connection for the user icinga on localhost.
Check the grants on mysql


On 13/ago/2010, at 02:34, "Grant Carthew (AU)" <[email protected]> 
wrote:

> Hi All,
> 
> I am a noob to both Linux and Icinga so just want to make sure I fix this 
> problem without adding other problems;
> 
> I have completed the Icinga Quickstart with IDOUtils, works great.
> 
> I have just installed Icinga-Web and got most of it working but am finding 
> the web interface just states loading…  and never displays details.
> 
> I have run a php icingaWebTest and this is the result;
> 
>  
> 
> PHPUnit @package_version@ by Sebastian Bergmann.
> 
>  
> 
> Running post installation checks
> 
>         Checking if cache folders exist
> 
>         Cache folders exist
> 
> .       Testing if web user can write to cache
> 
> touch: cannot touch 
> `/usr/local/icinga-web/etc/..//app/modules/AppKit/cache/testfile.txt': 
> Permission denied
> 
> Web user www-data couldn't write to cache 
> /usr/local/icinga-web/etc/..//app/modules/AppKit/cachePlease check that the 
> either the user www-data or the group www-data has write access to this 
> folder - otherwise icinga-web won't work
> 
> touch: cannot touch 
> `/usr/local/icinga-web/etc/..//app/modules/Web/cache/testfile.txt': 
> Permission denied
> 
> Web user www-data couldn't write to cache 
> /usr/local/icinga-web/etc/..//app/modules/Web/cachePlease check that the 
> either the user www-data or the group www-data has write access to this 
> folder - otherwise icinga-web won't work
> 
> 2 error(s) were reported. Try to fix them? [y/n] (y)y
> 
>         Cache is writeable for web user
> 
> .       Testing log write-access for web user
> 
>         Log-directory is writeable for wwwGroup!
> 
> .       Testing if API Connection is available
> 
> Could not connect to API. The API Connector returned the following message:
> 
> getConnection failed: Database connection failed: SQLSTATE[28000] [1045] 
> Access denied for user 'icinga'@'localhost' (using password: YES))
> 
> Without the icinga-API you will not be able to request any information from 
> icinga!
> 
> FTesting accessibility
> 
>         Checking table for NsmSession...
> 
> PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to 
> allocate 64 bytes) in 
> /usr/local/icinga-web/lib/doctrine/lib/Doctrine/Connection.php on line 1584
> 
> r...@mon:/usr/local/icinga-web/etc/tests#
> 
>  
> 
> So I can see three issues in the result.   I need to change permissions on 
> the /usr/local/icinga-web directory?   Is this correct?   And what 
> permissions do I need to add and what is the best way to do this?
> 
> Also the API Connector has access denied for the icinga user.   What do I 
> need to change in the Modules.xml file?
> 
> Lastly the memory issue.   What is needed here?
> 
>  
> 
> Regards,
> 
>  
> 
> Grant.
> 
>  
> 
> From: Andrew D [mailto:[email protected]] 
> Sent: Thursday, 12 August 2010 2:34 PM
> To: [email protected]
> Subject: Re: [icinga-users] check_commands
> 
>  
> 
> Thanks for your replies.
> 
>  
> 
> It appears it's the empty $ARG1$ i'm sending. also dependant on if i am using 
> check_http with -I or -H.
> 
>  
> 
> Is this as expected?
> 
>  
> 
> To get around this, I've had to define a command definition for each variant 
> of the check_http (for certs, non standard ports, https, keywords etc), which 
> i didn't think i would have to when following 
> http://docs.icinga.org/1.0.2/en/monitoring-publicservices.html (but i'm using 
> -H instead).
> 
>  
> 
> See the Processing line below:
> 
>  
> 
> Returns OK:
> 
> =======================================================
> 
> **** BEGIN MACRO PROCESSING ***********
> 
> Processing: '$USER1$/check_http -H $HOSTADDRESS$'
> 
>   Done.  Final output: '/usr/local/icinga/libexec/check_http -H website.com'
> 
> **** END MACRO PROCESSING *************
> 
> =======================================================
> 
>  
> 
>  
> 
> Returns Critical:
> 
> =======================================================
> 
> **** BEGIN MACRO PROCESSING ***********
> 
> Processing: '$USER1$/check_http -H $HOSTADDRESS$ $ARG1$'
> 
>   Done.  Final output: '/usr/local/icinga/libexec/check_http -H website.com '
> 
> **** END MACRO PROCESSING *************
> 
> **** BEGIN MACRO PROCESSING ***********
> 
> Processing: 'SERVICE ALERT: 
> website.com;HTTP;$SERVICESTATE$;$SERVICESTATETYPE$;$SERVICEATTEMPT$;Name or 
> service not known
> 
> '
> 
> Done.  Final output: 'SERVICE ALERT: website.com;HTTP;CRITICAL;HARD;3;Name or 
> service not known
> 
> '
> 
> **** END MACRO PROCESSING *************
> 
> =======================================================
> 
>  
> 
>  
> 
> Returns OK: 
> 
> =======================================================
> 
> **** BEGIN MACRO PROCESSING ***********
> 
> Processing: '$USER1$/check_http -I $HOSTADDRESS$ $ARG1$'
> 
>   Done.  Final output: '/usr/local/icinga/libexec/check_http -I website.com '
> 
> **** END MACRO PROCESSING *************
> 
> =======================================================
> 
>  
> 
>  
> 
> Regards,
> 
> Andrew
> 
>  
> 
>  
> 
> On Wed, Aug 11, 2010 at 10:00 PM, Michael Friedrich 
> <[email protected]> wrote:
> 
> Andrew D wrote:
> >
> > Not sure if this is the appropriate place for (silly?) questions, but
> > here goes.
> >
> > Is there a way to see the exact command sent from icinga?
> >
> > If i try it from the shell, it works, but in the config file, it
> > doesn't work. So perhaps i have messed up, so i'd like to see the
> > exact command sent and see how it expands the check_http! line.
> >
> > The icinga.log only shows the result of checks. Or can i turn on
> > verbose logging?
> 
> enable debugging, and set the debug_level to fit your needs in icinga.cfg
> 
> Kind regards,
> Michael
> 
> 
> --
> DI (FH) Michael Friedrich
> 
> Vienna University Computer Center
> Universitaetsstrasse 7 A-1010 Vienna, Austria
> 
> email:  [email protected]
> phone:  +43 1 4277 14359
> fax:    +43 1 4277 14279
> web:    http://www.univie.ac.at/zid
> 
> Icinga Core&  IDOUtils Developer
> http://www.icinga.org
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> icinga-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/icinga-users
> 
>  
> 
> 
> - NOTICE FROM DIMENSION DATA LEARNING SOLUTIONS PTY LTD
> This message is confidential, and may contain proprietary or legally 
> privileged information. If you have received this email in error, please 
> notify the sender and delete it immediately.
> 
> 
> Internet communications are not secure. You should scan this message and any 
> attachments for viruses. Under no circumstances do we accept liability for 
> any loss or damage which may result from your receipt of this message or any 
> attachments.
> ******************************************************************************
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> icinga-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to