On 21.04.2014 14:33, Andrés González wrote:
With that I managed to get Icinga running again. Here are some
useful details about my installation:
* Classic UI is fully working
* Ido2db is up and running
I doubt that. Logs?
Based on my previous corrections, I hope that makes sense now :-)
There's a reason why I am asking for logs - others might have the same
issue, and require to see how the icinga->idomod->ido2db handshake works
correctly. "up and running" doesn't describe much.
The wiki holds additional details on testing idoutils and web btw.
* MySQL users (icinga and icinga_web) are present with the right
credentials. I can log into MySQL shell and their correspondent
databases using username/password
* Icinga Web users are also present and they seem to have the right
settings
When I try to log into Icinga Web, I get two error messages:
"Request failed. The server encountered an error: Internal
Exception, check your logs!"
"Login failed. Please verify your input and try again!"
Checking /var/log/icinga-web/debug-2014-04-21.log shows this info:
[Mon Apr 21 11:21:46 2014] [debug] Auth.Dispatch: Starting
authenticate (username=myuser)
[Mon Apr 21 11:21:46 2014] [info] Auth.Dispatch: Converting username
to lowercase
While /var/log/icinga-web/icinga-web-2014-04-21.log show the next lines:
[Mon Apr 21 10:25:00 2014] [fatal]
Auth.Provider.HTTPBasicAuthentification: No value found for
auth_name/http_uservar
[Mon Apr 21 10:25:00 2014] [fatal]
Auth.Provider.HTTPBasicAuthentification: No value found for
auth_type/http_typevar
I even thought that maybe the db version for Icinga Web had to be
updated:
---
mysql> use icinga_web;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select * from nsm_db_version;
+----+-------------------+---------------------+---------------------+
| id | version | modified | created |
+----+-------------------+---------------------+---------------------+
| 1 | icinga-web/v1.9.0 | 2014-02-21 11:39:33 | 2014-02-21 11:39:33 |
+----+-------------------+---------------------+---------------------+
1 row in set (0.00 sec)
So you did not update your icinga_web database schema. In that
specific case, you're using an old database schema with a newer
software version (and there were changes).
Well that's interesting: when you install and update icinga from
backport repositories (Debian 7.4), you get the files in order to
upgrade the icinga db schema in the following path:
/usr/share/doc/icinga-idoutils/examples/mysql/
But if you follow the same process for icinga-web, there's no hint
about the upgrade files. I could find them in
https://github.com/Icinga/icinga-web/releases/download/v1.11.0/icinga-web-1.11.0.tar.gz.
Path is icinga-web-1.11.0/etc/schema/updates/mysql/. I guess I need to
run the next commands based on the current icinga-web version, but let
me know if I'm missing something:
# mysql -u root -p icinga_web < mysql_v1-9-0_to_1-9-1.sql
# mysql -u root -p icinga_web < mysql_v1-9-1_to_1-10-0.sql
# mysql -u root -p icinga_web < mysql_v1-10-0_to_1-10-1.sql
(there's no update further update from 1-10-1)
It's relatively uncommon that people disable the dbconfig-common
mechanism. The icinga-web Debian package doesn't ship the sqls involved
within the /usr/share/doc/ location, but rather only in the dbconfig
common path. dpkg -X <package-name> will show the same.
http://anonscm.debian.org/gitweb/?p=pkg-nagios/pkg-icinga-web.git;a=blob;f=debian/icinga-web.dirs;h=22f31b4df3a6dbd6e0c119f17a2dbb6a3b4cc062;hb=HEAD
Feel free to create a bug on the debian bug tracker if that's missing in
either README or file destination in your opinion.
---
But I could find a SQL file to import the new schema for this version.
After reading every bit of documentation related to icinga-web
installation and upgrade and many forum posts, I couldn't reach the
reason for this issue!
- import your mysql backup from yesterday
- stop ido2db
- re-apply icinga idoutils upgrade schemas 1.10 and 1.11 for MYSQL
- start ido2db, restart icinga
- apply icinga web upgrade schemas until 1.11 for MYSQL
- clear web cache
If you could confirm if I'm missing upgrade files for icinga-web I'll
proceed as you suggested!
Does it work after fixing the icinga web schema upgrade shown above?
--
DI (FH) Michael Friedrich
[email protected] || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
[email protected] || https://www.icinga.org/team
irc.freenode.net/icinga || dnsmichi
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
