Installing/upgrade trac w/ postgresql fails: Password fail

Hi, when I try to install/update my trac instances, I get this error:

Downloading http://ftp.edgewall.com/pub/trac/Trac-0.12.1.tar.gz (2.07 MB) ..
     Received 1024 bytes (0 %)
     Received 212 kB (10 %)
     Received 424 kB (20 %)
     Received 636 kB (30 %)
     Received 848 kB (40 %)
     Received 1.04 MB (50 %)
     Received 1.24 MB (60 %)
     Received 1.45 MB (70 %)
     Received 1.66 MB (80 %)
     Received 1.86 MB (90 %)
     Received 2.07 MB (100 %)
.. download complete.
Found http://www.saddi.com:80/software/flup/dist/flup-1.0.tar.gz in cache ..
 
Python module psycopg is required ..
Installing package python-psycopg ..
Installing package(s) with command apt-get -y --force-yes -f install python-psycopg ..
Reading package lists...
Building dependency tree...
Reading state information...
Package python-psycopg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package python-psycopg has no installation candidate
.. install failed!
.. automatic Python module installation failed
Installing package python-psycopg2 ..
Installing package(s) with command apt-get -y --force-yes -f install python-psycopg2 ..
Reading package lists...
Building dependency tree...
Reading state information...
python-psycopg2 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
.. install complete.
.. done
Now installing Trac version 0.12.1 ..
Database connection failed : DBI connect failed : FATAL: password authentication failed for user "software-consultant.net" 2.
.. failed! See the error message above for the reason why.

This happens with both the current 0.12.2 as well as the previous 0.12.1 version.

I did not manually fiddle with the passwords, nor do I have any problems with the installed application. Any idea what could be wrong or how I could fix it? Kind regards,

Christian

Status: 
Closed (fixed)

Comments

Never mind. Re-setting the (same) password and restarting both apache and postgresql helped. Although I'd like to understand what went wrong...

Perhaps the postgresql password was out of sync with what Virtualmin thought it should be?

Can't tell, the PG password was the same as the domain admin password. I seem to remember that some days ago there was a PG update from Ubuntu.!