[Mono-aspnet-list] mod_mono fails: HTTP 503, no error log
nospam.list at unclassified.de
Fri Dec 12 12:10:22 UTC 2014
I have now installed mod_mono for Apache 2.4 on Ubuntu 14.04.1. I didn't
use auto configuration because it does things I can't use. Instead I
went for the manual configuration section and added the following lines
at the end of my otherwise working VirtualHost configuration:
Since the mentioned example application (/usr/share/doc/xsp/test)
doesn't exist on my system, I started up Visual Studio 2013 and created
a simple ASP.NET 4.5 Web Forms application and uploaded it into my
document root's monotest directory.
After restarting apache, I can see the following process running as the
/usr/bin/mono /usr/lib/mono/4.5/mod-mono-server4.exe --filename
/tmp/.mod_mono_server4 --nonstop --appconfigdir /etc/mono-server4
It's the wrong use because I need it to be 'web001', but I think I could
add that later - as soon as I found a description of how to do that,
because the Mono documentation does not cover that.
When I access that site, the result is an HTTP 503 error, "Service
Unavailable", after a few seconds. The virtual host's error log is
empty, today's file doesn't even exist yet. The access log only contains
a line indicating the 503 error. No other log files seem to exist for
apache or mono.
So what did I miss to set up mod_mono correctly? The documentation seems
largely outdated, mentioning .NET 1.1 and 2.0 profiles. I seem to have
4.5 running which is the most current version.
More information about the Mono-aspnet-list