[Mono-list] Mod_mono stops responding (503 Service Unavailable)

Marek Habersack grendello at gmail.com
Fri Mar 14 11:04:51 EDT 2008

Hash: SHA1

On Fri, 14 Mar 2008 16:54:18 +0200
"Lauri Kotilainen" <rytmis at gmail.com> wrote:

> Hi,
> On Fri, Mar 14, 2008 at 4:09 PM, Marek Habersack <grendello at gmail.com> wrote:
> >  - From your description it's hard to tell what is wrong. Error 503 can be
> > anything - usually a segfault in apache or one of the modules. You need to find
> > the corresponding messages in the apache error log, possibly setting the logging
> > level to debug.
> That may be something we have to do, although I would imagine a
> segfault would be logged as an Error, not as a Debug. Right now, there
> is a curious absence of error log messages when this happens.
That's true, but apache error messages tend to be very unhelpful - and debug
provides (sometimes) enough context to pin-point the problem.
> > Also, your mono is really, really old and there's a very good chance that
> >  whatever issue you're running into is fixed in the newer versions. Even though
> > there are no updated packages for mono for your OS, compiling mono from the
> > released sources (http://go-mono.com/sources-stable/) is not hard and I'd
> > recommend you give it a try.
> I suppose I can suggest we snapshot the image, do an upgrade to 7.10
> and try with a newer Mono. Still, this is kind of a "let's hope for
> the best" sort of approach, since I can't even reproduce the problem.
You could install latest mono in /usr/local and just recompile your mod_mono to use
that installation - leaving the old one intact and swapping the mod_mono modules as
needed. mod_mono, xsp and system.web have all gone a long way since 1.2.3 was
released, so there's a really good chance the bugs you're seeing are long fixed -
and I'd risk a statement that in this approach there's more certainty than hope :)

best regards,

Version: GnuPG v2.0.4-svn0 (GNU/Linux)


More information about the Mono-list mailing list