Re: Debian 13 bacula install failed on dbconfig
Gary Dale <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
On 2025-08-30 10:36, Rob Gerber wrote: > Please note this weird quirk I discovered some time back: postgres < > v14 cannot accept a password > 99 characters. > > I think the error you showed indicated that user bacula wasn't even > created. Perhaps debian repo maintainers adjusted the user under which > bacula would run? > > Another strange thing: because it uses peer authentication by default, > bacula shouldn't even need a password to interact with postgres... If > bacula runs as the user that created the db. > > Props to the Debian maintainers for updating bacula in their repo to v > 15.0.3. I understand the usual stability arguments for leaving old > packages in a repo, but bacula 15.x has some new features that are > quite relevant for today. > > Robert Gerber > 402-237-8692 > [email protected] Here's the error I'm getting. This is after purging bacula and postgresql. I've tried with a new, simpler password, the password I tried the previous installs, and no password (a suggestion I got from someone who didn't reply to the list). An error occurred while installing the database: │ │ │ │ psql: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: password authentication failed for │ │ user "admin" password retrieved from file "/tmp/dbconfig-common.psql_home.auKhC2/.pgpass" . Your options are: │ │ * abort - Causes the operation to fail; you will need to downgrade, │ │ reinstall, reconfigure this package, or otherwise manually intervene │ │ to continue using it. This will usually also impact your ability to │ │ install other packages until the installation failure is resolved. │ │ * retry - Prompts once more with all the configuration questions │ │ (including ones you may have missed due to the debconf priority │ │ setting) and makes another attempt at performing the operation. │ │ * retry (skip questions) - Immediately attempts the operation again, │ │ skipping all questions. This is normally useful only if you have │ │ solved the underlying problem since the time the error occurred. │ │ * ignore - Continues the operation ignoring dbconfig-common errors. │ │ This will usually leave this package without a functional database. │ │ │ │ Next step for database installation: │ │ │ │ abort │ │ retry │ │ retry (skip questions) │ │ ignore │ │ │ │ │ │ <Ok> <Cancel> When I try with ident instead of password authentication, I get: An error occurred while installing the database: │ │ │ │ runuser: user admin does not exist or the user entry does not contain all the required fields . Your options are: │ │ * abort - Causes the operation to fail; you will need to downgrade, │ │ reinstall, reconfigure this package, or otherwise manually intervene │ │ to continue using it. This will usually also impact your ability to │ │ install other packages until the installation failure is resolved. │ │ * retry - Prompts once more with all the configuration questions │ │ (including ones you may have missed due to the debconf priority │ │ setting) and makes another attempt at performing the operation. │ │ * retry (skip questions) - Immediately attempts the operation again, │ │ skipping all questions. This is normally useful only if you have │ │ solved the underlying problem since the time the error occurred. │ │ * ignore - Continues the operation ignoring dbconfig-common errors. │ │ This will usually leave this package without a functional database. │ │ │ │ Next step for database installation: │ │ │ │ abort │ │ retry │ │ retry (skip questions) │ │ ignore │ │ │ │ │ │ <Ok> <Cancel> │ │ _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users