What you describe here has happened to us a couple of times. We basicly got rid of the problem by installing a keepalive server (which is completly different from the config parameter), that checks the sanity of my OACS installation and if down, restart it. Though this is only a treatment for the symptoms, it is working. Sadly though, without a considerable increase in the site-node-init.tcl (kudos to Timo for doing this), it is a PITA to restart a server (around 4 minutes with AIESEC).
Some other things I realized down that road:
- AOLserver4 crashes and needs to be restarted twice (first time it can't get hold of the ip:port)
- AOLserver4 wants to be killed, not terminated. Not sure if this is in protest of the terminator going into politics or if I'm just to anxious (but hey, 4 minutes to shut down should be enough ....).
