After installing postgresql and running emerge --config =postgresql-8.0.3 I can
start and use postgresql with no problem, but when I start or stop it using
/etc/init.d/postgresql I get a message like this:
yoda ~ # /etc/init.d/postgresql start
* Starting PostgreSQL ...
su: Authentication service cannot retrieve authentication info.
(Ignored) [ ok ]
yoda ~ #
As I said, I can use postgresql and it does not appear to be a real problem just
an ugly message.
This forum post has a solution:
Maybe it should be added to the install script?
Steps to Reproduce:
I ran into this as well after emerging 8.1.1. This same problem prevented setting a password on the postgres user account and ssh'ing into the postgres user (even using keys).
I'm glad Kim included the link to that forum post. Simply running '/usr/sbin/pwconv' as root fixed all these problems.
From 'man pwconv':
"pwconv creates shadow from passwd and an optionally existing shadow."
It appears that /etc/shadow isn't being set up properly in the ebuild.
The actual dev-db/postgresql ebuilds correctly set up their groups and users.
A solution posted in the forums is to simply run '/usr/sbin/pwconv' as root to fix this, but that isn't the ebuilds job.
Best regards, CHTEKK.
> The actual dev-db/postgresql ebuilds correctly set up their groups and users.
I haven't run into the problem in recent installs, so I assume that you mean the ebuilds have been fixed to address the problem.
> A solution posted in the forums is to simply run '/usr/sbin/pwconv' as root to
> fix this, but that isn't the ebuilds job.
If you are implying that users should intuitively know to run /usr/sbin/pwconv after an install, you're off your rocker.
However, like I already stated above, it appears the problem has already been fixed, as I've installed the latest version of postgresql on several new machines without encountering this issue.
Reopen to duplicate.
*** This bug has been marked as a duplicate of 98406 ***