[Dbconfig-common-devel] problems converting a package to
dbconfig-common
Torsten Werner
mail.twerner at googlemail.com
Sun Jul 30 15:54:48 UTC 2006
On 7/30/06, Karsten Hilbert <Karsten.Hilbert at gmx.net> wrote:
> Access to the database via UNIX domain sockets is chosen.
Okay probably that was an error, because the database is accessed by
different users: www-data, otrs (via cron), the mta user. That is why
I have tried now tcp/ip on localhost. I have purged the old database
and the db user and reconfigured otrs2 with -plow and the following
answers:
* otrs2/pgsql/app-pass: (password omitted)
* otrs2/app-password-confirm: (password omitted)
* otrs2/pgsql/admin-pass: (password omitted)
* otrs2/pgsql/method: tcp/ip
* otrs2/pgsql/authmethod-admin: ident
* otrs2/pgsql/authmethod-user: password
* otrs2/db/dbname: otrs2
* otrs2/remote/newhost: localhost
* otrs2/remote/host: localhost
* otrs2/db/app-user: otrs2
* otrs2/remote/port:
* otrs2/pgsql/admin-user: postgres
* otrs2/dbconfig-reinstall: true
* otrs2/dbconfig-install: false
* otrs2/pgsql/no-empty-passwords:
Now there is no db user and no database created and there are no
errors in the postgres log. What is wrong here?
Regards,
Torsten
--
http://www.twerner42.de/
More information about the Dbconfig-common-devel
mailing list