Incorrect automatic configuration of mono-server2-hosts.conf

Bug #179284 reported by John Ryan
10
Affects Status Importance Assigned to Milestone
xsp (Ubuntu)
Invalid
Undecided
Ralph Janke

Bug Description

Binary package hint: mono-apache-server2

The /usr/sbin/mono-server2-update script erroneously adds the following line to /etc/mono-server2/mono-server2-hosts.conf:

MonoServerPath default /usr/lib/mono/2.0/mod-mono-server2.exe

instead of the correct:

MonoServerPath default /usr/bin/mod-mono-server2

/usr/lib/mono/2.0/mod-mono-server2.exe is a native Windows executable and needs to be wrapped by the script /usr/bin/mod-mono-server2 in order to function.

When apache attempts to start mod-mono-server2 with the incorrect MonoServerPath, the following error is observed in the apache error log:

[Sun Dec 30 09:44:16 2007] [error] Failed running '/usr/lib/mono/2.0/mod-mono-server2.exe --filename /tmp/.mod_mono_server2 --nonstop --appconfigdir /etc/mono-server2 (null) (null) (null) (null) (null) (null) (null)'. Reason: Exec format error

To fix the package, line 223 of mono-server2-update needs to be altered from:

    print TEMPHOST " MonoServerPath default /usr/lib/mono/2.0/mod-mono-server2.exe\n";

to:

    print TEMPHOST " MonoServerPath default /usr/bin/mod-mono-server2\n";

Revision history for this message
Noah Massey (ubuntu-waterwelp) wrote :

This was fixed upstream in Debian xsp (1.2.5-2) in February
I realize that intrepid has moved to 1.9,
but could we please get this fix in to the LTS?

Revision history for this message
Ralph Janke (txwikinger) wrote :

In order to get something backported, please follow the process described in https://help.ubuntu.com/community/UbuntuBackports

Thanks

Changed in xsp:
assignee: nobody → txwikinger
status: New → Invalid
Revision history for this message
Noah Massey (ubuntu-waterwelp) wrote :

from the link referenced:
"-Updates offers patches for serious bugs in Ubuntu packaging that do not affect the security of the system. "

It seems to me that having XSP fail to start on the LTS server release "represent[s] a severe deviance from expected behavior", and that the one line change referenced above both is "the minimum amount of change required to fix the bug". and has a "low-risk to breakage". As such, I think this is a good candidate for -updates.

I referenced the fact that it was changed upstream to add validity to the proposed solution, and to point out the general reliability of the change.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.