[Mono-aspnet-list] Error 503. Failed to connect to mod-mono-server

I.Georgiev gory at mail.bg
Wed Mar 18 11:30:11 EDT 2009

Veleno wrote:
> Hi,
> your solution is useful when launching process. On my server occurs that
> the mod_mono processes will stop working after several hours of activity.
> In my case, deleting the files in / var / run / mod_mono will also cancel
> all sessions activated by users on web sites that require authentication.
> But the only string of interest in httpd logs is "Failed to connect to
> mod-mono-server after several attempts to spawn the process."
> Do y have an idea of wich issue can cause mod_mono process to freeze after
> several hours of activity?
> Thank you
Sorry i can't help you. My experience with ASP hosting with mono is very
very frustrating.
I try to setup production asp hosting few years ago with mono1 and xsp.
After few weeks of tests i find it completely unreliable. Now i try another
time hoping mod_mono now is mature and stable. Imho it's still completely
unreliable for production. Probably when developers decide to leave xsp
approach and make something like asp_worker process for apache mono asp
hosting grow up beyond the stage of a nice toy.
If you are using single CPU machine i suggest you to take a look on
Grasshoper (http://dev.mainsoft.com/).
But beware they want $$$KK if you are running more than one CPU.
For me asp hosting on linux is closed for another 2-3 years.
I hate java, but there is large numbers of free application servers so for
serious business applications i switch to J2EE.

View this message in context: http://www.nabble.com/Error-503.-Failed-to-connect-to-mod-mono-server-tp22097812p22581454.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.

More information about the Mono-aspnet-list mailing list