Hello,
> The background to our problem is that we are deploying a large website
> on mono for a customer, and have the server 'freeze' about 1-2 times
> a day. At the freeze points mono takes up between 15-55% of memory on
> the web server, typically consumes around 3% of CPU, and the website
> becomes responsive again if the mono processes are restarted.
>
>
>
> The freeze is completely random. When we run strace we get copius
> output into the trace logs resulting in a large build-up in the log
> size. We are therefore forced to stop the trace because of this. Gdb
> kills the running application, so we don’t use it.
>
>
>
> Is there another way of running the trace for days on-end without
> producing voluminous (and perhaps unnecessary) data?
Could you provide the following information:
* Operating system.
* Mono version, xsp version, mod_mono version.
* Process list, process sizes.
* If you strace the hung process, what do you get? A few lines
will be fine.
Miguel.
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
