Hello --

I went ahead with a re-install of the icinga and icinga-web applications, and 
following your advice I did the installation of the latter with the following 
options:

ac_cs_config="'--prefix=/usr/local/icinga-web' '--with-web-user=apache' 
'--with-web-group=apache' '--with-web-path=/icinga-web' 
'--with-web-apache-path=/etc/httpd/conf.d' '--with-db-type=mysql' 
'--with-db-host=localhost' '--with-db-port=3306' '--with-db-name=icinga_web' 
'--with-db-user=icinga_web' '--with-db-pass=icinga_web' 
'--with-conf-dir=etc/conf.d' '--with-log-folder=log'"

Once the installation was complete, I was able to log into the icinga-web 
interface without issue. So it appears you were right: the 
--with-api-type=driver option was causing the problem.

Per your request, I am including a copy of the databases.xml file for further 
verification.

Thanks again for the help.




________________________________
From: Michael Friedrich [mailto:michael.friedr...@univie.ac.at]
Sent: Tuesday, May 22, 2012 3:30 AM
To: icinga-users@lists.sourceforge.net
Subject: Re: [icinga-users] Problem installing the new icinga-web interface

On 22.05.2012 01:27, Kaplan, Andrew H. wrote:

When I ran the configure script for the application, there was a series of 
options that were used to complete the process. The following is taken from the 
config.status file from the installation directory:

ac_cs_config="'--prefix=/usr/local/icinga-web' '--with-web-user=apache' 
'--with-web-group=apache' '--with-web-path=/icinga-web' 
'--with-web-apache-path=/etc/httpd/conf.d' '--with-db-type=mysql' 
'--with-db-host=localhost' '--with-db-port=3306' '--with-db-name=icinga_web' 
'--with-db-user=icinga_web' '--with-db-pass=icinga_web' 
'--with-conf-dir=etc/conf.d' '--with-log-folder=log' 
'--with-api-subtype=driver' '--with-api-host=localhost' '--with-api-port=3306' 
'--with-api-socket-path=none'"

--with-api-type=driver sounds funny. why did you set that? that goes hand in 
hand with your first connection exception based on the driver. i bet a beer 
that this is the reason your icinga-web can't connect to the database.

btw - post the databases.xml where you configure your db access for further 
verification.




ehm. this is a joke right? 777 for _all_ dirs plus recursive? why did you do 
that dangerous setting?

This change was made in attempt to allow the necessary write access to the 
/usr/local/icinga-web/app/cache directory. If this problem can be solved, I 
will readily
change the permissions back to 644 on both directories.

well i would rather wipe the install again and start from scratch. first 777 
now 644 - something for thedailywtf.com - sorry. that makes the situation to 
debug more critical - what if application expects specific dir permissions you 
have now overridden? there's a reason why there's a make install option ....




The decision to make the directory permissions 777 is simply part of the 
troubleshooting process that I conducted on my end. I do not intend to keep the
permissions as such when the server goes into production.

whoever told you this to troubleshoot, simply forget it. you won't see such 
hints neither in the icinga docs nor the wiki entries we write ourselves.




--
DI (FH) Michael Friedrich

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria

email:     michael.friedr...@univie.ac.at<mailto:michael.friedr...@univie.ac.at>
phone:     +43 1 4277 14359
mobile:    +43 664 60277 14359
fax:       +43 1 4277 14338
web:       http://www.univie.ac.at/zid
           http://www.aco.net

Lead Icinga Core Developer
http://www.icinga.org



