[Mono-aspnet-list] Failed to connect to mod-mono-server after several attempts to spawn the process.
denis300
denis300 at gmail.com
Tue Mar 17 16:29:39 EDT 2009
Veleno wrote:
>
>
>
> denis300 wrote:
>>
>>
>>
>> denis300 wrote:
>>>
>>> Hi, i'm running fc9, and attempting to get apache working with mono. my
>>> error log shows
>>> [Mon Mar 16 01:44:30 2009] [error] Failed to connect to mod-mono-server
>>> after several attempts to spawn the process.
>>>
>>> i attempted to start /usr/bin/mod-mono-server and it still gave the same
>>> error: (selinux is disabled)
>>>
>>> Service Temporarily Unavailable
>>>
>>> The server is temporarily unable to service your request due to
>>> maintenance downtime or capacity problems. Please try again later.
>>>
>>> Any help on fixing this is truly appreciated. or some suggestions on
>>> where to look to fix it. Thanks.
>>>
>> ** (/usr/lib64/mono/2.0/mod-mono-server2.exe:25658): CRITICAL **:
>> _wapi_shm_file_open: shared file
>> [/var/run/.wapi/shared_data-joormama-Linux-x86_64-328-12-0] open error:
>> No such file or directory
>>
>> ** (/usr/lib64/mono/2.0/mod-mono-server2.exe:25658): CRITICAL **:
>> _wapi_shm_attach: shared file
>> [/var/run/.wapi/shared_data-joormama-Linux-x86_64-328-12-0] open error
>> **
>> ERROR:shared.c:349:shm_semaphores_init: assertion failed: (tmp_shared !=
>> NULL)
>>
>> ** (/usr/lib64/mono/2.0/mod-mono-server2.exe:25658): WARNING **: Thread
>> (nil) may have been prematurely finalized
>> Stacktrace:
>>
>>
>> ** (/usr/lib64/mono/2.0/mod-mono-server2.exe:25658): WARNING **: Thread
>> (nil) may have been prematurely finalized
>>
>>
>>
>
> Hi,
> i'm hosting about 10 websites on a fc10 64bit using apache and mono.
> With mono 1.9 everything worked fine , but now that i upgraded to 2.2 i've
> a lot of problems.
>
> The most important of all is that often websites are down showing the
> message:
> "The server is temporarily unable to service your request due to
> maintenance downtime or capacity problems. Please try again later. "
>
> and in my httpd log:
> "Failed to connect to mod-mono-server after several attempts to spawn the
> process"
>
> I tryed to configure http.conf for autorestart mono processes after
> several request served or time elapsed but the problem still persist.
>
> I think it could be a problem with files located in /var/run/mod_mono or
> in /tmp because if i restart apache , mod_mono process are still executing
> . I have to kill them manually and clean /var/run/mod_mono and /tmp before
> restart apache again.
>
> I tryed wirh apachectl too but the problem still remain the same, mod_mono
> process doesn't restart.
>
> After restarted all (apache , mod_mono and cleaned dirs) all websites
> works fine for some hour but random, one of them shows the message "The
> server is temp...."
>
> Any idea?
>
> Thx
>
>
>
I've figured my problem out. It was the permissions.
--
View this message in context: http://www.nabble.com/Failed-to-connect-to-mod-mono-server-after-several-attempts-to-spawn-the-process.-tp22532233p22567198.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.
More information about the Mono-aspnet-list
mailing list