Monitoring Project Portal processes

USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root      3672  0.0  0.0  4468 1972 ?        S    Mar18   0:00 /home/kronodoc/pp2012/httpd/kronohttpd_80 -d /home/kronodoc/pp2012/httpd
kronodoc      3673  0.0  0.0  4396 1920 ?        S    Mar18   0:00 /home/kronodoc/pp2012/httpd/fcgi-pm       -d /home/kronodoc/pp2012/httpd
kronodoc      3675  0.0  0.7 19308 16152 ?       S    Mar18   0:02 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronoconf
kronodoc      3676  0.0  1.7 40300 36344 ?       S    Mar18   0:09 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc
kronodoc      3679  0.0  1.6 39272 34784 ?       S    Mar18   0:09 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc
kronodoc      3680  0.0  1.6 32536 16412 ?       S    Mar18   0:00 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/streamer
kronodoc      3681  0.0  1.7 39288 35600 ?       S    Mar18   0:09 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc
kronodoc      3683  0.0  1.7 39280 35536 ?       S    Mar18   0:08 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc
kronodoc      3685  0.0  1.7 39276 35888 ?       S    Mar18   0:10 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc
kronodoc      3686  0.0  1.6 32536 16412 ?       S    Mar18   0:00 ../sbin/perl5 /home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/streamer
kronodoc      3674  0.0  0.1  4612 2236 ?        S    Mar18   0:00 /home/kronodoc/pp2012/httpd/kronohttpd_80 -d /home/kronodoc/pp2012/httpd
kronodoc      3710  0.0  0.1  4604 2240 ?        S    Mar18   0:00 /home/kronodoc/pp2012/httpd/kronohttpd_80 -d /home/kronodoc/pp2012/httpd

Monitor that the following Project Portal processes are running:

• Process owned by USER root if the PORTNUMBER is smaller than 1024 (see PID 3672 in the example above). This process manages the Apache processes and has root access to privileged ports, such as 80 (HTTP) or 443 (HTTPS).
• Several processes owned by the user on whose account Project Portal has been installed, and which process the incoming requests (see PID 3674, 3710 in the example above).
• fcgi-pm process under the kronohttpd directory. The fcgi-pm process manages other Project Portal processes (see PID 3673 in the example above).
• Several ../sbin/perl5 processes run in the Kronodoc's fcgi directory. These are the main software processes, the number of which is determined in the configuration file httpd/conf/kronodoc20.conf. These processes consist of:

• The kronodoc processes that represent the main software processes. The maximum number of concurrently processed requests constitutes the number of these processes (see PID 3676,3679,3681,3683,3685 in the example above).
• The streamer processes that are used for streaming large file downloads, to keep the kronodoc processes free for other operations (PIDs 3680, 3686).
• One or more kronoconf processes (PID 3675).

Note: The kronodoc/kronoconf/streamer fcgi processes described should not have more than thirty minutes of cumulative CPU time, because Project Portal processes are restarted after a preset number of requests. Project Portal processes are also restarted if their memory consumption after performing a request exceeds preset limits for virtual or resident memory consumption. If there is one of more Project Portal processes that constantly consume 100 per cent of the CPU time, it is usually safe to terminate them with ‘kill –TERM <PID>’. After terminating the process, check that the http/logs/error_log contains an entry for the successful restart of the process. See example below.

[Fri Mar 19 08:20:01 2004] [warn] FastCGI: server "/home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc" (pid 2739) terminated due to uncaught signal '15' (Terminated) 
[Fri Mar 19 08:20:01 2004] [warn] FastCGI: server "/home/kronodoc/pp2012/Kronodoc/KRONO/fcgi/kronodoc" restarted (pid 10832)