The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
<?xml version="1.0" encoding="UTF-8"?>
<ae:configurations xmlns:ae="http://agavi.org/agavi/config/global/envelope/1.0"; xmlns="http://agavi.org/agavi/config/parts/databases/1.0";>
    <!-- Some resources for:
        http://docs.icinga.org/latest/de/icinga-web-config.html#configweb-databases
        https://wiki.icinga.org/display/howtos/databases.xml -->
    
    <ae:configuration>
        <databases default="icinga_web">
            <database name="icinga_web" class="AppKitDoctrineDatabase">

                <!--
                    Doctrine dsn strings:
                    
                    http://www.doctrine-project.org/documentation/manual/1_1/en/introduction-to-connections
                    
                    * Postgre: pgsql://icinga_web:icinga_web@localhost:5432/icinga_web
                    * MySQL: mysql://icinga_web:icinga_web@127.0.0.1:3306/icinga_web
                    * Oracle: oracle://icinga_web:icinga_web@localhost/iweb (iweb is the DSN name on localhost)
                    * Oracle TSNAMES (e.g. /opt/oracle/instantclient_11_2/network/admin/tnsnames.ora):
                            iweb =
                                    (DESCRIPTION =
                                    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.121.0.85)(PORT = 1521))
                                    (CONNECT_DATA =
                                    (SERVER = DEDICATED)
                                    (SERVICE_NAME = XE)
                                    )
                             )
 
                    
                    Please note that some drivers can not be configured through attributes.
                    Just to be safe add attributes to the dsn, e.g.
                        oracle://icinga_web:icinga_web@localhost/iweb;persistent=true
                    
                    (https://dev.icinga.org/issues/2200)
                    
                -->
                <ae:parameter name="dsn">mysql://icinga_web:icinga_web@localhost:3306/icinga_web</ae:parameter>
                
                <!-- Generic credentials  -->
                <!-- <ae:parameter name="username">icinga_web</ae:parameter> -->
                <!-- <ae:parameter name="password">icinga_web</ae:parameter> -->
                
                <!-- DB encoding type -->
                <ae:parameter name="charset">utf8</ae:parameter>
                
                <!--
                    Doctrine_Manager configuration
                -->
                <ae:parameter name="manager_attributes">
                    <!-- This allows lazy loading of the models -->
                    <ae:parameter name="Doctrine_Core::ATTR_MODEL_LOADING">CONSERVATIVE</ae:parameter>
                </ae:parameter>
                
                <!-- The path to our models -->
                <ae:parameter name="load_models">%core.module_dir%/AppKit/lib/database/models/generated</ae:parameter>
                <ae:parameter name="models_directory">%core.module_dir%/AppKit/lib/database/models</ae:parameter>               
                <!-- Oracle specific -->
                <ae:parameter name="date_format"><![CDATA[YYYY-MM-DD HH24:MI:SS]]></ae:parameter>
            
                <!-- Define caching rules for this connection -->
                <ae:parameter name="caching">
                    <!-- enable caching -->
                    <ae:parameter name="enabled">false</ae:parameter>
                    <!-- curerntly supported: memcache and APC -->
                    <ae:parameter name="driver">apc</ae:parameter>
                    <!--
                        Memcache specific
                    <ae:parameter name="memcache_server">localhost</ae:parameter>
                    <ae:parameter name="memcache_port">11211</ae:parameter>
                    -->
                
                    <!-- there aren't many reasons for not using query-caches -->
                    <ae:parameter name="use_query_cache">true</ae:parameter>
                    <!-- result cache: If in doubt, let it out! This caches results from the database -->
                    <ae:parameter name="use_result_cache">true</ae:parameter>
                    <ae:parameter name="result_cache_lifespan">60</ae:parameter>
                </ae:parameter>     
            </database>

            <!-- 
                This part configures the icinga database (destination to ido2db)
                
                If you're using oracle in this case the driver 'icingaOracle' is needed.
                
                - oracle: icingaOracle://icinga:icinga@localhost/iweb
            -->
            <database xmlns="http://agavi.org/agavi/config/parts/databases/1.0"; name="icinga" class="IcingaDoctrineDatabase">
                <ae:parameter name="dsn">mysql://icinga:icinga@localhost:3306/icinga</ae:parameter>
                <!-- Must be removed for oracle databases -->
                <ae:parameter name="prefix">icinga_</ae:parameter>
                <ae:parameter name="charset">utf8</ae:parameter>
                <ae:parameter name="date_format"><![CDATA[YYYY-MM-DD HH24:MI:SS]]></ae:parameter>
                <ae:parameter name="manager_attributes">
                    <ae:parameter name="Doctrine_Core::ATTR_MODEL_LOADING">CONSERVATIVE</ae:parameter>
                </ae:parameter>
                <ae:parameter name="use_retained">true</ae:parameter>

                <ae:parameter name="load_models">%core.module_dir%/Api/lib/database/models/generated</ae:parameter>
                <ae:parameter name="models_directory">%core.module_dir%/Api/lib/database/models</ae:parameter>              
                <ae:parameter name="caching">
                    <!-- enable caching -->
                    <ae:parameter name="enabled">false</ae:parameter>
                    <!-- curerntly supported: memcache and APC -->
                    <ae:parameter name="driver">apc</ae:parameter>
                    <ae:parameter name="use_query_cache">true</ae:parameter>
                </ae:parameter>

            </database>
            <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="etc/conf.d/databases.xml#xpointer(databases/node())">
                <xi:fallback></xi:fallback>
            </xi:include>
        </databases>
    </ae:configuration>
</ae:configurations>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to