[Mono-bugs] [Bug 472732] mod-mono crashes after timeout

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=472732

User bassam at symform.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=472732#c4





--- Comment #4 from Bassam Tabbara <bassam at symform.com>  2009-02-09 10:13:53 MST ---
I've set the process limits to 10240, verified that the memory is set to
unlimited, and reset the server. Its been running for a 4 days now and last
night it tripped again. Here are the contents of the apache error log:

[Sun Feb 08 21:37:41 2009] [error] Maximum number of concurrent mod_mono
requests to /tmp/mod_mono_dashboard_control_2.l
ock reached (20 active, 20 waiting). Request dropped.
[Sun Feb 08 21:58:22 2009] [error] (70014)End of file found: read_data failed
[Sun Feb 08 21:58:23 2009] [error] Command stream corrupted, last command was 1
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:23 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:22 2009] [error] (70014)End of file found: read_data failed
[Sun Feb 08 21:58:23 2009] [error] Command stream corrupted, last command was 1
[Sun Feb 08 21:58:23 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:23 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:24 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:24 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:22 2009] [error] (104)Connection reset by peer: read_data
failed
[Sun Feb 08 21:58:24 2009] [error] Command stream corrupted, last command was
-1
[Sun Feb 08 21:58:31 2009] [error] Failed to connect to mod-mono-server after
several attempts to spawn the process.
<snip>
[Sun Feb 08 22:03:16 2009] [error] Failed to connect to mod-mono-server after
several attempts to spawn the process.
[Sun Feb 08 22:06:55 2009] [error] Failed to connect to mod-mono-server after
several attempts to spawn the process.

** (/usr/lib/mono/2.0/mod-mono-server2.exe:29495): WARNING **:
process_set_current: error creating process handle

** (/usr/lib/mono/2.0/mod-mono-server2.exe:29499): WARNING **:
process_set_current: error creating process handle
[Sun Feb 08 22:07:01 2009] [error] Failed to connect to mod-mono-server after
several attempts to spawn the process.

** (/usr/lib/mono/2.0/mod-mono-server2.exe:29503): WARNING **:
process_set_current: error creating process handle

** (/usr/lib/mono/2.0/mod-mono-server2.exe:29507): WARNING **:
process_set_current: error creating process handle

** (/usr/lib/mono/2.0/mod-mono-server2.exe:29511): WARNING **:
process_set_current: error creating process handle
[Sun Feb 08 22:07:07 2009] [error] Failed to connect to mod-mono-server after
several attempts to spawn the process.
<snip>

There are currently 100+ mod-mono-server2 processes running, and the server is
not accepting any more connections. We could really use some help with this
one. Is there any more information that we can collect to help resolve this
issue? We can even arrange for SSH access to the machine if it would help
debugging.

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