Re: [Ledger-smb-users] upgrade problem

2013-05-13 Thread Chris Travers
Hi Bob; On Mon, May 13, 2013 at 10:23 PM, Bob Miller wrote: > Hi Chris, > > > > I considered a caching problem too. I force reloaded, then I cleared > history/cookies/cache in my browser, then just to be sure loaded it up > in a browser on a different machine that had never been to that site.

Re: [Ledger-smb-users] upgrade problem

2013-05-13 Thread Bob Miller
Hi Chris, Thanks for taking a look at this... > > > When I visit my page at http://ledger.computerisms.ca it shows > me I am > still version 1.3.29. When I log into it it says the same > version. > But: > > > Something is wrong here. It

Re: [Ledger-smb-users] upgrade problem

2013-05-13 Thread Chris Travers
> > >> psql:Reconciliation.sql:358: ERROR: syntax error at or near "in_scn" >> LINE 121: in_scn NOT LIKE t_prefix || '%'; >> > > Just more on this one. I have tracked down the source of the problem but not why my test cases didn't pick it up. It only affects 1.3.31. In your case you can ig

Re: [Ledger-smb-users] upgrade problem

2013-05-13 Thread Chris Travers
Something certainly sounds wrong. On Mon, May 13, 2013 at 5:45 PM, Bob Miller wrote: > Hello again, > > Something is wrong > > As per the upgrade instructions: > 1.untar over top of the existing install > 2.run reload_modules.sh > > Seems simple enough (I use apache2-mpm-itk with documentro

Re: [Ledger-smb-users] upgrade problem

2013-05-13 Thread Bob Miller
Hello again, Something is wrong As per the upgrade instructions: 1.untar over top of the existing install 2.run reload_modules.sh Seems simple enough (I use apache2-mpm-itk with documentroot of /var/www/ledger.computerisms.ca/): cd /usr/src/ wget http://downloads.sourceforge.net/project/

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
I've done a dump of the databases now (pg_dumpall) and made a tgz copy of the folder. ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww: http://hek

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 4:37 AM, Linda Ursin wrote: > I replaced and reconfigured. Now I can log in with my linda user. > Thanks for all the help. I will have to move this to another server, and > upgrade it. Any advice on how to do that without it going wrong again? > Best thing to do is copy y

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
I replaced and reconfigured. Now I can log in with my linda user. Thanks for all the help. I will have to move this to another server, and upgrade it. Any advice on how to do that without it going wrong again? Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 4:24 AM, Linda Ursin wrote: > [database] > # Sets database connection parameters. Note that default_db can be left > blank > # if you want to force people to enter a company name at login. > port = 5432 > default_db = heksebua > host = localhost > db_namespace = public >

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
[database] # Sets database connection parameters. Note that default_db can be left blank # if you want to force people to enter a company name at login. port = 5432 default_db = heksebua host = localhost db_namespace = public Should this say ledgersmb for default_db? Linda ~*~*~*~*~*~*~*~*~*~*~

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
That's probably the database ledgersmb. I had one named heksebua and one named ledgersmb last time I checked the admin page. ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvang

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 4:15 AM, Linda Ursin wrote: > heksebua=# \dt defaults >List of relations > Schema | Name | Type | Owner > +--+---+--- > public | defaults | table | ledgersmb > > Ok, so your data has been moved back However the tables for t

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
heksebua=# \dt defaults List of relations Schema | Name | Type | Owner +--+---+--- public | defaults | table | ledgersmb (1 row) heksebua=# \dt users No matching relations found. heksebua=# \dt users_conf No matching relations found. heksebua=# sele

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 3:49 AM, Linda Ursin wrote: > heksebua=# \dt > Ok, in this database: \dt defaults \dt users \dt users_conf Then: select * from defaults where setting_key = 'version'; > public | partscustomer| table | ledgersmb > public | partsgroup | table | ledg

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
heksebua=# \dt public | partscustomer| table | ledgersmb public | partsgroup | table | ledgersmb public | partstax | table | ledgersmb public | partsvendor | table | ledgersmb public | pricegroup | table | ledgersmb public | project

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 3:38 AM, Linda Ursin wrote: > postgres=# \dn > List of schemas > Name| Owner > +-- > information_schema | postgres > pg_catalog | postgres > pg_toast | postgres > pg_toast_temp_1| postgres > pu

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
postgres=# \dn List of schemas Name| Owner +-- information_schema | postgres pg_catalog | postgres pg_toast | postgres pg_toast_temp_1| postgres public | postgres (5 rows) ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Thu, Feb 16, 2012 at 3:16 AM, Linda Ursin wrote: > Hi > > There's nothing from that time in the postgresql log. > > postgres=# \dt defaults > No matching relations found. > postgres=# \dt users > No matching relations found. > postgres=# \dt users_conf > No matching relations found. > Ok, so:

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Linda Ursin
Hi There's nothing from that time in the postgresql log. postgres=# \dt defaults No matching relations found. postgres=# \dt users No matching relations found. postgres=# \dt users_conf No matching relations found. Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~

Re: [Ledger-smb-users] Upgrade problem

2012-02-16 Thread Chris Travers
On Wed, Feb 15, 2012 at 11:25 PM, Linda Ursin wrote: > Hi > > So the data has been moved back now? > It suggests that it was. Can you check your PostgreSQL log as well? In the mean time, also log into your db in psql and: \dt defaults \dt users \dt users_conf Best Wishes, Chris Travers > >

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
Hi So the data has been moved back now? There are no more lines for the specific time in the error log. [Thu Feb 16 08:53:05 2012] [error] [client 193.69.154.79] Name "Config::Std::Hash::DEMOLISH" used only once: possible typo at /usr/share/perl5/Class/Std.pm line 523., referer: http://lur.aitel

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Chris Travers
On Wed, Feb 15, 2012 at 8:35 AM, Linda Ursin 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

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
Is it possible to do a fresh install of 1.3.11 and import customers, parts and assemblies? Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww:

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Michael Richardson
> "Linda" == Linda Ursin writes: Linda> Finally found it. When I ran it I got this: Linda> postgres@lur:/home/lur/ledgersmb/sql/upgrade$ psql heksebua < Linda> /home/lur/ledgersmb/sql/upgrade/1.3-1.2.sql Linda> BEGIN Linda> ALTER SCHEMA Linda> ALTER SCHEMA Linda>

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
And when I try to log in, I get a 500 error, with these lines in the log file for apache: [Wed Feb 15 18:08:40 2012] [error] [client 193.69.154.79] Can't call method "prepare" on an undefined value at LedgerSMB/User.pm line 51., referer: http://lur.aitel.hist.no/regnskap/login.pl [Wed Feb 15 18:08

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
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,

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
Weird. I'll have to look again. Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww: http://heksebua.com 7288 Soknedal E-post:

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Chris Travers
On Wed, Feb 15, 2012 at 7:09 AM, Linda Ursin wrote: > In what version can I find the sql/upgrade/1.3-1.2.sql ? I cn't find it > in 1.3.11 > > I see it in the directory the tarball was built from. And I just unpacked the tarball and it's there. Best Wishes, Chris Travers --

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Linda Ursin
In what version can I find the sql/upgrade/1.3-1.2.sql ? I cn't find it in 1.3.11 Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww: http:

Re: [Ledger-smb-users] Upgrade problem

2012-02-15 Thread Chris Travers
On Wed, Feb 15, 2012 at 3:31 AM, Linda Ursin wrote: > Hi > > I had a lot of problems upgrading, and I think I've messed up good. New > version isn't working properly, and neither does the old. > > The new version asks me for my username and password, and then asks for > the user ledgersmb. > When