Hi guys,

I set up a test environment on my Ubuntu 6.0 with Apache 2.0 and Mono
1.1.13.6 (the latest found on repository
http://people.debian.org/~formoer/mono).
The first tests I've made on the website were successful and very good
(I also launched a flood test to check the response time and the
memory load with excellent results), using the following configuration
(in the /etc/apache2/sites-enabled/default configuration file):

        DocumentRoot /path/to/the/web/site
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>
        MonoApplications default "/:/path/to/the/web/site"
        <Directory /path/to/the/web/site/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
                SetHandler mono
        </Directory>

As you can see, I stripped any advanced configuration to mod_mono (eg.
MonoMaxMemory or MonoCPUTime).

Anyway, after a while I started having some troubles, since the site
begun responding with a 500 error code (internal server error).
I checked the Apache error files log and this is what I found:

[Sat Sep 30 16:12:58 2006] [notice] Apache/2.0.55 (Ubuntu)
mod_mono/1.1.10 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.

I tried killing all the mod-mono-server processes pointing to
/path/to/the/web/site and restarting Apache, but with the same result.

Anyone could explain me how to fix this permanently or what
configuration should I adopt to avoid such this error in production?

Thanks
Antonello
_______________________________________________
Mono-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to