[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting Back to testing 1.4

On Wed, Oct 2, 2013 at 5:49 PM, <..hidden..> wrote:
1.4 is starting so seem like a brick wall here.
I am running Apache 2.4 and Postgresql 9.2
(I have several test versions of 1.2 working on this setup.)

likely a configuration issue on my Gentoo system however I thought I had
it working before.
Since it is just a test setup I have tried to set everything the most
I set pg_hba.conf to:
# TYPE  DATABASE        USER            ADDRESS                 METHOD
local   all             all                                     trust
host    all             all               trust
host    all             all             ::1/128                 trust
host    all         all               md5

the pertinent lines from ledgersmb-httpd.conf are:
Alias /ledgersmb-1.4 /var/www/localhost/htdocs/ledgersmb-1.4/

<Directory ledgersmb-1.4>
  RewriteEngine On
  RewriteRule ^/ledgersmb-1.4/?$ /ledgersmb-1.4/login.pl [R]
  RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

>From my postgres log when I try to connect to my old test database:
ERROR:  column "version" does not exist at character 8
STATEMENT:  SELECT version FROM defaults
ERROR:  column "version" does not exist at character 8
STATEMENT:  SELECT version FROM defaults

We are looking at how to silence these errors.  They are normal in the sense that we try to detect the current type and version of the software for upgrade or migration.  Those occur from testing for LedgerSMB 1.2 and SQL-Ledger 2.6. 

When I enter "14" into the input box on setup.pl I get
FATAL:  database "14" does not exist
FATAL:  database "14" does not exist


The question I have is whether you get the next screen,.  You should get a screen which says in the first case something about which version you are running and, if an upgrade or migration is supported, if you would like to upgrade your data.

In the second, you should be told "Database does not exist.  Would you like to create it?"

You are right that the errors above would do better to be silenced.  We are working on that but the task is a rare one and it may be that the simpler fix is to document that these are expected in the logs.
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.