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

[Veleno]

I.Georgiev wrote:
> 
> CentOS 5.2 x86_64
> mono, xsp and mod_mono build from fedora SRPMs
> SELinux is disabled
> /tmp - writable to apache user
> /var/run/mod_mono - owned by apache
> 
> mod_mono still can't cleanup sockets
> the only solution i find is to add this to mod_monoserver2 script this
> code
> 
> MONO_CLEAN_1=/tmp/mod_mono_server_*
> MONO_CLEAN_2=/var/run/mod_mono/*
> 
> if [ -f $MONO_CLEAN_1 ]; then
>         rm $MONO_CLEAN_1
> fi
> if [ -f $MONO_CLEAN_1 ]; then
>         rm $MONO_CLEAN_1
> fi
> 
> If any one can point me to better approach help will be appreciated.
> __________________________________________
> Apache error log
> [Thu Feb 19 11:19:12 2009] [warn] config = 0x
> [Thu Feb 19 11:19:12 2009] [warn] dir_config = 0x
> [Thu Feb 19 11:19:12 2009] [warn] idx = -1
> [Thu Feb 19 11:19:12 2009] [warn] Alias not found. Checking for
> auto-applications.
> [Thu Feb 19 11:19:12 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:12 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:12 2009] [warn] After setup_socket
> [Thu Feb 19 11:19:12 2009] [warn] No backend found, will start a new copy.
> [Thu Feb 19 11:19:12 2009] [warn] Acquiring the
> /var/run/mod_mono/mod_mono_dashboard_XXGLOBAL_1.lock lock for backend
> start
> [Thu Feb 19 11:19:12 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:12 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:12 2009] [warn] forking XXGLOBAL
> [Thu Feb 19 11:19:12 2009] [warn] Applications: (null)
> [Thu Feb 19 11:19:12 2009] [warn] Config file: (null)
> [Thu Feb 19 11:19:12 2009] [warn] Config dir.: (null)
> [Thu Feb 19 11:19:12 2009] [warn] Listen port: (null)
> [Thu Feb 19 11:19:12 2009] [warn] Listen address: (null)
> [Thu Feb 19 11:19:12 2009] [warn] child started
> [Thu Feb 19 11:19:12 2009] [warn] PATH: /sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:12 2009] [warn] serverdir: /usr/bin
> [Thu Feb 19 11:19:12 2009] [warn] PATH after:
> /usr/bin:/sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:12 2009] [warn] Started new backend, sleeping 2s to let
> it configure
> [Thu Feb 19 11:19:14 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:14 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:14 2009] [warn] After setup_socket
> [Thu Feb 19 11:19:14 2009] [warn] No backend found, will start a new copy.
> [Thu Feb 19 11:19:14 2009] [warn] Acquiring the
> /var/run/mod_mono/mod_mono_dashboard_XXGLOBAL_1.lock lock for backend
> start
> [Thu Feb 19 11:19:14 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:14 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:14 2009] [warn] forking XXGLOBAL
> [Thu Feb 19 11:19:14 2009] [warn] Applications: (null)
> [Thu Feb 19 11:19:14 2009] [warn] Config file: (null)
> [Thu Feb 19 11:19:14 2009] [warn] Config dir.: (null)
> [Thu Feb 19 11:19:14 2009] [warn] Listen port: (null)
> [Thu Feb 19 11:19:14 2009] [warn] Listen address: (null)
> [Thu Feb 19 11:19:14 2009] [warn] child started
> [Thu Feb 19 11:19:14 2009] [warn] PATH: /sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:14 2009] [warn] serverdir: /usr/bin
> [Thu Feb 19 11:19:14 2009] [warn] PATH after:
> /usr/bin:/sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:14 2009] [warn] Started new backend, sleeping 2s to let
> it configure
> [Thu Feb 19 11:19:16 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:16 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:16 2009] [warn] After setup_socket
> [Thu Feb 19 11:19:16 2009] [warn] No backend found, will start a new copy.
> [Thu Feb 19 11:19:16 2009] [warn] Acquiring the
> /var/run/mod_mono/mod_mono_dashboard_XXGLOBAL_1.lock lock for backend
> start
> [Thu Feb 19 11:19:16 2009] [warn] Socket file name
> /var/run/mod_mono/mod_mono_server_global
> [Thu Feb 19 11:19:16 2009] [warn] try_connect: -1
> [Thu Feb 19 11:19:16 2009] [warn] forking XXGLOBAL
> [Thu Feb 19 11:19:16 2009] [warn] Applications: (null)
> [Thu Feb 19 11:19:16 2009] [warn] Config file: (null)
> [Thu Feb 19 11:19:16 2009] [warn] Config dir.: (null)
> [Thu Feb 19 11:19:16 2009] [warn] Listen port: (null)
> [Thu Feb 19 11:19:16 2009] [warn] Listen address: (null)
> [Thu Feb 19 11:19:16 2009] [warn] child started
> [Thu Feb 19 11:19:16 2009] [warn] PATH: /sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:16 2009] [warn] serverdir: /usr/bin
> [Thu Feb 19 11:19:16 2009] [warn] PATH after:
> /usr/bin:/sbin:/usr/sbin:/bin:/usr/bin
> [Thu Feb 19 11:19:16 2009] [warn] Started new backend, sleeping 2s to let
> it configure
> [Thu Feb 19 11:19:18 2009] [error] Failed to connect to mod-mono-server
> after several attempts to spawn the process.
> 
> 
> 

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

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