[Bsd-sharp-list] problem with xsp/mono/mod-mono
René Woldtmann
rene at woldtmann.com
Fri Nov 9 08:39:01 MST 2007
Hi, Phillip
version of FreeBSD: 6.2
mod_mono/1.2.5
mono/1.2.5.1
Apache/2.2.6
Apache-errorLog:
[Fri Nov 09 13:27:17 2007] [notice] SIGHUP received. Attempting to restart
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_XXGLOBAL_1' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_XXGLOBAL_1' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_vserver1_2' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_vserver2_2' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_XXGLOBAL_1' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_vserver3_2' shared memory dashboard
[Fri Nov 09 13:27:17 2007] [warn] (22)Invalid argument: Failed to
destroy the '/tmp/mod_mono_dashboard_vserver4_2' shared memory dashboard
[Fri Nov 09 13:27:18 2007] [crit] (17)File exists: Failed to create
mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
[Fri Nov 09 13:27:18 2007] [crit] (17)File exists: Failed to create
mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
[Fri Nov 09 13:27:18 2007] [warn] (22)Invalid argument: Failed to enable
the 'httpready' Accept Filter
[Fri Nov 09 13:27:18 2007] [warn] (22)Invalid argument: Failed to enable
the 'httpready' Accept Filter
but, all webs run without errors
Phillip N. schrieb:
> Hi Rene.
>
> I havent had the problem you are describing (the /tmp one).
> What version of FreeBSD do you have?
>
> I just migrate to releng_7. As soon as i have time, ill try to setup
> mod_mono in apache2 (and the equivalent on lighttpd), so i can see if i
> can replicate your problem.
>
>
> El mié, 31-10-2007 a las 00:08 +0100, René Woldtmann escribió:
>> The following errors appear since updating to Mono 1.2.5 during startup
>> of Apache with mod_mono
>>
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver1_2.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver2_2.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver3_2.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:03:18 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver4_2.lock'
>>
>> These error appear during shutdown:
>>
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver1_2.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver2_2.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver3_2.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:17:58 2007] [crit] (17)File exists: Failed to create
>> mutex '/tmp/mod_mono_dashboard_vserver4_2.lock'
>>
>> The server, however, starts correctly. If the files are deleted
>> beforehand the following errors appear:
>>
>> [Fri Oct 05 12:20:05 2007] [crit] (1)Operation not permitted: Failed to
>> create mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:20:05 2007] [crit] (1)Operation not permitted: Failed to
>> create mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:20:05 2007] [crit] (1)Operation not permitted: Failed to
>> create mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>> [Fri Oct 05 12:20:05 2007] [crit] (1)Operation not permitted: Failed to
>> create mutex '/tmp/mod_mono_dashboard_XXGLOBAL_1.lock'
>>
>> Afterwards the same errors as in the beginning appear again
>>
>> And one question about xsp/mono behaviour.
>> On Linux systems XSP/Mono restarts when a dll is changed. It also parses
>> changed aspx files automatically. On FreeBSD this does not happen. A
>> manual restart via the webconsole is necessary to do this. This is
>> impracticable if only one aspx file has changed.
>
> Yes there is something wired with FileSystemWatcher on xsp/FreeBSD.
> I notice that if i dont force xsp to use manager watcher, then xsp
> doesnt even work in my case. Ill see what can be do about this, as time
> permits.
>
> Wired is, that other FSWatcher applications works pretty well..
>
> If you get what is the solution of any of the problems, please tell..
>
>
>
> thanks!
>
>
>> _______________________________________________
>> Bsd-sharp-list mailing list
>> Bsd-sharp-list at forge.novell.com
>>
>> Home Page: http://www.mono-project.com/Mono:FreeBSD
>> Project Site: http://forge.novell.com/mailman/listinfo/bsd-sharp-list
>> IRC: #BSD-Sharp on irc.freenode.org
More information about the Bsd-sharp-list
mailing list