[Mono-list] More mono-1.1.13-4/mod_mono issues

[Chris Aitken]

Hi All,

I am currently experiencing a few issues with mono/mod_mono/apache. I
upgraded from 1.1.10 to 1.1.13-4 yesterday (mono installer and mod_mono FC3
alien'd for debian by myself).

1. I need to use libgdiplus.dll for one of my apps. To do so I must ensure
that the line "/opt/mono/lib" is in my /etc/ld.so.conf file. App runs fine.
However, this stops PostgreSQL from running, due to a relocation error
(/opt/mono-1.1.13.4/lib/libreadline.so.4: undefined symbol: BC). Either I do
not run PostgreSQL or my App.

2. Using the alien'd version of mod_mono (1.1.10 or .13-4) I have never been
able to get autoconfiguration to work. I get messages in the apache log that
look as if apache or mono is looking for mono within
"/usr/lib/pkgconfig/../../bin/mono" however, mono is in "/opt/mono"
(symlinked to "/opt/mono-1.1.13"). Is this what others are experiencing?

3. I am experiencing crossovers in applications.
I have 3 name based virtual hosts. A, B & C. A & B are setup for mono, and
have the following in the namebased host file:

A:	  MonoRunXSP True
        MonoPath "/opt/mono/share"
        MonoApplications "/:/home/A/public_html"
        MonoExecutablePath "/opt/mono/bin/mono"
        MonoServerPath "/opt/mono/lib/xsp/1.0/mod-mono-server.exe"
        AddHandler mono aspx ashx asmx ascx asax config ascx
        MonoWapiDir "/tmp/mono/A"
        MonoUnixSocket "/tmp/mono/A/mod_mono_socket"

B:	  MonoRunXSP True
        MonoPath "/opt/mono/share"
        MonoApplications "/:/home/B/public_html"
        MonoExecutablePath "/opt/mono/bin/mono"
        MonoServerPath "/opt/mono/lib/xsp/1.0/mod-mono-server.exe"
        AddHandler mono aspx ashx asmx ascx asax config ascx
        MonoWapiDir "/tmp/mono/B"
        MonoUnixSocket "/tmp/mono/B/mod_mono_socket"

C is not setup for mono.
The following issues exist:

If I call a page from domain A from domain C (i.e. hello.aspx exists ONLY
under www.A.net, but type www.C.net/hello.aspx) then the page appears. i.e.
there is leakage from a mono'd domain to a non-mono domain. B->C doesn't
happen, unless A is turned off. 

If I call a page from B that exists in A, I get an aspx 404 page saying that
the page doesn't exist in A. Ditto the other way round. This is to be
expected.

If I call a page from C that exists in B, I get the aspx 404, but the 404
shows that the page had been searched for in A.

I hope someone can shed some light on these!
Thanks,
Chris


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.