Nagios Support Forum

You're saying between 1.4 and 1.5 Nagvis changed which characters they allowed as passwords? That'd be rather odd... Maybe we just need some form of quoting / escaping.

I believe they've changed how the passwords are handled when authenticating in 1.5.

In a standard auth mechanism for SQL databases, the "@" sign is the separator between user and host for a login. So what I believe is happening is it's attempting to auth "n@gweb"; the app is confused and attempting to auth user "n" at server "gweb". I haven't reviewed the changelogs for 1.5, but the behaviour is consistent with that theory.

I did try to use the standard Linux mechanisms for explicit character definitions (escape characters, single quoting, etc) but none of that worked.

MySQL usernames are a bit odd. The 'server' name in the username is actually a reference to the client, hence root@localhost is user name of root that's connecting from 127.0.0.1. This is kinda creepy if you want to connect from a Windows box that isn't running exchange as you enter an email address that does not exist.

MySQL uses ` (the backtick) for escape, dual-sided (quoting). So perhaps it would just need to be wrapped in that, being passed to MySQL as `n@gweb` instead of straight.

There is an issue as to how this is stored and used on the back-end. Keep in mind this value must be placed as a whole string into the MySQL database. "n@gweb@loaclhost" is unambiguous is the hostname "gweb@loaclhost" or "localhost", perhaps these is a way to escape this for MySQL.

Right, it would be `n@gweb`@localhost, I believe. Possibly even 'n@gweb'@'localhost', depending on how MySQL decides to process things at this layer.

This document and accompanying scripts have now been updated for NagVis 1.5.x.

Hello, I'm newbie to the field and also nagios glpi, is what makes if possible migration between glpi and nagios, please help me to question, if possible, tell me how does your attention and thank you, j 'I am very happy when you answered my question.