sql-ledger-users

[SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

I've been putting off the upgrade as long as I could, but I finally gave
it a go. However, when I log in after following the instructions, I get
this error:

Error!

drop trigger del_recurring ON oe
ERROR: trigger "del_recurring" for table "oe" does not exist

and now when I try to log in it tells me Login disabled. Some help would
be greatly appreciated.
-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Are we not men? 
 
 
 
 

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
> I've been putting off the upgrade as long as I could, but I finally gave
> it a go. However, when I log in after following the instructions, I get
> this error:
> 
> Error!
> 
> drop trigger del_recurring ON oe
> ERROR: trigger "del_recurring" for table "oe" does not exist

Well, I just tried again and it worked (after I deleted the nologin
file). But then I found that my nightly backups using pg_dump and
restores to a mirror system stopped working about a week ago. I'm
getting these messages:

pg_restore: [tar archiver] could not open TOC file for input: No such
file or directory

The line that triggers this message is:
pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup

The funny thing is that the backup file suddenly went from 4.1MB in size
to 9.3MB on the day it stopped working. I had upgraded postgres from
8.0.13 to 8.0.15 a few days previous, and then we had a power failure
and when the machine rebooted, these problems started.

So, since my mirror was a week out of date, I got a backup file from
System -> Backup -> Save to file, and restored that to my mirror system.
Then when I logged in I got this error message:

Upgrading to Version 2.8.15 ... 
Error!
create table cargo (id int not null, trans_id int not null, package
text, netweight float4, grossweight float4, volume float4)
ERROR: relation "cargo" already exists

I REALLY need to get this working again. Any help will be greatly
appreciated.

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Respect is a rational process   -- McCoy, "The
 Galileo Seven", stardate 2822.3 
 
 
 

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Michael H. <mh...@it...>]

Not a complete answer but we've seen the TOC error after upgrades as  
some of the rights get reset and the user the dump is executing under  
doesn't have access.


Thanks,

Michael

On Jun 14, 2008, at 11:14 AM, Stuart Luppescu wrote:

> On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
>> I've been putting off the upgrade as long as I could, but I  
>> finally gave
>> it a go. However, when I log in after following the instructions,  
>> I get
>> this error:
>>
>> Error!
>>
>> drop trigger del_recurring ON oe
>> ERROR: trigger "del_recurring" for table "oe" does not exist
>
> Well, I just tried again and it worked (after I deleted the nologin
> file). But then I found that my nightly backups using pg_dump and
> restores to a mirror system stopped working about a week ago. I'm
> getting these messages:
>
> pg_restore: [tar archiver] could not open TOC file for input: No such
> file or directory
>
> The line that triggers this message is:
> pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup
>
> The funny thing is that the backup file suddenly went from 4.1MB in  
> size
> to 9.3MB on the day it stopped working. I had upgraded postgres from
> 8.0.13 to 8.0.15 a few days previous, and then we had a power failure
> and when the machine rebooted, these problems started.
>
> So, since my mirror was a week out of date, I got a backup file from
> System -> Backup -> Save to file, and restored that to my mirror  
> system.
> Then when I logged in I got this error message:
>
> Upgrading to Version 2.8.15 ...
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists
>
> I REALLY need to get this working again. Any help will be greatly
> appreciated.
>
> -- 
> Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> University of Chicago (^_^)/ CCSR
> 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> Respect is a rational process   -- McCoy, "The
>  Galileo Seven", stardate 2822.3
>
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Paul T. <pt...@wa...>]

Upgrading and restoring at the same time?  Seems a bit tricky to begin with.

If all else fails first restore to same version then do upgrades later. But
maybe this helps:

Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts before
letting postgres or SQL-Ledger have a second go?
If not i strongly suggest you do that, saved my ass in the past getting from
a blown 2.2 to a new 2.4 iirc..


2008/6/14 Michael Hasse <mh...@it...>:

