Project

General

Profile

Unclear password prompt when installing from Debian Bullseye Backports packages -- Resolved

Added by Ken Johnson 12 months ago

I am trying to install Redmine on a test virtual machine from Debian Bullseye (11) Backports packages.

I have already installed Postgresql, that installation reported:

Ver Cluster Port Status Owner Data directory Log file
13 main 5432 down postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log

After the install, I started the postgres service.

My install command for Redmine is:

aptitude install -s redmine-pgsql -t bullseye-backports

I selected the use of dbconfig. After being prompted for the hostname, I get an input box labeled 'Configuring Redmine', which prompts me to fill in a field labeled 'Password confirmation'. That's fine, but which password is it?

Thank you for any help you can provide.


Replies (2)

RE: Unclear password prompt when installing from Debian Bullseye Backports packages - Added by Ken Johnson 12 months ago

'dpkg-reconfigure redmine' re-runs the package configuration actions, but with many more prompts for input. Those additional prompts include a postgresql user name and password, and then the 'Password confirmation' prompt for the postgres password. I speculate that the various possible prompts have priority levels assigned when the dpkg is assembled, and the 'Password confirmation' prompt incorrectly does not have the same priority level as the user name and password prompts.

Regards,

Ken

RE: Unclear password prompt when installing from Debian Bullseye Backports packages - Added by Ken Johnson 12 months ago

The configuration saved after 'dpkg-reconfigure redmine' allowed me to connect to the redmine main page when using

sudo -u www-data REDMINE_INSTANCE=default rackup -E production

Additional configuration as described in /usr/share/doc/redmine/README.Debian for the Apache webserver let me connect to the redmine instance at mynode.mydomain.tla/redmine (fqdn obscured) and perform basic configuration. I believe my original query is resolved.

    (1-2/2)