Is there any chance that it can be added to the demo system at http://www.icinga.org ?

Next time please chose the mailinglists, blogpost answers are a bit unusal for support ;)

But yes you are right – this connection handler needs to be adapted the right way fitting your DB connection parameters. I’m not sure why this is not pointed out exactly in the install-fromscratch.txt but I will hand that over for the real documentation then.

But glad to hear you got it working. The next release will include an installscript, but for this alpha release there was not really time to add this.

changing the database.xml
from
mysql://icinga_web:icinga_web@127.0.0.1:3306/icinga_web
to
mysql://icinga:mypsw@127.0.0.1:3306/icinga_web

solved the problem now. Tried that before. Don’t know why it now helped.

Tested also with a own index.php with an echo. This works with the given configfiles from pastebin.

So I don’t think this is the error. Somethin with Agavi is wrong or my configuration?

http://de.pastebin.ca/1653032 database.xml
- I will use the icinga-mysql-user to connect to icinga_web-database. Do the icinga_web:icinga_web in the dsn-paramter keep as it is, or must I change it from

mysql://icinga_web:icinga_web@127.0.0.1:3306/icinga_web

to

mysql://icinga:mypsw@127.0.0.1:3306/icinga_web

http://de.pastebin.ca/1653037 icinga.xml
- I set a absolut path for .

@Michael Friedrich
thanks for support so far

I think I found the problem. Tested to add echo “test” in the index.php. Test1 shows up in webinterface, test2 not. Seems that something is wrong with Agavi. Ideas?

// +—————————————————————————+
// | An absolute filesystem path to the agavi/agavi.php script. |
// +—————————————————————————+
require (dirname(dirname(__FILE__)). ‘/lib/agavi/src/agavi.php’);

// +—————————————————————————+
// | An absolute filesystem path to our app/config.php script. |
// +—————————————————————————+
// Not needed, we work with bootstrap events
require(‘../app/config.php’);

echo ‘test1′; // showes up

// +—————————————————————————+
// | Initialize the framework. You may pass an environment name to this method.|
// | By default the ‘development’ environment sets Agavi into a debug mode. |
// | In debug mode among other things the cache is cleaned on every request. |
// +—————————————————————————+
Agavi::bootstrap(‘development’);

echo ‘test2′; // don’t showes up

// Setting the running context to web …
AgaviConfig::set(‘core.default_context’, ‘web’);

// Initialize the appkit framework
AppKit::bootstrap();

// +—————————————————————————+
// | Call the controller’s dispatch method on the default context |
// +—————————————————————————+

// AppKitEventDispatcher::getInstance()->triggerSimpleEvent(‘agavi.dispatch’, ‘Agavi is starting its container’);

AgaviContext::getInstance(‘web’)->getController()->dispatch();

// AppKitEventDispatcher::getInstance()->triggerSimpleEvent(‘agavi.afterdispatch’, ‘Agavi stoped, response is served’);

exit (0);

There is a important setting in the idomod.cfg file. At the end of this config file is the option “config_output_option” which has to be set to 3.
After restarting all the deamons icinga will write ALL data from the configs to the db!

< IfModule mod_rewrite.c>
< /IfModule>

in yout config. maybe you pastebin the content. if you are talking about a 500 error you should at least find those entries in you error logs. maybe the httpd config is set not to output any logs?

i also would recommend creating a new file icinga-web.conf and put it into conf.d directory, with the provided information (alias and allowoverride).