[peruser] Testing peruser 0.4rc1 // warns logs //

Lazy lazy404 at gmail.com
Thu Dec 3 11:59:34 MST 2009


2009/12/2 WebMaster / XTRM Hosting Services <webmaster at xtrmhost.com>:
> Hi Lazy!
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
> <is it always  (9)Bad file desc... ?
>
> Yes! Always the same I have a lot...
> [Tue Dec 01 12:49:43 2009] [warn] (9)Bad file descriptor:
> apr_socket_opt_set: (TCP_NODELAY)
>
> <could you recompile with
> <#define MPM_PERUSER_DEBUG
> <it generates loads of logs so watch out
>
> I try this. What should verify in specific?
there will be information on what 9 filedescrptor is refering to

try ls -l /proc/pidof a multiplexer/fd/

maybe this will give up some more info

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> <do you have keep-alive enabled ?
>
>
> I have it on, when I disable the processes they go crazy!!!

>
> This is my httpd.conf
>        TimeOut 120
>        KeepAlive On
>        MaxKeepAliveRequests 0
>        KeepAliveTimeout 10
> My peruser.conf
>
>        <IfModule peruser.c>
>                MinMultiplexers 5
>                MaxMultiplexers 20

more multiplexers might be usefull we use about 40

>                #Multiplexer ${APACHE_RUN_USER} ${APACHE_RUN_GROUP}
>                ProcessorWaitTimeout 2 10
>                ServerLimit 850
>                MaxClients 800
>                MaxRequestsPerChild 10000
>                MinProcessors 10
>                MinSpareProcessors 5

how many vhosts do you have ?

I whould set MinProcessors and MinSpareProcessors to 0 or 1 maybe 2

>                MaxProcessors 100
>                IdleTimeout 60
>                ExpireTimeout 300
>        </IfModule>
>
> Can you comment some better configuration with or without keepalive? Is it
> better to use keepalive or not? Thanks in advance!
KeepAlive will use more server resources but it will be faster,
turning keepalive off usually lowers serwers load


More information about the Peruser mailing list