Sorry for the delay on the release, we had to catch several technical issues next to OSMC.
We decided to split the releases into Icinga Core and Icinga Web. Therefore you will find two several packages to download and install.
The Core contains the Icinga API and IDOUtils which are needed for a functional Web this time. Make sure to download Icinga 1.0 RC1 and install it with IDOUtils for MySQL, the API will be installed automatically in share/icinga-api/
The Icinga Web depends on the API – you have to point the config to the actual install path. There are also several prerequisites and dependencies to resolve, so please catch on the instructions in doc/install-fromscratch.txt and do not hesitate to ask questions on the mailinglists and/or report any issues/bugs on our dev tracker.
Please keep in mind that this is an alpha release and be patient while we are working on future versions! :-)
Better late than never! either way you look at it, a job well done by all the team! thanks…
Finally got it installed. Can’t say it was easy but after all this is an alpha. Looks great I must say. Shows a lot of promise and you’re already miles ahead of the original nagios web ui.
It will indeed be exciting what you guys will come up with next.
Cheers
Dag
I’m faced with the problem, that the new webui does not show any service/host information. The Log Section on the bottom of the side contains information. Whats wrong?
please open up an issue on the dev tracker for the web.
https://dev.icinga.org/projects/icinga-web/issues
Will do! Thank you…
Great work, looks very promising!
Gibts irgendwo auch mal neue Screenshots davon?
Please have a look at this previous post!
http://www.icinga.org/2009/10/26/teasers-for-future-web-ui/
It takes me three hours to get it up and running. But for some reason, my machine doesn’t always load css files, and running very slow for this site, and always displaying ‘loading’ in the top frame of the page. I tested in IE8, FF3.0.15, chrome3.0.195.27. any idea?
would be interesting what kind of machine you are using. css problems may relate to wrong apache configs. this problem reminds me of the problems i had before on wednesday while testing the install by myself. i didn’t have set the alias icinga-web and the AllowOverride All confition – as now described in install-fromscratch.txt
My problem with this alpha is, that I get an HTTP 500 when I go to http://server/icinga-web/ . I checked the .htaccess but it is correct and mod_rewrite is enabled (tested with mod_rewrite condition to google.de).
Checked also the doc/install_fromscratch.txt and do the described things more than one time. But no chance.
The httpd-Log shows also no errors. Can somebody give a hint, where the problem is?
I installed the
- Web GUI @ /usr/local/icinga-web
- API 1.0 RC @ /usr/local/icinga
API is running good and the normal web-interface is running under http://server/icinga with no problems.
httpd.conf:
Alias /icinga-web “/usr/local/icinga-web/pub”
Options None
AllowOverride All
Order allow,deny
Allow from all
htaccess:
DirectoryIndex index.php
Options -MultiViews -Indexes +FollowSymLinks
Order allow,deny
Allow from all
RewriteEngine On
RewriteBase /icinga-web
RewriteRule ^$ index.php?/ [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule (.*) index.php?/$1 [QSA,L]
AcceptPathInfo On
i’m missing the
< 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).
Here is more Info: http://de.pastebin.ca/1652875
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);
mh for what I can tell I think your rewritebase in .htaccess is wrong – just use / instead of /icinga-web (since you are pointing to icinga-web already with your apache settings)
changed in the .htacess to /, but then I get a 404 Not found error:
[Mon Nov 02 14:45:25 2009] [error] [client 192.168.194.150] script ‘/var/www/html/index.php’ not found or unable to stat
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
ok, found the problem, after some debugging …
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.
Also found out, that without
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_USER_DEPRECATED
in the php.ini with PHP Version 5.3.0 the web_gui get some javascript-errors and don’t show up data like hosts.
@Andreas
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.
Wohoo… Got the new icinga interface working!!!
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!
Great news!
Is there any chance that it can be added to the demo system at http://www.icinga.org ?