Forum OpenACS Q&A: Response to VMWare OACS installation question

Collapse
4: Response to VMWare OACS installation question (response to 1)
Posted by damon pin on 07/26/02 07:27 AM
hi

I restarted the postgres server and can try out OACS now.

Thanks a lot for your help.

Collapse
6: Re: Response to VMWare OACS installation question (response to 4)
Posted by V. Amaral on 12/03/02 09:26 AM
Hi,

I have exactly the same problem, but restarting or starting the postgre service didn't help.
What else did you change (in nsd.tcl, in postgresql.conf)?

Any ideas?

Thanks for any help.

Collapse
7: Re: Response to VMWare OACS installation question (response to 6)
Posted by John Sequeira on 12/03/02 04:14 PM
Vitor, Could you confirm that you can log in to postgres using psql?

I believe you want to try (as root) 

/sbin/service postgresql start
su postgres
psql openacs
If you succeed with that, do you still get the same log errors when you start aolserver?

i.e. 

/sbin/service aolserver start

Then read the log file...

Collapse
8: typo (response to 7)
Posted by John Sequeira on 12/03/02 04:29 PM
The psql command above should be "psql openacs4".

If you succeed with the psql command, you can type "\d" to get a list of all the objects in the database.  If you get a bunch of acs* tables,  this should confirm that your db is fine.

Other debugging thoughts:
What you do get when you type ifconfig?
And what type of virtual network adapter is the VM using (bridged or NAT)?

Can you ping the VM from your host OS?