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 <cales...@scientia.net> wrote: > 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 reassigning and > kindly asking its maintainers to have a look. I agree with you that the issue you experience is more likely in dbconfig than in icinga. I have multiple question: For your initial question: I couldn't quickly find under which user the program icinga is running, but are Unix sockets appropriate? I.e. I found a hint it may be running under the nagios user, then Unix sockets only work if the database user is called the same obviously. (The maintainers of icinga believe that the default authentication scheme should be password (thus TCP) as can be seen in the config file of icinga2-ido-pgsql. One of my packages (cacti) doesn't even know itself how to run via an Unix socket, so the dbconfig question is misleading there (but luckily for the package ignored anyways), maybe icinga has a similar "issue". If you leave the password for the icinga user blank, dbconfig will create one for you, as if you are using the password scheme, you need a password obviously. The debconf question should have told you. Now, when I try to install icinga2-ido-pgsql (with normal priority), the package installs fine. So can you please be more verbose on what you did and answered in the TCP case, such that I can reproduce? Please also run "debconf-show icinga2-ido-pgsql" and show us the output (in the situation where you have the issue). Also, if you can reproduce the issue, running the installation with export dbc_debug=true is also very helpful (mind you, you may have to hide your passwords before you send the response). Paul
signature.asc
Description: OpenPGP digital signature
