On Wed, Feb 15, 2012 at 8:35 AM, Linda Ursin <[email protected]> wrote:
> Finally found it. When I ran it I got this:
>
> postgres@lur:/home/lur/ledgersmb/sql/upgrade$ psql heksebua <
> /home/lur/ledgersmb/sql/upgrade/1.3-1.2.sql
> BEGIN
> ALTER SCHEMA
> ALTER SCHEMA
> COMMIT
> BEGIN
> ERROR: column "entity_id" of relation "vendor" does not exist
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
> ROLLBACK
>
> Does any of this matter?
>
Ok, this is sounding like the entire upgrade failed with the exception of
the moving of the old data out of the way. The commands are in the
transactions they are to address that possibility. This should be ok at
this point.
Regarding your 500 error, are there more log lines then that? That really
sounds like a connection failure for some reason. 1.2 is supposed to throw
an error "No GlobalDBH Configured or Could not Connect" when that
connection fails. Can you double check and see if there are more log lines
associated with this http request?
Best Wishes,
Chris Travers
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Ledger-smb-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
