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

[Marek Habersack]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 14 Mar 2008 10:23:19 +0200
"Lauri Kotilainen" <rytmis at gmail.com> wrote:

> Hey, and thanks for replying.
> 
> On Fri, Mar 14, 2008 at 10:15 AM, David Temes <dtemes at infoco.es> wrote:
> > It would be good to know what version of mono you are using. For instance I
> >  got many 503 errors after restarting apache (mono 1.2.6.x) with mod_mono on
> >  a debian server with kernel 2.4.x. and after upgrading the kernel to 2.6.x
> >  everything started to work really well.
> 
> Yeah, I knew I forgot something crucial when I was so eager to get
> that mail going. Here be the specs:
> 
> OS: Ubuntu Server 7.04
> Kernel: 2.6.20-15-generic
> Runtime: Mono 1.2.3.1
> Web server: Apache 2.2.3
> 
> I realize the first option people are going to suggest is "upgrade
> mono" but I want to avoid it if possible -- a newer mono is not
> available packaged for that version of Ubuntu, so to upgrade mono I'd
> have to either upgrade the OS or remove all traces of mono and install
> manually. If that's what it takes, I'll do it, but only as a last
> resort. :)
- 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. 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.

best regards,

marek
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFH2ochq3909GIf5uoRAi/fAKCC8dB/2e2VTM5Unz76jEY+sZmYUACdHH78
lsCtTG+hHsP9yk+bmK8tABw=
=7WU1
-----END PGP SIGNATURE-----