Forum OpenACS Q&A: Re: Server shutdown
The answer to (a) lies in the request (or scheduled proc) currently executing. You should check this. Was the server issuing an
Concerning (b) there are two potential sources. You are running out of the address space of a single process (2 GB with 32-bit compiled binaries on Linux) or the machine was in general running out of memory. It would be interesting to know, how large the server was at the time of the crash. Keep in mind, that all threads of the aolserver are running within one 2GB address space (for 32-bit compiled code).
You can do several things to keep under the 2GB mark:
- reduce the number of connection threads configured
- reduce the number of packages loaded
- avoid the calls to exec
- daily restarts of the server
You can remove the 2GB limit by compiling aolserver as a 64 bit binary (all components have to be compiled this way, from tcl ... nspostgres ...)
If the machine is running out of memory, well, adding more memory or swap space might help. Maybe the problem is coming from some other processes running wild on the machine, eating up all resources, so moving these away might help...
PS: looks like a good candidate for a FAQ.