Anonymous | Login | 2024-08-24 22:19 EDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001117 | PacketFence | performance | public | 2010-11-16 10:48 | 2015-02-13 15:24 | |||
Reporter | rbalzard | |||||||
Assigned To | obilodeau | |||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |||
Status | closed | Resolution | open | |||||
Platform | OS | OS Version | ||||||
Product Version | ||||||||
Target Version | Fixed in Version | |||||||
Summary | 0001117: Violations are loaded way too often when monitoring PacketFence status (pfcmd service pf command) | |||||||
Description | By looking at PF logs, I noticed we call read_violations_conf() too often. In pfcmd we see: print "service|command\n"; if ($command !~ /^stop$/){ print "config files|$command\n"; require pf::os; pf::os::read_dhcp_fingerprints_conf(); read_violations_conf(); if (! ($Config{'network'}{'mode'} =~ /vlan/i)) { print "iptables|$command\n"; require pf::iptables; pf::iptables::iptables_generate(); } } Does it mean that we reload violations for every command that is not 'stop' ? if yes, we reload violations on status, watch, stop, restart. I guess we should only load violations on start, no ? | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
![]() |
|
(0001763) rbalzard (administrator) 2010-11-17 09:19 |
Here are the logs for one client for which we have the following cronjob: 45 * * * * /usr/local/pf/bin/pfcmd service pf watch > /dev/null 2>&1 Nov 16 16:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 17:45:04 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 18:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 19:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 20:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 21:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 22:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 16 23:45:04 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 00:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 01:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 02:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 03:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 04:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 05:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 06:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 07:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) Nov 17 08:45:03 pfcmd(0) INFO: All triggers deleted (pf::trigger::trigger_delete_all) So when executing 'service pf watch', PF reloads the violations. |
(0003667) lmunro (administrator) 2015-02-13 15:24 |
These issues are too old to still be relevant. Let's start anew. |
![]() |
|||
Date Modified | Username | Field | Change |
2010-11-16 10:48 | rbalzard | New Issue | |
2010-11-16 10:48 | rbalzard | Status | new => assigned |
2010-11-16 10:48 | rbalzard | Assigned To | => obilodeau |
2010-11-17 09:19 | rbalzard | Note Added: 0001763 | |
2011-01-18 11:41 | obilodeau | Target Version | => 2.1.0 |
2011-03-03 15:15 | obilodeau | Target Version | 2.1.0 => +1 |
2011-03-03 15:18 | obilodeau | Target Version | +1 => +2 |
2015-02-13 15:24 | lmunro | Note Added: 0003667 | |
2015-02-13 15:24 | lmunro | Status | assigned => closed |
Copyright © 2000 - 2012 MantisBT Group |