[Mono-list] mod_mono problems
I've installed Mono on OS X and compiled and installed mod_mono from source (./configure && make && make install) which has all gone smoothly but I'm having some trouble launching Apache. I've gone the AutoHosting route and added "Include /etc/apache2/mod_mono.conf" to my httpd.conf file but with this line Apache wont launch. If I remove the line then Apache loads fine but not when it's included. The error I'm getting in the logs is this: 03/03/2008 22:25:33 org.apache.httpd[59793] httpd: Syntax error on line 485 of /private/etc/apache2/httpd.conf: Syntax error on line 8 of /etc/apache2/mod_mono.conf: Cannot load /usr/libexec/apache2/mod_mono.so into server: dlopen(/usr/libexec/apache2/mod_mono.so, 10): image not found Now, /usr/libexec/apache2/mod_mono.so definitely exists. To prove it, this is the output from "sudo find / -name mod_mono.so": darrells-imac:~ Darrell$ sudo chmod /usr/libexec/apache2/ darrells-imac:~ Darrell$ sudo find / -name mod_mono.so /Users/Darrell/Downloads/mod_mono-1.2.6/src/.libs/mod_mono.so /usr/libexec/apache2/mod_mono.so darrells-imac:~ Darrell$ Does anyone have any idea what I could have done wrong? ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mod_mono problems
On Tue, 2005-05-24 at 11:06 +0100, Chris Aitken wrote: > Hi Neale, > > Sorry to contact you offlist. The problem you had here: > http://galactus.ximian.com/pipermail/mono-list/2005-April/026637.html > > Other than rebuilding from SVN - was there any cure? > > I have installed monobundle 1.1.7, and have been running mod_mono 1.0.5-2 > (from FC2 rpm). I have upgraded to 1.0.9-0 (from FC3 rpm), and like you, I > have the following message in /var/log/apache2/error.log: > > [Tue May 24 11:01:02 2005] [notice] Apache/2.0.54 (Debian GNU/Linux) > mod_mono/1.0.9 PHP/4.3.10-13 configured -- resuming normal operations > Another mod-mono-server with the same arguments is already running. > Another mod-mono-server with the same arguments is already running. > Another mod-mono-server with the same arguments is already running. > Another mod-mono-server with the same arguments is already running. That message is just informative. It means that apache spawned a few childs and when each of them loaded mod_mono, they tried to spawn mod-mono-server. In the end only one succeeds and the others print that. -Gonzalo ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mod_mono problems
Hi Neale, Sorry to contact you offlist. The problem you had here: http://galactus.ximian.com/pipermail/mono-list/2005-April/026637.html Other than rebuilding from SVN - was there any cure? I have installed monobundle 1.1.7, and have been running mod_mono 1.0.5-2 (from FC2 rpm). I have upgraded to 1.0.9-0 (from FC3 rpm), and like you, I have the following message in /var/log/apache2/error.log: [Tue May 24 11:01:02 2005] [notice] Apache/2.0.54 (Debian GNU/Linux) mod_mono/1.0.9 PHP/4.3.10-13 configured -- resuming normal operations Another mod-mono-server with the same arguments is already running. Another mod-mono-server with the same arguments is already running. Another mod-mono-server with the same arguments is already running. Another mod-mono-server with the same arguments is already running. (FC2/3 rpms were converted via alien into debs). Any ideas? Regards, Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems
Dustin, Tks for advise. I had an old Mono from SuSE in /usr and I installed latest in /usr/local. Some conflict somewhere resulted. After deleting everything and reinstalling I have it working. Hopefully this may be useful for the next user :) What is the 'correct' method for running .aspx code outside a browser? But I am not there yet, I now get in Apache logs: [Tue May 17 16:39:15 2005] [error] No application found for /demo/index.aspx If you happen to know this one, I would be interested :) Much thanks, Ben. Dustin Aleksiuk wrote: I had this exact issue a couple of weeks ago. I'm afraid I can't remember how I fixed it, but I recompiled mod_mono with debug messages turned on and it was obvious. It was a configuration issue though, in my case. I had something wrong in my apache config. If you didn't do this already, I recommend getting the XSP samples going first, before trying your own .aspx. Not much help I'm afraid. :) Dustin [EMAIL PROTECTED] wrote: - To: mono-list@lists.ximian.com From: Ben Clewett <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] Date: 05/17/2005 03:47PM Subject: [Mono-list] mod_mono problems Sorry if this posting is duplicated. Dear List, Is this the correct list for mod_mono? I have closely followed the compilation INSTALL and README for mono and mod_mono. Mono works perfectly: '$mono HelloWorld.exe' When I try calling the given mod_mono test program 'index.aspx' I get this in my apache logs: [Tue May 17 15:35:01 2005] [notice] child pid 15197 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15198 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15199 exit signal Segmentation fault (11) The browser returns no page. I am using the given apache2 in SuSE 9.1. Have I done anything wrong? Regards, Ben Clewett. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems
I had this exact issue a couple of weeks ago. I'm afraid I can't remember how I fixed it, but I recompiled mod_mono with debug messages turned on and it was obvious. It was a configuration issue though, in my case. I had something wrong in my apache config. If you didn't do this already, I recommend getting the XSP samples going first, before trying your own .aspx. Not much help I'm afraid. :) Dustin [EMAIL PROTECTED] wrote: - To: mono-list@lists.ximian.com From: Ben Clewett <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] Date: 05/17/2005 03:47PM Subject: [Mono-list] mod_mono problems Sorry if this posting is duplicated. Dear List, Is this the correct list for mod_mono? I have closely followed the compilation INSTALL and README for mono and mod_mono. Mono works perfectly: '$mono HelloWorld.exe' When I try calling the given mod_mono test program 'index.aspx' I get this in my apache logs: [Tue May 17 15:35:01 2005] [notice] child pid 15197 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15198 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15199 exit signal Segmentation fault (11) The browser returns no page. I am using the given apache2 in SuSE 9.1. Have I done anything wrong? Regards, Ben Clewett. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] mod_mono problems
Sorry if this posting is duplicated. Dear List, Is this the correct list for mod_mono? I have closely followed the compilation INSTALL and README for mono and mod_mono. Mono works perfectly: '$mono HelloWorld.exe' When I try calling the given mod_mono test program 'index.aspx' I get this in my apache logs: [Tue May 17 15:35:01 2005] [notice] child pid 15197 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15198 exit signal Segmentation fault (11) [Tue May 17 15:35:01 2005] [notice] child pid 15199 exit signal Segmentation fault (11) The browser returns no page. I am using the given apache2 in SuSE 9.1. Have I done anything wrong? Regards, Ben Clewett. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems after upgrade to beta1
El jue, 06-05-2004 a las 11:54, Trond Arve Nordheim escribió: > Gonzalo Paniagua Javier wrote: > > El mié, 05-05-2004 a las 14:16, Trond Arve Nordheim escribió: > >>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) > > > 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. > > I installed the previous versions from source, and just installed the > beta1 version over the old one - that will do, won't it? I'm no completely sure of this. May be removing everything related to mono and reinstalling helps. > > The strange thing is that it works when I run the command manually, as I > mentioned.. It's just when Apache starts it it's a problem.. And I run > exactly the same command as mod_mono does - both as root and www-data.. May be you have a copy in /usr and other in /usr/local and depending on where you installed mod_mono it uses one or the other. -Gonzalo ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems after upgrade to beta1
Gonzalo Paniagua Javier wrote: El mié, 05-05-2004 a las 14:16, Trond Arve Nordheim escribió: 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) 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. I installed the previous versions from source, and just installed the beta1 version over the old one - that will do, won't it? The strange thing is that it works when I run the command manually, as I mentioned.. It's just when Apache starts it it's a problem.. And I run exactly the same command as mod_mono does - both as root and www-data.. -- Trond Arve Nordheim - "This message is ROT13-encrypted twice for extra security" ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems after upgrade to beta1
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 ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] mod_mono problems after upgrade to beta1
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? -- Trond Arve Nordheim - "This message is ROT13-encrypted twice for extra security" ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mod_mono problems
Hola Rogelio, Currently it only works with prefork MPM. I can reproduce the problem and I have set aside some time this weekend to look into it, unless somebody figures it out first (in that case he/she should send a patch please ;) > Thanks Daniel for your response. Apache segfaults, thats the only error I got > in logs/erros_log. Yes, My apache is compiled using the the worker MPM. I > remember that I installed the mod_module the first time it was available to the > public some time ago and it worked fine but at that time I was using prefork > MPM. I cannot use the RPM because it is compiled for the version of apache that > comes in RH 8.0 and the module fails to load in 2.0.44. > > Let me know if you find any solution. > > Thanks for you help. > > Rogelio > > > > > The warnings while compiling ModMono.dll are normal, because some functions > > are > > declared as being provided by Mono, but the compiler cant find them in the > > runtime (that is ok, they will be provided by mod_mono, not Mono) > > When you mention crashes, I guess you refer to segfaults or do you get some > > other errors? > > Are you using a threaded MPM, like the worker MPM? That is the only time I > > have seen segfaults (I am currently looking at this, Alp Toker mentioned it > > to me) > > Have you tried mod_mono RPM? > > If that does not fix it, can you email me off-list your error_log? > > > > Thanks! > > > > Daniel > > > > > > > Hi, > > > > > > I have a RH8.0 box with mono-0.23 installed from RPMs. I have compiled a > > > couple of small programs on it without any problem but I am getting a lot > > of > > > warnings compiling ModMono.dll. The result of this compilation > > (ModMono.dll) > > > crashes my apache 2.0.44 everytime I try to access /mono. The xsp server > > > works fine when started as a standalone application. I also tried with the > > > code in cvs as it was last night with the same results. The apache module > > > (mod_mono.so) compiles and installs without any problem. > > > > > > It seems there is a problem with my mono install, I removed the installed > > > RPMs and made sure there was no remaining files on the system and then > > > installed again the RPMs getting the same results. > > > > > > Is there anything I can do to make it work? > > > > > > Thanks > > > > > > RJ > > > > > > > > > mcs /debug+ /debug:full /nologo /r:System.Web.dll /target:library > > > /out:ModMono.dll ApacheApplicationHost.cs ApacheWorkerRequest.cs > > > MonoWorkerRequest.cs IApplicationHost.cs Request.cs > > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > > "Apache.Web.Request::GetConnectionInternal(intptr)" (tested without > > > signature also) > > > Your mono runtime and corlib are out of sync. > > > When you update one from cvs you need to update, compile and install > > > the other too. > > > Do not report this as a bug unless you're sure you have updated correctly: > > > you probably have a broken mono install. > > > If you see other errors or faults after this message they are probably > > > related > > > and you need to fix your mono install first. > > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > > "Apache.Web.Request::GetHttpVersionInternal(intptr)" (tested without > > > signature also) > > > Your mono runtime and corlib are out of sync. > > > When you update one from cvs you need to update, compile and install > > > the other too. > > > Do not report this as a bug unless you're sure you have updated correctly: > > > you probably have a broken mono install. > > > If you see other errors or faults after this message they are probably > > > related > > > and you need to fix your mono install first. > > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > > "Apache.Web.Request::GetHttpVerbNameInternal(intptr)" (tested without > > > signature also) > > > Your mono runtime and corlib are out of sync. > > > When you update one from cvs you need to update, compile and install > > > the other too. > > > Do not report this as a bug unless you're sure you have updated correctly: > > > you probably have a broken mono install. > > > If you see other errors or faults after this message they are probably > > > related > > > and you need to fix your mono install first. > > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > > "Apache.Web.Request::SendResponseFromMemoryInternal(intptr,byte[],int)" > > > (tested without signature also) > > > Your mono runtime and corlib are out of sync. > > > When you update one from cvs you need to update, compile and install > > > the other too. > > > Do not report this as a bug unless you're sure you have updated correctly: > > > you probably have a broken mono install. > > > If you see other errors or faults after this message they are probably > > > related > > > and you need to fix your mono install first. > > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal ca
Re: [Mono-list] mod_mono problems
Thanks Daniel for your response. Apache segfaults, thats the only error I got in logs/erros_log. Yes, My apache is compiled using the the worker MPM. I remember that I installed the mod_module the first time it was available to the public some time ago and it worked fine but at that time I was using prefork MPM. I cannot use the RPM because it is compiled for the version of apache that comes in RH 8.0 and the module fails to load in 2.0.44. Let me know if you find any solution. Thanks for you help. Rogelio > > The warnings while compiling ModMono.dll are normal, because some functions > are > declared as being provided by Mono, but the compiler cant find them in the > runtime (that is ok, they will be provided by mod_mono, not Mono) > When you mention crashes, I guess you refer to segfaults or do you get some > other errors? > Are you using a threaded MPM, like the worker MPM? That is the only time I > have seen segfaults (I am currently looking at this, Alp Toker mentioned it > to me) > Have you tried mod_mono RPM? > If that does not fix it, can you email me off-list your error_log? > > Thanks! > > Daniel > > > > Hi, > > > > I have a RH8.0 box with mono-0.23 installed from RPMs. I have compiled a > > couple of small programs on it without any problem but I am getting a lot > of > > warnings compiling ModMono.dll. The result of this compilation > (ModMono.dll) > > crashes my apache 2.0.44 everytime I try to access /mono. The xsp server > > works fine when started as a standalone application. I also tried with the > > code in cvs as it was last night with the same results. The apache module > > (mod_mono.so) compiles and installs without any problem. > > > > It seems there is a problem with my mono install, I removed the installed > > RPMs and made sure there was no remaining files on the system and then > > installed again the RPMs getting the same results. > > > > Is there anything I can do to make it work? > > > > Thanks > > > > RJ > > > > > > mcs /debug+ /debug:full /nologo /r:System.Web.dll /target:library > > /out:ModMono.dll ApacheApplicationHost.cs ApacheWorkerRequest.cs > > MonoWorkerRequest.cs IApplicationHost.cs Request.cs > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > "Apache.Web.Request::GetConnectionInternal(intptr)" (tested without > > signature also) > > Your mono runtime and corlib are out of sync. > > When you update one from cvs you need to update, compile and install > > the other too. > > Do not report this as a bug unless you're sure you have updated correctly: > > you probably have a broken mono install. > > If you see other errors or faults after this message they are probably > > related > > and you need to fix your mono install first. > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > "Apache.Web.Request::GetHttpVersionInternal(intptr)" (tested without > > signature also) > > Your mono runtime and corlib are out of sync. > > When you update one from cvs you need to update, compile and install > > the other too. > > Do not report this as a bug unless you're sure you have updated correctly: > > you probably have a broken mono install. > > If you see other errors or faults after this message they are probably > > related > > and you need to fix your mono install first. > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > "Apache.Web.Request::GetHttpVerbNameInternal(intptr)" (tested without > > signature also) > > Your mono runtime and corlib are out of sync. > > When you update one from cvs you need to update, compile and install > > the other too. > > Do not report this as a bug unless you're sure you have updated correctly: > > you probably have a broken mono install. > > If you see other errors or faults after this message they are probably > > related > > and you need to fix your mono install first. > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > "Apache.Web.Request::SendResponseFromMemoryInternal(intptr,byte[],int)" > > (tested without signature also) > > Your mono runtime and corlib are out of sync. > > When you update one from cvs you need to update, compile and install > > the other too. > > Do not report this as a bug unless you're sure you have updated correctly: > > you probably have a broken mono install. > > If you see other errors or faults after this message they are probably > > related > > and you need to fix your mono install first. > > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > > "Apache.Web.Request::SetResponseHeaderInternal(intptr,string,string)" > > (tested without signature also) > > Your mono runtime and corlib are out of sync. > > When you update one from cvs you need to update, compile and install > > the other too. > > Do not report this as a bug unless you're sure you have updated correctly: > > you probably have a broken mono install. > > If you see other errors or faults after this message
Re: [Mono-list] mod_mono problems
The warnings while compiling ModMono.dll are normal, because some functions are declared as being provided by Mono, but the compiler cant find them in the runtime (that is ok, they will be provided by mod_mono, not Mono) When you mention crashes, I guess you refer to segfaults or do you get some other errors? Are you using a threaded MPM, like the worker MPM? That is the only time I have seen segfaults (I am currently looking at this, Alp Toker mentioned it to me) Have you tried mod_mono RPM? If that does not fix it, can you email me off-list your error_log? Thanks! Daniel > Hi, > > I have a RH8.0 box with mono-0.23 installed from RPMs. I have compiled a > couple of small programs on it without any problem but I am getting a lot of > warnings compiling ModMono.dll. The result of this compilation (ModMono.dll) > crashes my apache 2.0.44 everytime I try to access /mono. The xsp server > works fine when started as a standalone application. I also tried with the > code in cvs as it was last night with the same results. The apache module > (mod_mono.so) compiles and installs without any problem. > > It seems there is a problem with my mono install, I removed the installed > RPMs and made sure there was no remaining files on the system and then > installed again the RPMs getting the same results. > > Is there anything I can do to make it work? > > Thanks > > RJ > > > mcs /debug+ /debug:full /nologo /r:System.Web.dll /target:library > /out:ModMono.dll ApacheApplicationHost.cs ApacheWorkerRequest.cs > MonoWorkerRequest.cs IApplicationHost.cs Request.cs > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::GetConnectionInternal(intptr)" (tested without > signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::GetHttpVersionInternal(intptr)" (tested without > signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::GetHttpVerbNameInternal(intptr)" (tested without > signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::SendResponseFromMemoryInternal(intptr,byte[],int)" > (tested without signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::SetResponseHeaderInternal(intptr,string,string)" > (tested without signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.Web.Request::GetRequestHeaderInternal(intptr,string)" (tested > without signature also) > Your mono runtime and corlib are out of sync. > When you update one from cvs you need to update, compile and install > the other too. > Do not report this as a bug unless you're sure you have updated correctly: > you probably have a broken mono install. > If you see other errors or faults after this message they are probably > related > and you need to fix your mono install first. > ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to > "Apache.
[Mono-list] mod_mono problems
Hi, I have a RH8.0 box with mono-0.23 installed from RPMs. I have compiled a couple of small programs on it without any problem but I am getting a lot of warnings compiling ModMono.dll. The result of this compilation (ModMono.dll) crashes my apache 2.0.44 everytime I try to access /mono. The xsp server works fine when started as a standalone application. I also tried with the code in cvs as it was last night with the same results. The apache module (mod_mono.so) compiles and installs without any problem. It seems there is a problem with my mono install, I removed the installed RPMs and made sure there was no remaining files on the system and then installed again the RPMs getting the same results. Is there anything I can do to make it work? Thanks RJ mcs /debug+ /debug:full /nologo /r:System.Web.dll /target:library /out:ModMono.dll ApacheApplicationHost.cs ApacheWorkerRequest.cs MonoWorkerRequest.cs IApplicationHost.cs Request.cs ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::GetConnectionInternal(intptr)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::GetHttpVersionInternal(intptr)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::GetHttpVerbNameInternal(intptr)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::SendResponseFromMemoryInternal(intptr,byte[],int)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::SetResponseHeaderInternal(intptr,string,string)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::GetRequestHeaderInternal(intptr,string)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::AliasMatches(string,string)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug unless you're sure you have updated correctly: you probably have a broken mono install. If you see other errors or faults after this message they are probably related and you need to fix your mono install first. ** (/usr/bin/mcs.exe:13055): WARNING **: cant resolve internal call to "Apache.Web.Request::GetServerVariableInternal(intptr,string)" (tested without signature also) Your mono runtime and corlib are out of sync. When you update one from cvs you need to update, compile and install the other too. Do not report this as a bug u