> Not a complete answer but we've seen the TOC error after upgrades as
> some of the rights get reset and the user the dump is executing under
> doesn't have access.
>
>
> Thanks,
>
> Michael
>
> On Jun 14, 2008, at 11:14 AM, Stuart Luppescu wrote:
>
> > On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
> >> I've been putting off the upgrade as long as I could, but I
> >> finally gave
> >> it a go. However, when I log in after following the instructions,
> >> I get
> >> this error:
> >>
> >> Error!
> >>
> >> drop trigger del_recurring ON oe
> >> ERROR: trigger "del_recurring" for table "oe" does not exist
> >
> > Well, I just tried again and it worked (after I deleted the nologin
> > file). But then I found that my nightly backups using pg_dump and
> > restores to a mirror system stopped working about a week ago. I'm
> > getting these messages:
> >
> > pg_restore: [tar archiver] could not open TOC file for input: No such
> > file or directory
> >
> > The line that triggers this message is:
> > pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup
> >
> > The funny thing is that the backup file suddenly went from 4.1MB in
> > size
> > to 9.3MB on the day it stopped working. I had upgraded postgres from
> > 8.0.13 to 8.0.15 a few days previous, and then we had a power failure
> > and when the machine rebooted, these problems started.
> >
> > So, since my mirror was a week out of date, I got a backup file from
> > System -> Backup -> Save to file, and restored that to my mirror
> > system.
> > Then when I logged in I got this error message:
> >
> > Upgrading to Version 2.8.15 ...
> > Error!
> > create table cargo (id int not null, trans_id int not null, package
> > text, netweight float4, grossweight float4, volume float4)
> > ERROR: relation "cargo" already exists
> >
> > I REALLY need to get this working again. Any help will be greatly
> > appreciated.
> >
> > --
> > Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> > University of Chicago (^_^)/ CCSR
> > 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> > Respect is a rational process   -- McCoy, "The
> >  Galileo Seven", stardate 2822.3
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > ---
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > sql-ledger-users mailing list
> > sql...@li...
> > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 日, 2008-06-15 at 00:33 +0200, Paul Tammes wrote:
> Upgrading and restoring at the same time?  Seems a bit tricky to begin
> with.
> 
> If all else fails first restore to same version then do upgrades
> later. But maybe this helps:
> 
> Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts
> before letting postgres or SQL-Ledger have a second go?
> If not i strongly suggest you do that, saved my ass in the past
> getting from a blown 2.2 to a new 2.4 iirc..

I downgraded back to 2.6.27, restored from the backup, and everything
was fine. Then I tried upgrading to 2.8.1 and got the same message as
before:
Error!
create table cargo (id int not null, trans_id int not null, package
text, netweight float4, grossweight float4, volume float4)
ERROR: relation "cargo" already exists

I tried over and over, but I keep getting the same message. This is
getting frustrating.

Paul, where do I get those upgrade scripts you mention?

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Denver, n.:  A smallish city located just below
 the `O' in Colorado. 
 
 
 

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Paul T. <pt...@wa...>]

in the /sql dir there are sripts named Pg-upgrade-2.0.8-2.2.0.sql etcetera
Start on the one you have and work up to actual version: bos is now part of
the family ;-)

2008/6/22 Stuart Luppescu <sl...@cc...>:

> On 日, 2008-06-15 at 00:33 +0200, Paul Tammes wrote:
> > Upgrading and restoring at the same time?  Seems a bit tricky to begin
> > with.
> >
> > If all else fails first restore to same version then do upgrades
> > later. But maybe this helps:
> >
> > Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts
> > before letting postgres or SQL-Ledger have a second go?
> > If not i strongly suggest you do that, saved my ass in the past
> > getting from a blown 2.2 to a new 2.4 iirc..
>
> I downgraded back to 2.6.27, restored from the backup, and everything
> was fine. Then I tried upgrading to 2.8.1 and got the same message as
> before:
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists
>
> I tried over and over, but I keep getting the same message. This is
> getting frustrating.
>
> Paul, where do I get those upgrade scripts you mention?
>
> --
> Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> University of Chicago (^_^)/ CCSR
> 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> Denver, n.:  A smallish city located just below
>  the `O' in Colorado.
>
>
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Rolf S. <in...@to...>]

It seems your database already contains a table "cargo". You should find 
it somewhere in your dump file.
1) Make a backup.
2) Insert at the beginning of sql/Pg-upgrade-2.7.0-2.7.5.sql:

drop table if exists cargo;

3) Try again to upgrade.

