Don Bessinger [2009-07-19 19:05 -0000]:
> As I posted on July 8, I have a script that clears out log files that
> haven't been accessed in 3 or more days. If a missing log file is the
> problem, I'll make sure that the log files in the /var/log/postgresql
> directory remain untouched.
Right, that's the problem then. I'll fix this for Ubuntu 9.10, but
this is not a fix that meets the criteria for a stable update.
> Meanwhile, here's the output of id postgres:
>
> ~:id postgres
> uid=1001(postgres) gid=1001(postgres) groups=1001(postgres)
Ah, as I expected. Any idea why postgres was removed from the ssl-cert
group? Also, it is in the ID range of normal users, not system users.
Do you happen to use some central account service which also serves
the 'postgres' user (it shouldn't)?
You should be able to start PostgreSQL again after
Don Bessinger [2009-07-19 19:05 -0000]:
> As I posted on July 8, I have a script that clears out log files that
> haven't been accessed in 3 or more days. If a missing log file is the
> problem, I'll make sure that the log files in the /var/log/postgresql
> directory remain untouched.
Right, that's the problem then. I'll fix this for Ubuntu 9.10, but
this is not a fix that meets the criteria for a stable update.
> Meanwhile, here's the output of id postgres: 1001(postgres)
>
> ~:id postgres
> uid=1001(postgres) gid=1001(postgres) groups=
Ah, as I expected. Any idea why postgres was removed from the ssl-cert
group? Also, it is in the ID range of normal users, not system users.
Do you happen to use some central account service which also serves
the 'postgres' user (it shouldn't)?
You should be able to start PostgreSQL again after
sudo adduser postgres ssl-cert
(or disabling SSL in postgresql.conf).
Thanks, Martin