I'll definitely look into these changes. I guess a good question could now
be why might my relatively small network of maybe 250 concurrent devices
with < 1000 registered devices even come close to maximum processes? I feel
like this a symptom of a bigger problem somewhere. Our users are mostly
transient. So on a given day we could have 30 devices on and there are no
problems. But when the larger user base is here and there are 250 some odd
devices that's when things crash. But even that is small compared to what
I've seen on this list and only started after the update to 4.4. I'll keep
digging. Thanks again.
Brian
On Oct 3, 2014 12:55 PM, "Louis Munro" <[email protected]> wrote:
> On 2014-10-03, at 13:00 , Brian Lucas <[email protected]> wrote:
>
> Thanks for the quick response. Here you go!
>
> Pastebin for readability.
>
> http://pastebin.com/xNB1V6g6
>
>
> I have to admit this is a new one.
>
> None of what you sent seems wrong *per se*.
>
> I suggest you try changing the AcceptMutex variable for the webservice.
> In conf/httpd.conf.d/webservices change this line
>
> AcceptMutex posixsem
>
> to this
>
> AcceptMutex fcntl
>
> And restart the webservices.
>
>
> Then keep an eye on it to see if it happens again.
>
> Another thing: you are hitting the Maximum number of apache processes you
> can run based on the value of $MaxClients in
> conf/httpd.conf.d/httpd.webservices:
>
> [error] server reached MaxClients setting, consider raising the
> MaxClients setting
>
> Raise that value until that error goes away. Keep an eye on available
> memory.
> Each apache process uses some memory and running out is going to make
> things worse, not better.
>
> You could also lower these two:
>
> $Timeout = "50";
> $KeepAliveTimeout = "10";
>
> To something like:
>
> $Timeout = "5";
> $KeepAliveTimeout = "3";
>
> Although I'm not sure this is going to have as much of an effect on the
> webservices (as opposed to the portal).
>
>
> Keep us posted.
>
> Regards,
> --
> Louis Munro
> [email protected] :: 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)
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
