On Tue, Sep 09, 2008 at 03:31:00PM +0200, Morten Brekkevold wrote:
On Tue, 9 Sep 2008 13:58:07 +0100 Tim Chown tjc@ecs.soton.ac.uk wrote:
Is there any gotcha to doing a straight aptitude update from a previous version (3.4.1) to the new version on a live system?
There shouldn't be. But make sure to do a "/etc/init.d/apache2 force-reload" after the upgrade, to make sure Apache/mod_python is using the new NAV code.
The upgrade seemed to work fine.
I followed the info about the sql update but got errors:
# psql -f 3.4.2.sql manage nav Password for user nav: BEGIN CREATE RULE CREATE RULE CREATE RULE psql:3.4.2.sql:46: ERROR: syntax error at or near "WHERE" at character 1 psql:3.4.2.sql:46: LINE 1: WHERE key='serviceid' AND value=old.serviceid::text; psql:3.4.2.sql:46: ^ ROLLBACK
We have psql 8.1, but I assumed the patch was required because we did install 3.4.1 from scratch. The comment in the patch file also says "NAV 3.4.1 and 3.4.1 were shipped with a manage.sql..." which I assume should say "NAV 3.4 and 3.4.1".
Is the patch failing because we don't need it, or some other issue? :)
Thanks,
On Tue, 9 Sep 2008 16:13:51 +0100 Tim Chown tjc@ecs.soton.ac.uk wrote:
The upgrade seemed to work fine.
I followed the info about the sql update but got errors:
You don't need to do that when using the Debian packages, they automatically perform the SQL schema upgrade for you. (That's assuming you didn't decline the offer to do so at the time you first installed the nav package).
Of course, in your case, the SQL schema upgrade failed both during package upgrade and during your manual attempt.
psql:3.4.2.sql:46: ERROR: syntax error at or near "WHERE" at character 1 psql:3.4.2.sql:46: LINE 1: WHERE key='serviceid' AND value=old.serviceid::text; psql:3.4.2.sql:46: ^ ROLLBACK
We have psql 8.1, but I assumed the patch was required because we did install 3.4.1 from scratch. The comment in the patch file also says "NAV 3.4.1 and 3.4.1 were shipped with a manage.sql..." which I assume should say "NAV 3.4 and 3.4.1".
Is the patch failing because we don't need it, or some other issue? :)
The SQL script fails because of a typo, i.e. a line was appended after a line that it was meant to replace, causing an SQL error.
For more details on this bug, see https://bugs.launchpad.net/nav/+bug/260330 , which is part of NAV 3.4.3, slated for release next week.
You can fix it yourself by simply deleting the first of the two WHERE-lines, as commented by Kristian Klette here: https://bugs.launchpad.net/nav/+bug/260330/comments/1
-
Morten Brekkevold -
Tim Chown