> > 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) > -------------- next part -------------- [Daniel V Muller]
I have some new information let me bounce this off of you? I was able to reproduce the issue on a new freshly installed PacketFence v5.0.1 and this has brought some new information to light. Unbeknownst to me we had a new ACL implemented on one of our routers that prevented me from connecting via SNMP to some of the switches I'm managing. I setup a fresh PacketFence, imported my categories, switches and nodes, Identified a switch that was issuing SNMP port-security traps and reconfigured this switch to issue the trap to my new server.. The new server reproduces the issue! I have a message in the logs I didn't notice before: Apr 27 13:15:59 pfcmd.pl(10444) INFO: Memory configuration is not valid anymore for key interfaces::management_network in local cached_hash (pfconfig::cached::is_valid) Apr 27 13:16:04 pfcmd.pl(10444) INFO: pf::services::manager, /usr/local/pf/lib/pf/services/manager.pm, 171 (pf::services::manager::dhcpd::generateConfig) Apr 27 13:16:04 pfcmd.pl(10444) INFO: Memory configuration is not valid anymore for key interfaces::listen_ints in local cached_hash (pfconfig::cached::is_valid) Apr 27 13:16:04 pfcmd.pl(10444) ERROR: requesting member ips for an undefined interface... (pf::cluster::members_ips) Apr 27 13:16:04 pfcmd.pl(10444) ERROR: requesting member ips for an undefined interface... (pf::cluster::members_ips) My interfaces have disappeared in the web interface in spite of a correct configuration in networks.conf ... Removing the switch from the configuration and restarting packetfence / mysql have no effect! We believe the ACL was modified to allow communication and in fact I can snmpwalk the switch now. Any clue how to recover PF from this state? ------------------------------------------------------------------------------ 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
