> I think I see the correct number, do not think this is the case;
>
> I did try stopping packetfence and mysql, rotating the logs and then starting
> up with empty logs because I was concerned about old entries in snmptrapd.log
> ...
>
> However I do continue to see the problem even after starting up mysql, then
> packetfence with empty logs.
>
Daniel,
Let’s consider the problems one at a time.
Temporarily shut down or kill pfmon.
See if that fixes the deadlock issue.
pfmon is responsible for purging old entries from the database when they expire.
If there is too much to purge the table may be locked for a long time.
Once that’s out of the way we’ll tackle pfsetvlan
--
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)
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
