Forum OpenACS Q&A: Re: Openacs process disappearing

Collapse
Posted by Jason Cheung on
versions
------------
Operating System: Fedora Core 3
AOLserver: version 4.0.9
tcl: version 8.4

building and installation
------------------------------
building with the instructinos given in openacs.org:
https://openacs.org/doc/current/complete-install.html
(only altered some name of folders)

configuration
-----------------
Modules Loaded: nssock nslog nssha1 nscache nsgdchart nsdb
stacksize: expr 128 * 8192

Planned kill
---------------
There is no planed kill for AOLserver process.
AOLserver process crashed itself at some point.

Clawer
--------
Yes. Clawer was the last visiter before crashes most of the time. And most of the time it is Googlebot.

resource limit
-----------------
I have not set any limit myself, but the os may set some
limit by default. Please see what I got from the OS:

[root@machine etc]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16380
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

I am trying your ulimit -c unlimited option now.
See if it is related. The site was down when an unblocked Googlebot visited the CLB site.
I have block that ip now

Collapse
Posted by Andrew Piskorski on
Jason, "ulimit -a" reports the current limits in effect for that shell, right now. You gave ulimit output for a root shell, which may or may not have any relevance at all. You need to know what if any limits are configured for the shell that starts the AOLserver process. Also, AFAICT you do not yet know whether or not "AOLserver crashed itself" - that one of the things you're trying to figure out.