Hi again,
Thanks for all the help, Chris. I know you're busy and really appreciate it.
Here is the output:
psql (8.4.11)
Type "help" for help.
postgres=# SELECT * FROM defaults WHERE setting_key = 'version';
ERROR: relation "defaults" does not exist
LINE 1: SELECT * FROM defaults WHERE setting_key = 'version';
postgres=# SELECT count(*) FROM defaults;
ERROR: relation "defaults" does not exist
LINE 1: SELECT count(*) FROM defaults;
^
Major problem – the log files at the root level have disappeared.
root@AELS:/tmp# find / -name dblog_stderr
reveals nothing nor does the list (/l) command in the directory. The files
were there a few days ago... Back to square zero...
Just for reference: /l for postgres output:
List of databases
Name | Owner | Encoding | Collation | Ctype | Access privileges
-----------+-----------+-----------+-----------+-------+-----------------------
aels | postgres | UTF8 | C | C |
cana | ledgersmb | UTF8 | C | C |
company | postgres | UTF8 | C | C |
ledgersmb | ledgersmb | SQL_ASCII | C | C |
mycompany | ledgersmb | UTF8 | C | C |
mytestdb | postgres | SQL_ASCII | C | C |
postgres | postgres | SQL_ASCII | C | C |
template0 | postgres | SQL_ASCII | C | C | =c/postgres
: postgres=CTc/postgres
template1 | postgres | SQL_ASCII | C | C | =c/postgres
: postgres=CTc/postgres
testt | ledgersmb | UTF8 | C | C |
(10 rows)
I don't know what to make of all this. Maybe I need to reinstall postgres
again?
Thanks in advance.
Billy
On Wed, Mar 14, 2012 at 10:16 AM, Chris Travers <[email protected]>wrote:
> Hi;
>
> On Tue, Mar 13, 2012 at 4:15 PM, billy akazawa <[email protected]>
> wrote:
> > Hi again, everyone,
> >
> > I decided to start a new thread because the problem now seems to have
> been
> > reduced to the unexpected version dilemma.
> >
> > Here is the problem at the moment.
> >
> > setup.pl announces that it has successfully created the database. When
> I try
> > to log in using I get the unexpected version message and hint to rerun
> > setup.pl.
>
> Ok, this is a bit odd. Normally if it fails you will get other
> errors. It did prompt you to create a user, right?
>
> >
> > Error!
> >
> > Database is not the expected version. Was , expected 1.3.12. Please
> re-run
> > setup.pl against this database to correct.
> >
> > When I try to do that I get the following:
> >
> > Confirm Operation
> >
> > Unknown version found.
> > Cancel?
> > Yes No
> >
> > Clicking on either 'Yes' or 'No' and then 'Next' just takes me back to
> the
> > same Database Management Console. I can't get any further than this loop
> > process. In other words, there doesn't seem to be any way to re-run
> setup.pl
> > against the database a second time.
>
> Ok, we need to see what's going on.
>
> Can you log in to the db using psql and run the following queries:
>
> SELECT * FROM defaults WHERE setting_key = 'version';
>
> and
>
> SELECT count(*) FROM defaults;
>
> Also, please check your /tmp/ledgersmb/dblog_stderr for info on errors.
>
> 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
>
------------------------------------------------------------------------------
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
