On Wed, Feb 25, 2009 at 08:36:37AM +0100, Morten Brekkevold wrote:
On Mon, 23 Feb 2009 15:27:58 +0000 Tim Chown tjc@ecs.soton.ac.uk wrote:
Hi again :)
So we upgraded nav, and before running the sql script we tried to run the merge script, and it seems to fail because it thinks there already is a database called nav:
postgres@nwtraffic:/usr/share/doc/nav/sql$ sh mergedb.sh Creating database nav, owned by nav createdb: database creation failed: ERROR: database "nav" already exists
Hi Tim,
Why did you try to do this manually? Did the Debian package not fix this for you already?
Hmmm. I guess the cause of my confusion (and the possible mistake) is that I read the new README notes and these talk about the upgrade script and running the merge, etc.
Hindsight of course makes thing easy, but I guess I was trying to be too diligent in reading the upgrade notes and your mail on 22nd Jan about the new v3.5 release and not realising that your debian package simply does it all. Having re-read your mail of 18th Feb I see this now ("For the automatically database upgrade to complete successfully you need to..."). I think the info from the first release notes were stuck in my mind as something important to do.
Having fixed up the apache config all now seems well. We'll give it a whirl and send any feedback as usual.
Sometimes it pays not to think too much it seems :)
Thanks again,