Hi Sean, Thanks for your reply.
Putting the hostname in /etc/hosts with the private address does work. That is what we are actually doing now to have our setup working. About your suggestions, I like option b. I could imagine that when prompted for the database user name one could add the '@hostname' information part if he needs it (as in our case) or leave it empty. In such case we apply to logic already in place to find the hostname. Cheers, Jean-christophe On Thu, 22 Oct 2009 11:27:20 +0200 sean finney <[email protected]> wrote: > hi jean-christophe, > > On Thu, Oct 22, 2009 at 10:25:42AM +0200, jean-christophe zulian > wrote: > > Upon installation dbconfig common uses the hostname information to > > create the database user. But later on the db connection won't be > > possible as we will use the private IP to connect to the database. > > Mysql will refuse the connection telling that user > > 'xyz'@'privateIP' is not allowed to connect. If we look at > > mysql.user table we can see the connection for user 'xyz' should be > > coming from the webserver hostname. > > and just to verify: if the hostname in question is associated with > the private address in /etc/hosts on the remote database, everything > works? > > i'll ponder this for a bit and in worst case add a new question. > however, i'm thinking that (a) maybe there's soemthing automagical > that can be done here, and (b) maybe we can hijack the existing user > question (i.e. allow "u...@host" syntax for the response). any > thoughts on that? > > > sean -- Liip AG // Agile Web Development // T +41 26 422 25 11 CH 1700 Fribourg // GPG 0xFC648C61 // www.liip.ch
signature.asc
Description: PGP signature
