Forum OpenACS Development: Two historic problems

Posted by Jose Agustin Lopez Bueno on

We have two historic problems on our installation and I like to resolve then. Both of then refers to aol drivers and
are very uncomfortable.

-When I stop DB (postgres), aolservers can not reconnect.
We have to stop / start the aols and that is 3-5 minutes
for every aol node.
-When I stop our openldap server (all nights), the aol
server crash. We have recompiled standard system openldap
libraries to avoid that.

Anybody can help us?

(we use Debian lenny and PG 8.2.13)


2: Re: Two historic problems (response to 1)
Posted by Dave Bauer on
Why are you regularly stopping your databases?

You should not ever have to stop Postgresql if you have it configured correctly.

If the ldap server is not running, how can aol authenticate? If you are stopping the databases it seems much easier to plan ahead and restart aolserver.

3: Re: Two historic problems (response to 2)
Posted by Jose Agustin Lopez Bueno on
Thanks for the answer, Dave.

For postgres, we have not periodic restarts but
some times we need restart the DB system and
we will be life easier if the aol driver auto connect.

For ldap, we have three openldap balanced and several
nightly processes. If we stop the ldap connected to
one aol server, the server crash.


4: Re: Two historic problems (response to 3)
Posted by Dave Bauer on
I don't know about openldap but still, I don't believe there is any solution to this. It is the design of the pooled database connections for AOLserver.

You might also want to check on the AOLserver mailing list.

5: Re: Two historic problems (response to 1)
Posted by Claudio Pasolini on
Years ago I had an Oracle based OpenACS connecting to a remote Oracle database and the driver was able to reconnect after a disconnection.

AFAIK never stop PostgreSQL before stopping Aolserver.