[Pkg-mono-devel] Re: Timeframe for libapache2-mod-mono
Sam Liddicott
sam@liddicott.com
Thu, 23 Sep 2004 01:20:54 +0100
Fabian Fagerholm wrote:
...
> The fact that you have to purge mono packages suggests that something is
> modified along the way -- perhaps in the GAC? You could do this:
>
> COLUMNS=140 dpkg --list | egrep '^ii.*mono.*$' | awk '{print
> $2}' | xargs dpkg --listfiles {} | xargs md5sum > monofiles.txt
>
> immediately after installation. (It'll give error messages about
> directories but don't worry.) Then, once the thing has stopped working,
> do it again but change the output file name. You could then compare the
> two files to see what has changed: diff monofiles.txt monofiles2.txt
> This could give a clue as to what is changing.
I shall certainly perform these debug actions next time something occurs.
Since posting that message it came about that not always did purge work.
It also came about that not always did mono automatically start when
apache did but since then I have noticed that mono generally was started
on-demand by apache when I requested a mono page. Because previously
mono had started with apache I had not expected this and so in some
cases I may have been mistaken that mono would fail to start, as I
hadn't been "stimulated it" with a mono request.
In a few cases I did "stimulate it" and the request failed with an error
about the system being overloaded (or I guess mono not responding); but
in these cases where mono would not start it may have been a webapp error?
The machine I was testing on has now gone live but I will be able to try
this out on another machine soon to reproduce it.
Can I thank you for your efforts and also your response.
Sam