On Mon, Oct 3, 2011 at 9:32 PM, Dave Babb <[email protected]> wrote: > Here is the error log. > > I ran the "./tools/prepare-company-database.sh" script as: > > "./tools/prepare-company-database.sh --company aci --pgsql-contrib > /usr/share/postgresql/8.4/contrib" > > URL I'm launching: "http://localhost/ledgersmb/setup.pl"; > > credentials: > user = admin > pass = admin > database = aci > > Thank you for the assistance in getting me up and running. > > > Dave.......... > > > > > > [Mon Oct 03 22:25:24 2011] [notice] Apache/2.2.16 (Debian) configured -- > resuming normal operations > DBD::Pg::st execute failed: ERROR: column "version" does not exist > LINE 1: SELECT version FROM defaults > ^ at LedgerSMB/Database.pm line 208.
^^^ Normal in that it didn't find a legacy database. I would prefer that we do log these because it is not a common operation and because if things don't go well, having the detection statements in the log are helpful. > DBD::Pg::st fetchrow_hashref failed: no statement executing at > LedgerSMB/Database.pm line 209. > Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db > handle dbname=aci at scripts/setup.pl line 58. > [Mon Oct 03 22:25:42 2011] [error] [client 127.0.0.1] Premature end of script > headers: setup.pl, referer: http://localhost/ledgersmb/setup.pl So you enter these credentials and you get a message saying the database doesn't exist,and then you click continue and you get an error?> Best Wishes, Chris Travers ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