Stuart Luppescu schrieb:
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 日, 2008-06-22 at 13:50 +0200, Rolf Stöckli wrote:
> It seems your database already contains a table "cargo". You should find 
> it somewhere in your dump file.
> 1) Make a backup.
> 2) Insert at the beginning of sql/Pg-upgrade-2.7.0-2.7.5.sql:
> 
> drop table if exists cargo;
> 
> 3) Try again to upgrade.
> 
> Stuart Luppescu schrieb:
> > Error!
> > create table cargo (id int not null, trans_id int not null, package
> > text, netweight float4, grossweight float4, volume float4)
> > ERROR: relation "cargo" already exists

Rolf, I entered that line, but got this error:

Error!
drop table if exists cargo
ERROR: syntax error at or near "exists" at character 15

Right after that is the line that creates the cargo relation. Perhaps I
should try and comment out that line...

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
<gholam> well I'm impressed <gholam> win98 managed
 to crash X from within vmware. * gholam applauds. 
 
 
 

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 日, 2008-06-29 at 19:25 -0500, Stuart Luppescu wrote:
> On 日, 2008-06-22 at 13:50 +0200, Rolf Stöckli wrote:
> > It seems your database already contains a table "cargo". You should find 
> > it somewhere in your dump file.
> > 1) Make a backup.
> > 2) Insert at the beginning of sql/Pg-upgrade-2.7.0-2.7.5.sql:
> > 
> > drop table if exists cargo;
> > 
> > 3) Try again to upgrade.
> > 
> > Stuart Luppescu schrieb:
> > > Error!
> > > create table cargo (id int not null, trans_id int not null, package
> > > text, netweight float4, grossweight float4, volume float4)
> > > ERROR: relation "cargo" already exists
> 
> Rolf, I entered that line, but got this error:
> 
> Error!
> drop table if exists cargo
> ERROR: syntax error at or near "exists" at character 15
> 
> Right after that is the line that creates the cargo relation. Perhaps I
> should try and comment out that line...

So, I commented out the line, unlocked the database, logged in again,
found another offending line. Repeated this pattern perhaps 100 times. I
finally got to the point where the upgrade scripts would run to
completion. Hooray! I now have a functioning 2.8.15 system. 

However, when I do (AR|AP) -> Reports -> Transactions and select
``Details'' all the lines display twice. Has anyone ever seen this
before?

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
You're a card which will have to be dealt with. 
 
 
 
 

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Bob G. <bo...@rc...>]

I would guess that both symptoms come from trying to reload a database
that already contains your data. You MUST have a created EMPTY
sql-ledger database before doing the restore.

After you have a decent dump of your database (check that it does not
contain the duplicate statements you mention in your email).

The script I use is:
# To restore, do
su  postgres

  psql template1
  psql> DROP DATABASE "sql-ledger";
  psql> CREATE DATABASE "sql-ledger";
  psql> \q

# Then:
psql sql-ledger < sql-ledger.dump

On Sun, 2008-06-29 at 21:33 -0500, Stuart Luppescu wrote:
> On 日, 2008-06-29 at 19:25 -0500, Stuart Luppescu wrote:
> > On 日, 2008-06-22 at 13:50 +0200, Rolf Stöckli wrote:
> > > It seems your database already contains a table "cargo". You should find 
> > > it somewhere in your dump file.
> > > 1) Make a backup.
> > > 2) Insert at the beginning of sql/Pg-upgrade-2.7.0-2.7.5.sql:
> > > 
> > > drop table if exists cargo;
> > > 
> > > 3) Try again to upgrade.
> > > 
> > > Stuart Luppescu schrieb:
> > > > Error!
> > > > create table cargo (id int not null, trans_id int not null, package
> > > > text, netweight float4, grossweight float4, volume float4)
> > > > ERROR: relation "cargo" already exists
> > 
> > Rolf, I entered that line, but got this error:
> > 
> > Error!
> > drop table if exists cargo
> > ERROR: syntax error at or near "exists" at character 15
> > 
> > Right after that is the line that creates the cargo relation. Perhaps I
> > should try and comment out that line...
> 
> So, I commented out the line, unlocked the database, logged in again,
> found another offending line. Repeated this pattern perhaps 100 times. I
> finally got to the point where the upgrade scripts would run to
> completion. Hooray! I now have a functioning 2.8.15 system. 
> 
> However, when I do (AR|AP) -> Reports -> Transactions and select
> ``Details'' all the lines display twice. Has anyone ever seen this
> before?
>