Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 7:29 PM, Philip Rhoades wrote: > Chris, > > > On 2012-02-01 14:02, Chris Travers wrote: > > On Tue, Jan 31, 2012 at 6:55 PM, Philip Rhoades > [6]> wrote: > > > >> Chris, > >> > >> On 2012-02-01 13 [1]:21, Chris Travers wrote: > >> > Hi Philip; > >> > > >> > Something is o

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Philip Rhoades
Chris, On 2012-02-01 14:02, Chris Travers wrote: > On Tue, Jan 31, 2012 at 6:55 PM, Philip Rhoades [6]> wrote: > >> Chris, >> >> On 2012-02-01 13 [1]:21, Chris Travers wrote: >> > Hi Philip; >> > >> > Something is obviously not as expected here.  1.3.10 addresses >> issues >> > of missing extens

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 6:55 PM, Philip Rhoades wrote: > Chris, > > > On 2012-02-01 13:21, Chris Travers wrote: > > Hi Philip; > > > > Something is obviously not as expected here. 1.3.10 addresses issues > > of missing extensions directories by detecting the PostgreSQL server > > version and if

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Philip Rhoades
Chris, On 2012-02-01 13:21, Chris Travers wrote: > Hi Philip; > > Something is obviously not as expected here.  1.3.10 addresses issues > of missing extensions directories by detecting the PostgreSQL server > version and if it is 9.0 or lower, it tries to look for the > tablefunc.sql, but if it i

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Chris Travers
Hi Philip; Something is obviously not as expected here. 1.3.10 addresses issues of missing extensions directories by detecting the PostgreSQL server version and if it is 9.0 or lower, it tries to look for the tablefunc.sql, but if it is 9.1 or above, it looks for tablefunc.control. If you are ru

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Philip Rhoades
On 2012-02-01 12:45, Chris Travers wrote: > On Tue, Jan 31, 2012 at 5:22 PM, Philip Rhoades [7]> wrote: > >> Roderick, >> >> On 2012-01-30 09 [1]:57, Roderick A. Anderson wrote: >> > Chris Travers wrote: >> >> On Mon, Jan 16, 2012 at 5:55 PM, Philip Rhoades >> >> >> wrote: >> >>> Chris, >> >>> >>

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 5:22 PM, Philip Rhoades wrote: > Roderick, > > > On 2012-01-30 09:57, Roderick A. Anderson wrote: > > Chris Travers wrote: > >> On Mon, Jan 16, 2012 at 5:55 PM, Philip Rhoades > >> wrote: > >>> Chris, > >>> > >>> RPM? > >> > >> The RPM drops the version number requirement

Re: [Ledger-smb-users] Announcing LedgerSMB 1.3.10

2012-01-31 Thread Philip Rhoades
Roderick, On 2012-01-30 09:57, Roderick A. Anderson wrote: > Chris Travers wrote: >> On Mon, Jan 16, 2012 at 5:55 PM, Philip Rhoades >> wrote: >>> Chris, >>> >>> RPM? >> >> The RPM drops the version number requirement for the perl-config-std >> package, and it is there at the same download loca

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 8:39 AM, Linda Ursin wrote: > It's the default configuration. I haven't touched it. What should be there > that isn't? > > Now that I have had a chance to sleep on this just a little Basically you have two options. 1) I suspect you are missing a database port assign

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
It's the default configuration. I haven't touched it. What should be there that isn't? Linda ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww: h

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Håvard Sørli
On 31. jan. 2012 15:28, Linda Ursin wrote: > I don't know why it says dbname template1, because I gave the dbname > heksebua > ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Could it be that user postgres is a db "superuser" and the user info is stored in temp

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 7:01 AM, Linda Ursin wrote: > How is that possible when I haven't changed it? ( I changed it back to > default after trying trust) > 1.3 handles things a bit differently, security-wise, so it isn't entirely surprising that some configurations that worked with 1.2 are not

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
Of course, you have to at least tell PostgreSQL to reload the config files after making the change, but I find restarting is more reliable. Best Wishes, Chris Travers -- Keep Your Developer Skills Current with LearnDevNow

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
How is that possible when I haven't changed it? ( I changed it back to default after trying trust) This is what it looks like: - # Database administrative login by UNIX sockets local all postgres ident local ledgersmb ledgersmb md5 # TY

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 6:26 AM, Linda Ursin wrote: > [Tue Jan 31 15:42:15 2012] [error] [client 193.69.154.79] DBI > connect('dbname=template1','postgres',...) failed: FATAL: Ident > authentication failed for user "postgres" at LedgerSMB.pm line 982, > referer: http://lur.aitel.hist.no/ledgersm

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
I don't know why it says dbname template1, because I gave the dbname heksebua ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~ Linda Ursin Heksebua Adresse: Tlf: (+47) 402 40 767 Solvangwww: http://heksebua.co

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
[Tue Jan 31 15:42:15 2012] [error] [client 193.69.154.79] DBI connect('dbname=template1','postgres',...) failed: FATAL: Ident authentication failed for user "postgres" at LedgerSMB.pm line 982, referer: http://lur.aitel.hist.no/ledgersmb/setup.pl ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 6:10 AM, Linda Ursin wrote: > ALTER USER "postgres" WITH VALID UNTIL '2013-11-09'; didn't help, even if > the command worked. > > If I was still using the old ledgersmb confiuration for apache, my > installation would be available through http:///regnskap/ > but it isn

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
ALTER USER "postgres" WITH VALID UNTIL '2013-11-09'; didn't help, even if the command worked. If I was still using the old ledgersmb confiuration for apache, my installation would be available through http:///regnskap/ but it isn't, it's aat http://.../ledgersmb/ lur:/home/lur# more /etc/

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Chris Travers
On Tue, Jan 31, 2012 at 5:08 AM, Linda Ursin wrote: > Yes, I have the correct user and password. > > I can login through psql. > > Using trust didn't work for setup.pl > > When I try the tip from the FAQ, I get > Please check your web server error logs and attach relevant entries. My guess, if

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Linda Ursin
Yes, I have the correct user and password. I can login through psql. Using trust didn't work for setup.pl When I try the tip from the FAQ, I get postgres=# ALTER USER 'postgres' WITH VALID UNTIL '2013-11-09'; ERROR: syntax error at or near "'postgres'" LINE 1: ALTER USER 'postgres' WITH VALID

Re: [Ledger-smb-users] Problems with upgrade from 1.2.x to current version

2012-01-31 Thread Håvard Sørli
On 30. jan. 2012 12:02, Linda Ursin wrote: > What should I do? Do you try to login with the Postgres superuser and the correct database name and password ? Can you try to test the login to the db with psql ? What about the FAQ : I can't login http://www.ledgersmb.org/node/27 Login to several