Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

On Tue, 2016-08-16 at 21:20 +0200, Paul Gevers wrote: > The intent is that dbconfig indeed support identd based > authentication. I see.. hmm well wouldn't be my first choice for security reasons,... but I think it should be possible to get "full" support even with supporting identd as well. >

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hey. On Fri, 2016-08-19 at 09:50 +0200, Paul Gevers wrote: > Would you agree with me, i.e. do you know the following to be true, > that > peer authentication requires Unix socket (localhost) This, I think, is the case: https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html peer

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hi Christoph, Would you agree with me, i.e. do you know the following to be true, that peer authentication requires Unix socket (localhost) and that Unix socket requires peer identification for PostgreSQL? I tried the other day to have password authentication via the Unix socket, but that

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hi On 15-08-16 23:05, Christoph Anton Mitterer wrote: > On Mon, 2016-08-15 at 22:11 +0200, Paul Gevers wrote: > But in these specific cases (i.e. installation to a remote system), the > UNIX user under which we run psql/etc. locally shouldn't matter at al > (that is unless the remote DB server

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

On Mon, 2016-08-15 at 22:11 +0200, Paul Gevers wrote: > Your second e-mail to this bug contained some information where you > tried to enable TCP login and it still failed for you because the > credentials were tried to be created with the $dbuser login. As TCP > is > the default answer, I am even

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

On Mon, 2016-08-15 at 22:11 +0200, Paul Gevers wrote: > > - create only those objects as DB-admin-user, that need to be (e.g. > >   other DB-users, the (empty) DBs, and so n)... and everything else > >   (including populating the DBs) as the DB-(non-admin)-user > > > > AFAIU, you do the 2nd? > >

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hi On 15-08-16 00:02, Christoph Anton Mitterer wrote: > On Sun, 2016-08-14 at 11:30 +0200, Paul Gevers wrote: > In general though, I think that any auto-magical fall-back from a user- > specified "use sockets" to TCP (or vice versa) is not something that > should be even tried, regardless of

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hey Paul. On Sun, 2016-08-14 at 11:30 +0200, Paul Gevers wrote: > Control: clone -1 -2 -3 ouch... I didn't want to cause you so much work ;) > And just to be sure, I assume everything we discuss here is done with > the backported version of dbconfig. There are too many changes since > Jessie to

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Control: clone -1 -2 -3 Control: retitle -1 psql ident without existing sys-user unclear error Control: tags -1 -moreinfo Control: retitle -2 psql incorrectly falls back to TCP in ident case Control: tags -1 -moreinfo Control: retitle -3 psql alters credentials with dbuser iso dbadmin Hi

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hey. See below... went actually much faster than I'd have expected. I think it already shows the possible problem that happens: >populating database via sql...  warning: ident method specified but local >account doesn't exist. >warning: ident method specified but local account doesn't exist.

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Hi Christoph, I am going to bed, now, so a short answer. On 13-08-16 22:45, Christoph Anton Mitterer wrote: > Was the information above already enough for you? > If not I can stop the services, make some temp DB for a test and run it > with dbc_debug=true I will try to reproduce with the

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

On Sat, 2016-08-13 at 22:19 +0200, Paul Gevers wrote: > Sorry for taking a while before responding. Holiday season. No worries.. > I couldn't quickly find under which user > the > program icinga is running Mutliple things come here together: - the user/groups under which the icinga daemon itself

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Control: tags -1 moreinfo Hi Christoph, Sorry for taking a while before responding. Holiday season. On Tue, 19 Jul 2016 01:35:13 +0200 Christoph Anton Mitterer wrote: > I've just checked the whole package again, and nothing in it seems to > so contain anything about tcp

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Control: reassign -1 dbconfig-common Control: retitle -1 dbconfig configuration fails with unix sockets I've just checked the whole package again, and nothing in it seems to so contain anything about tcp or UNIX sockets... so it rather seems to me that this might be a problem in dbconfig, thus

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Even if one enables TCP, it doesn't work: 2016-07-12 18:45:55 CEST [8172-2] icinga@template1 LOG:  connection authorized: user=icinga database=template1 SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, compression=off) 2016-07-12 18:45:55 CEST [8202-1] [unknown]@[unknown] LOG:  

Bug#830888: icinga2-ido-pgsql: dbconfig configuration fails with unix sockets

Package: icinga2-ido-pgsql Version: 2.4.10-1~bpo8+1 Severity: important Hi. On jessie with the backports package,... when selecting to use unix sockets during dbconfig, it apparently still tries to create the DB/etc. using TCP and an error appears: An error occurred while installing the