|
From: Louis M. <lm...@in...> - 2015-07-10 13:57:26
|
We deliberately set the MaxClient to a low value for the admin and graphite servers. That was done so that they don’t use memory that could be better used by the captive portal. Unless you grant access to those to a large number of people there should not be any adverse effect, apart maybe from the admin or graphite dashboard being slower than otherwise. If you have to resources for it, go ahead and raise those values. If you don’t have a problem, it’s probably not worth it anyway. Regards, -- Louis Munro lm...@in... :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) On Jul 8, 2015, at 16:05 , Leja, Maciej <ML...@de...> wrote: > So I keep getting these in the logs – and the error/ emerg ticket is worrisome… thoughts? > > logs/httpd.admin.error:[Tue Jun 30 11:58:12 2015] [error] server reached MaxClients setting, consider raising the MaxClients setting > logs/httpd.graphite.error:[Thu May 28 15:03:50 2015] [error] server reached MaxClients setting, consider raising the MaxClients setting > logs/portal_error_log:[Wed May 13 14:56:56 2015] [emerg] mod_qos(007): could not determine MaxClients/MaxRequestWorkers! You MUST set this directive within the Apache configuration file. > > There are only about 2 of us using this system for now – no one has access to it so even 2 is less than the 4 allowed on httpd.admin conf file… > > Thanks! > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/_______________________________________________ > PacketFence-users mailing list > Pac...@li... > https://lists.sourceforge.net/lists/listinfo/packetfence-users |