PDA

View Full Version : Cant get XSP/mod_mono working with apache2



t3hl33td4rg0n
19th January 2008, 07:15 PM
Greets all,

I've been trying to get ePresence to work for the last 2 days without success. So, ePresence requires mod_mono and XSP installed in order to work. Problem is, I cant get them to work :mad:

Initially, I just installed the XSP and mod_mono packages from the official repo, but I was getting errors. I think at one time it ran once for about 2 minutes before getting the dreaded 503 error.

So I grabbed the XSP and mod_mono tarballs from the mono project page. Went through the instructions and installed httpd-devel before doing the compiling.

The compilations went without issue, and I moved the automatically generated mod_mono.conf to /etc/httpd/conf.d, and fired up the test page... Error 503.

I've googled the issue for countless hours without finding any solution. Here are some logs...

When starting apache

[Sat Jan 19 13:02:10 2008] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sat Jan 19 13:02:10 2008] [notice] mod_python: using mutex_directory /tmp
[Sat Jan 19 13:02:10 2008] [notice] Apache/2.2.6 (Unix) DAV/2 mod_mono/1.2.6 PHP/5.2.4 mod_python/3.3.1 Python/2.5.1 mod_ssl/2.2.6 OpenSSL/0.9.8b mod_perl/2.0.3 Perl/v5.8.8 configured -- resuming normal operations

And when trying to view the mod_mono included test pages.

[Sat Jan 19 13:00:17 2008] [error] Failed to connect to mod-mono-server after several attempts to spawn the process.

When shutting down apache

[Sat Jan 19 13:01:05 2008] [notice] caught SIGTERM, shutting down
[Sat Jan 19 13:01:05 2008] [warn] (22)Invalid argument: Failed to destroy the '/tmp/mod_mono_dashboard_XXGLOBAL_1' shared memory dashboard

I've basically hit a brick wall and dont know what else I can try to get it working, can anyone help me out? :confused:

mon
25th July 2008, 10:27 AM
And when trying to view the mod_mono included test pages.

[Sat Jan 19 13:00:17 2008] [error] Failed to connect to mod-mono-server after several attempts to spawn the process.


Try to disable SELinux. This guide may help you:
http://www.inprose.com/articles/2-howtos/10-enable-aspnet-support-in-fedora-linux.html