[Mono-bugs] [Bug 476081] New: Too many mod_mono instances running and mod-mono server stops responding

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Feb 16 04:05:41 EST 2009


           Summary: Too many mod_mono instances running and mod-mono
                    server stops responding
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.2.x
          Platform: Other
        OS/Version: SLES 10
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: kuanil at novell.com
         QAContact: mono-bugs at lists.ximian.com
                CC: bkalidas at novell.com, rarul at novell.com,
                    vvaradhan at novell.com, vprabudas at novell.com,
                    amahabaleshwar at novell.com, sbindu at novell.com
          Found By: ---

After discussion with Mono team for bug id 440486, iFolder code was modified so
that it is supported to run with Mono2.x runtime. Currently we are
running/testing iFolder with Mono2.2 runtime tree (This tree is a directory
structure with all mono runtime libraries inside iFolder) as it was decided
alongwith Mono team. When iFolder server is accessed through mod-mono with very
requests coming in one by one, everything works fine. But once many clients
connect and server also starts using mod-mono frequently, suddenly it is seen
that there are many instances of mod-mono running and server stops responding.
Once this happens, then every minute many instances of mod-mono comes up and
get added. Server becomes non-responsive. This can be reproduced within15-30
minutes. Our ST person, when tries to connect around 15 clients, this happens
in first time itself. 
I read http://www.mono-project.com/Mod_mono#Advanced_options 
and tried putting "MonoAutoRestartTime simias10 00:00:120 " into our conf file
for a restart at every 2 minutes, but this is not working at all. No restart of
mod-mono happens. 
I also used : 
<Location /mono>
  SetHandler mono-ctrl
  Order deny,allow
  Deny from all
  Allow from
to check the mod-mono server, but no of requests currently being processed does
not cross 3 (or may be when i am checking this no has reduced ...not sure).

i am writing here a part of the result of "pe -ef | grep mono"  : 

wwwrun   32538     1  0 13:11 ?        00:00:00
--filename /tmp/mod_mono_server_simias10 --applications
/simias10:/opt/novell/ifolder3/lib/simias/web --nonstop
wwwrun   32554     1  0 13:11 ?        00:00:00
--filename /tmp/mod_mono_server_simias10 --applications
/simias10:/opt/novell/ifolder3/lib/simias/web --nonstop
wwwrun   32563     1  0 13:12 ?        00:00:00
--filename /tmp/mod_mono_server_simias10 --applications
/simias10:/opt/novell/ifolder3/lib/simias/web --nonstop

and so-on...........

For you reference, i am writing the conf file used by iFolder and which
reproduces this issue : 
Include /opt/novell/ifolder3/lib/Mono/bin/mod_mono.conf

Alias /simias10 "/opt/novell/ifolder3/lib/simias/web"
AddMonoApplications simias10 "/simias10:/opt/novell/ifolder3/lib/simias/web"
MonoSetEnv simias10
MonoServerPath simias10 /opt/novell/ifolder3/lib/Mono/bin/mod-mono-server2
<Location /simias10 >
        MonoSetServerAlias simias10
        Order allow,deny
        Allow from all
        SetHandler mono

even if i do apache2 restart/reload or pkill mono, it does not kill mono..
after sending SIGKILL to mono process, it kills mono. But these manual
workarounds won't be acceptable by customers.Also iFolder will have big
deployments where restarting server every now and then won't be acceptable
scenario. So we would like to have a fix.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list