Re: [Postfixadmin-devel] Setup error
Brought to you by:
christian_boltz,
gingerdog
From: David G. <da...@co...> - 2011-05-06 15:17:52
|
On 6 May 2011, at 15:33, Geoff Shang wrote: > On Fri, 6 May 2011, David Goodwin wrote: > >> Either install phppgadmin or nuke the database from orbit and restart >> the installation - fixing the plpgsql problem first ;-) > > ah yes. I should have thought of this. This should work. > > I uninstalled the package so that dbconfig would get rid of the database. > I didn't notice this the first time I installed, but when I reinstalled > the package this time, I got the following errors: > > sh: getcwd() failed: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf > shell-init: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > sh: getcwd() failed: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > shell-init: error retrieving current directory: getcwd: cannot access > parent directories: No such file or directory > sh: getcwd() failed: No such file or directory > creating postgres user postfixadmin: already exists. > resetting password: success. > sh: getcwd() failed: No such file or directory > creating database postfixadmin: already exists. > dbconfig-common: flushing administrative password I'd guess your shell was 'in' /etc/postfixadmin or something similar which was removed when you nuked the package from orbit. > > It looks like it did all it should do, but the errors are a bit > concerning. There's nothing about these in /var/log/dpkg.log. > > postgres@patronus:~$ psql postfixadmin > psql (8.4.7) > Type "help" for help. > > postfixadmin=# CREATE LANGUAGE plpgsql; > ERROR: language "plpgsql" already exists > Yes, 'create language' is a database wide change... hence it just needs doing once. > Guess it already remembered that from before. > > hmm. Same error, guess i actually need to purge, not just uninstall. > > OK, didn't get the shell errors this time. > You'd probably changed directory! > hmm, still remembered the database. Will have to try removing postgresql > *as well*. > > OK, this time I purged postfixadmin, postgresql-8.4 and dbconfig-common. > I should add that each time I've removed the dump that the uninstall wrote > to /var/tmp. > I suspect that's a dbcommon thing. > This time, the PFA install didn't seem to give comments about he database > already existing, despite the uninstall saying that it was gone. > As expected, /var/lib/postgresql had been nuked. > postgres@patronus:~$ psql postfixadmin > psql (8.4.7) > Type "help" for help. > > postfixadmin=# CREATE LANGUAGE plpgsql; > CREATE LANGUAGE > > OK, everything worked this time. Obviously this will need to get sorted. > Fortunately I'd only just installed the database so nothing was lost, but > this won't always be the case. > >> I'm sure you can fix permissions on postgresql objects, but I can't >> remember the syntax off the top of my head. > > I know almost nothing about PG. I'm more familiar with MySQL, but made > the switch for philosophical reason. I decided the only way to learn it > was to use it, but I've not made the time to actually learn it yet. > >> Sorry, I'm not overly helpful. > > You were very helpful. Thanks. np. David |