Ah -- this one turned out to be subtle.
When the VM boots up, aolserver was starting before postgres, and so couldn't connect.
The services just need to be restarted for you to have a working site.
svc /service/openacs5 -d
svc /service/openacs5 -u
and
svc /service/dotlrn -d
svc /service/dotlrn -u
Once you do that, just suspend your machine between uses and the boot bug won't strike. To address the issue, I've added (and you can add) the following code to the daemontools run script (/service/openacs5/run and /service/dotlrn/run) to wait until postgresql is alive:
#!/bin/sh
pid=`pidof -s postmaster`
while !([ $pid ] && /etc/init.d/postgresql status > /dev/null 2>&1)
do
pid=`pidof -s postmaster`
sleep 1
done
So you could also redownload the VM and not have the issue. I'm not sure why this hasn't been a problem in the past...
Sorry for the snafu ... you really are close to having working openacs/dotlrn instances. Promise.
