Mono 2.x

LI_Geek_95 · Jan 9, 2010

My Web Host said:

Due to a security/auditing issue, I have removed Mono 2.x from the server indefinitely. If you know how to get Mono to run ASP.NET processes under the correct user and not "nobody" please let me know and I will reinstall it.

I was alerted to this issue when I get a flood of e-mails telling me that the user "nobody" was using all of the CPU, unfortunately by the time I logged in the process was no longer running so I couldn't find out which account it was. So to prevent users from running more scripts anonymously I have removed Mono from the server.
Click to expand...

How could this be done?

Tux_Rules · Jan 10, 2010

I don't believe you would want to change the user as "nobody" in the *nix world (if I remember correctly) has limited capabilities and is the best choice. What I would suggest would be to maybe cut down the instances in which the process can spawn:

Limiting the number of concurrent requests
The number of concurrent requests that can be processed by the mod-mono-server backend is limited by the size of the ThreadPool, and some have experienced deadlocks when too many requests are going at once. As a result of the deadlocks, Apache child process instances that are processing requests get backed up until no more incoming HTTP connections can be made (even for any virtual host).

mod_mono will limit the number of concurrent requests that are passed off to mod-mono-server, and when the limit is reached, incoming requests wait for a certain amount of time until more requests can be passed off to the backend. The default limit of concurrent requests is 20, and the default limit of requests waiting to be passed off to the backend is 20. This should be just below the amount mod-mono-server can process without reaching the ThreadPool limit on a single processor machine.

To adjust the limits, use these directives:

1 MonoMaxActiveRequests 20
1 MonoMaxWaitingRequests 20
A value of zero disables the limits.
Click to expand...

This is from:

http://www.mono-project.com/Mod_mono#Limiting_the_number_of_concurrent_requests

or in the config file, find:

Under high load, mono process consumes a lot of memory, website stops responding
These symptoms have been reported, but their underlying causes are not known. Set the MonoAutoRestartMode, MonoAutoRestartRequests, MonoMaxActiveRequests, and MonoMaxWaitingRequests directives as described earlier to limit the lifetime of the mono process and to restrict the concurrency happening in the server.
Click to expand...

http://www.mono-project.com/Mod_mon...s_a_lot_of_memory.2C_website_stops_responding

This for *nix, correct?

LI_Geek_95 · Jan 15, 2010

Yes, this is for *nix.

Tux_Rules · Jan 18, 2010

zDawg32 said: ↑

Yes, this is for *nix.
Click to expand...

Then my first guess would be to try what I have posted above (cutting down the:

1 MonoMaxActiveRequests 20
1 MonoMaxWaitingRequests 20
Click to expand...

)
as I don't belive changing the "user" from nobody is the wisest choice, but cutting back on the amount of processes running should help.

Log in or Sign up

Mono 2.x

LI_Geek_95 Post-and-Run Geek

Tux_Rules Corporal

LI_Geek_95 Post-and-Run Geek

Tux_Rules Corporal