My comments, below. Kind regards, Andrés
Andrés González Systems & Infrastructures Supervisor @ Vivocomtech T. +34 91 542 8424 ext. 110 F. +34 91 542 8445 @. agonza...@vivocomtech.eu Skype. ruidoboy Follow us on Facebook ******VivoCom Confidentiality and Security Notice****** This e-mail message is CONFIDENTIAL and may contain legally privileged information. If you are not the intended recipient you should not read, copy, distribute or disclose this e-mail or otherwise use the information in this e-mail. Please telephone, e-mail or fax us immediately and delete the message from your system. The addressee cannot use or quote this e-mail other than for the referenced matter. Security Warning: e-mail is susceptible to delivery failures which may result in non-delivery or delayed delivery, and is also susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any of the above or the consequences thereof. Viruses: Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Este e-mail es CONFIDENCIAL y puede contener información legalmente privilegiada. Si usted no es el destinatario al que va dirigido, no debe leer, copiar, distribuir o comunicar este mensaje, ni hacer uso de la información que contiene. Por favor, llámenos o mándenos un fax o un e-mail y borre este mensaje de su sistema. El destinatario sólo puede usar o citar este e-mail para el asunto mencionado en la referencia. Advertencia de seguridad: los e-mail están expuestos a fallos de envío que pueden dar lugar a que no lleguen a su destinatario o lo hagan con retraso; también están expuestos a corrupciones de su contenido, y pueden ser interceptados o modificados por terceros no autorizados; esta Firma no se hace responsable de ninguno de dichos problemas, ni de las consecuencias que puedan causar. Virus: aunque hemos tomado medidas para asegurarnos de que este correo electrónico y los archivos adjuntos estén libres de virus, recomendamos que, de acuerdo con las buenas prácticas informáticas, el receptor se asegure de que realmente están libres de virus. *********[http://www.vivocom.eu] ***************** El 21/04/2014, a las 14:17, Michael Friedrich <michael.friedr...@gmail.com> escribió: > On 21.04.2014 14:05, Andrés González wrote: >> Hello! >> >> I can't log into Icinga Web (http://mysite/icinga-web) after completing the >> upgrade from version 1.9.3 to 1.11.0. >> >> Icinga is installed in Debian 7.4 and I've used the backport repositories >> and apt in order to upgrade the software. I've kept these files from the >> original installation: >> >> * /etc/icinga/cgi.cfg >> * /etc/icinga/icinga.cfg >> >> I skipped the db configuration process for icinga and icinga_web, since they >> are already configured. After the upgrade, Icinga couldn't start because DB >> versions mismatch (ido2db), so I had to upgrade the db version using: >> >> # mysql -u root -p icinga < >> /usr/share/doc/icinga-idoutils/examples/oracle/upgrade/oracle-upgrade-1.10.0.sql >> # mysql -u root -p icinga < >> /usr/share/doc/icinga-idoutils/examples/oracle/upgrade/oracle-upgrade-1.11.0.sql > > Why in the world would one use the oracle upgrade sqls for his/her mysql > rdbms? o_O > My fault! I actually used the mysql files (sorry, I just copied and pasted the wrong ones): # mysql -u root -p icinga < /usr/share/doc/icinga-idoutils/examples/mysql/upgrade/mysql-upgrade-1.10.0.sql # mysql -u root -p icinga < /usr/share/doc/icinga-idoutils/examples/mysql/upgrade/mysql-upgrade-1.11.0.sql >> >> 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 :-) >> * 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) >> >> mysql> use icinga; >> 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 icinga_dbversion; >> +--------------+----------+---------+---------------------+---------------------+ >> | dbversion_id | name | version | create_time | modify_time >> | >> +--------------+----------+---------+---------------------+---------------------+ >> | 1 | idoutils | 1.11.0 | 2014-02-20 18:35:09 | 2014-04-09 >> 12:26:02 | >> +--------------+----------+---------+---------------------+---------------------+ >> 1 row in set (0.00 sec) > > That's interesting. The oracle upgrade sqls should at least throw an error > when used with mysql, but tbh I've never tested that one. > Again, my fault. I was using the correct mysql upgrade files so… false positive! >> --- >> >> 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! Thank you, Michael! > >> >> Can anybody help me? >> >> Thanks in advance! >> Andrés >> >> *Andrés González* >> Systems & Infrastructures Supervisor @ Vivocomtech <http://vivocomtech.eu> >> T. +34 91 542 8424 ext. 110 >> F. +34 91 542 8445 >> @. agonza...@vivocomtech.eu <mailto:agonza...@vivocomtech.eu> >> Skype. ruidoboy <skype:ruidoboy?chat> >> Follow us on Facebook <http://www.facebook.com/vivocom> >> http://www.vivocomtech.eu/ <http://vivocomtech.eu> >> ******VivoCom Confidentiality and Security Notice****** >> >> This e-mail message is CONFIDENTIAL and may contain legally privileged >> information. If you are not the intended recipient you should not read, >> copy, distribute or disclose this e-mail or otherwise use the information in >> this e-mail. Please telephone, e-mail or fax us immediately and delete the >> message from your system. The addressee cannot use or quote this e-mail >> other than for the referenced matter. Security Warning: e-mail is >> susceptible to delivery failures which may result in non-delivery or delayed >> delivery, and is also susceptible to data corruption, interception and >> unauthorised amendment, and we do not accept liability for any of the above >> or the consequences thereof. Viruses: Although we have taken steps to ensure >> that this email and attachments are free from any virus, we advise that in >> keeping with good computing practice the recipient should ensure they are >> actually virus free. >> >> Este e-mail es CONFIDENCIAL y puede contener información legalmente >> privilegiada. Si usted no es el destinatario al que va dirigido, no debe >> leer, copiar, distribuir o comunicar este mensaje, ni hacer uso de la >> información que contiene. Por favor, llámenos o mándenos un fax o un e-mail >> y borre este mensaje de su sistema. El destinatario sólo puede usar o citar >> este e-mail para el asunto mencionado en la referencia. Advertencia de >> seguridad: los e-mail están expuestos a fallos de envío que pueden dar lugar >> a que no lleguen a su destinatario o lo hagan con retraso; también están >> expuestos a corrupciones de su contenido, y pueden ser interceptados o >> modificados por terceros no autorizados; esta Firma no se hace responsable >> de ninguno de dichos problemas, ni de las consecuencias que puedan causar. >> Virus: aunque hemos tomado medidas para asegurarnos de que este correo >> electrónico y los archivos adjuntos estén libres de virus, recomendamos que, >> de acuerdo con las buenas prácticas informáticas, el receptor se asegure de >> que realmente están libres de virus. >> >> *********[http://www.vivocom.eu] ***************** >> >> >> >> _______________________________________________ >> icinga-users mailing list >> icinga-users@lists.icinga.org >> https://lists.icinga.org/mailman/listinfo/icinga-users > > > -- > DI (FH) Michael Friedrich > > michael.friedr...@gmail.com || icinga open source monitoring > https://twitter.com/dnsmichi || lead core developer > dnsmi...@jabber.ccc.de || https://www.icinga.org/team > irc.freenode.net/icinga || dnsmichi > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
