[Mono-list] mod_mono problems after upgrade to beta1

[Gonzalo Paniagua Javier]

El mié, 05-05-2004 a las 14:16, Trond Arve Nordheim escribió:
> Hi!
> 
> After upgrading from mcs-0.31, mono-0.31, xsp-0.12 and mod_mono-0.8 to 
> the beta1-versions (mcs-0.91, mono-0.91, xsp-0.13, mod_mono-0.9) I'm 
> having some problems with the mod-mono-server.exe spawned by Apache upon 
> the first request to a mono-handler.
> 
> This is what I get in my error-log:
> 
> ** (/usr/bin/mod-mono-server.exe:4295): WARNING **: cant resolve 
> internal call to 
> "System.Net.Sockets.Socket::Socket_internal(System.Net.Sockets.AddressFamily,System.Net.Sockets.SocketType,System.Net.Sockets.ProtocolType)" 
> (tested without signature also)
> 
> ** (/usr/bin/mod-mono-server.exe:4295): WARNING **: cant resolve 
> internal call to 
> "System.Net.Sockets.Socket::Socket_internal(System.Net.Sockets.AddressFamily,System.Net.Sockets.SocketType,System.Net.Sockets.ProtocolType)" 
> (tested without signature also)
> 
> ** (/usr/bin/mod-mono-server.exe:4294): WARNING **: cant resolve 
> internal call to "System.Net.Sockets.Socket::Close_internal(intptr)" 
> (tested without signature also)
> 
> ** (/usr/bin/mod-mono-server.exe:4294): WARNING **: cant resolve 
> internal call to "System.Net.Sockets.Socket::Close_internal(intptr)" 
> (tested without signature also)
> [Wed May 05 12:05:40 2004] [error] Failed connecting and child didn't exit!
> 
> I've added some debugging to mod_mono.c to print the command before it's 
> executed:
> [Wed May 05 12:05:37 2004] [error] running '/usr/bin/mono 
> /usr/bin/mod-mono-server.exe --filename /tmp/mod_mono_server 
> --applications /mono:/usr/share/doc/xsp/test,/trond:/home/trond/mono 
> --nonstop'
> 
> If I execute this manually (either as root or as the user Apache 2 is 
> running as), it works.. That is, as long as I change the mode on 
> /tmp/mod_mono_server. All mono-requests against the Apache server is 
> working.
> 
> My system is Debian Testing (fully updated) running Apache 2.0.49. All 
> Mono-packages are compiled from source.
> 
> Anyone know what might cause this?

Mmm, weird problem. That internal call has been there for a long time
and hasn't changed. Ensure you don't have any other mono installation
around. Otherwise, looks like an installation problem.

-Gonzalo