Hey Guys, 

I just noticed this thread in the email queue so this may be coming too late. I have the same problem and sent an email about it to this group with the subject line: Mod_Managed Mono is not following the system LD Path.

That said,
I have mod_managed working but it is a bit of a hack to do so. I simply CD into the mod directory and then start the server from there.

EG.

cd /usr/local/freeswitch/mod
../bin/freeswitch

This makes that particular problem go away. I have tried changing the LD Path, configured mono per the instructions on the wiki, etc… None of that has worked for me but cd'ing into the mod directory and then starting the server at least gets me running.

This might be useful to everyone while we wait for this to be resolved. I have yet to add this as a bug in Jira. I was attempting to get some response here before doing so.

Ryan

On Wed, Aug 31, 2011 at 3:16 PM, <covici@ccs.covici.com> wrote:
Thanks so much for working on this.

Michael Giagnocavo <mgg@giagnocavo.net> wrote:

> Yea I have been meaning to get around to it. I'll put it on my todo and see if I can figure it out. Sorry for the inconvenience.
>
> "covici@ccs.covici.com" <covici@ccs.covici.com> wrote:
>
>
> Any chance of you fixing the bug?  I think you must be right because in
> the server stack trace I see a lot of things involving serialization.
>
> Michael Giagnocavo <mgg@giagnocavo.net> wrote:
>
> > It's probably more related to some cross-appdomain/serialization stuff that's specific to Mono. I wrote mod_managed against Mono 2.4 or so, and I think last time I ran it was 2.6, and only on CentOS 5. Probably something changed and is triggering a bug in mod_managed in the newer builds.