On 2014-10-03, at 14:17 , Brian Lucas <[email protected]> wrote:
> 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.
As you say, one may be a side-effect of the other.
I don't think this is load related.
I think you hit the MaxClient limit because of this issue, not the other way
around.
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
