PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000874PacketFenceerror-handlingpublic2009-12-08 20:082011-01-26 15:42
Reporterobilodeau 
Assigned Toobilodeau 
PrioritynormalSeveritytweakReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target Version2.0.0Fixed in Version2.0.0 
fixed in git revision
fixed in mtn revision6272b83016fe4f8264cbfdce928af5b55cd32b15
Summary0000874: pfcmd_vlan should log at the same place as everyone else
Descriptionmaking wireless a lot harder to troubleshoot because deassociate traps leave no clue to what happened

solution: port bin/pfcmd_vlan to use conf/log.conf like everyone else!
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0001130closed  binaries should have an option to log on stdout 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-12-08 20:08obilodeauNew Issue
2009-12-08 20:08obilodeauStatusnew => assigned
2009-12-08 20:08obilodeauAssigned To => obilodeau
2010-04-15 17:43obilodeauProjectPacketFence 1.9 => PacketFence
2010-08-04 09:57obilodeauNote Added: 0001623
2010-08-04 09:57obilodeauTarget Version => 1.10.0
2010-08-04 09:58obilodeauNote Added: 0001624
2010-11-19 14:25obilodeauTarget Version1.10.0 => 2.0.0
2010-11-26 11:20obilodeauRelationship addedrelated to 0001130
2010-11-26 11:26obilodeaumtn revision => 6272b83016fe4f8264cbfdce928af5b55cd32b15
2010-11-26 11:26obilodeauNote Added: 0001780
2010-11-26 11:26obilodeauStatusassigned => resolved
2010-11-26 11:26obilodeauFixed in Version => trunk
2010-11-26 11:26obilodeauResolutionopen => fixed
2010-12-15 11:37obilodeauFixed in Versiontrunk => 2.0.0
2011-01-26 15:42obilodeauStatusresolved => closed

Notes
(0001623)
obilodeau   
2010-08-04 09:57   
Once the fix is committed open a new feature request to have the output duplicated to stdout if the -verbose flag is present (with log4perl levels):

       -verbose             log verbosity level
                              0 : fatal messages
                              1 : warn messages
                              2 : info messages
                              3 : debug
                              4 : trace


Or implement it right away if it's easy to do with log4perl and it sounds valuable.
(0001624)
obilodeau   
2010-08-04 09:58   
patch from Josh:
--- pf2010/bin/pfcmd_vlan	2010/07/07 21:26:56	1
+++ pf2010/bin/pfcmd_vlan	2010/08/02 20:16:16	59
@@ -215,12 +215,13 @@
 } else {
     $logLevel = $TRACE;
 }
-Log::Log4perl->easy_init(
-    {   level  => $logLevel,
-        layout => '%d (%r) %M%n    %m %n'
-    }
-);
-my $logger = Log::Log4perl->get_logger('');
+#Log::Log4perl->easy_init(
+#    {   level  => $logLevel,
+#        layout => '%d (%r) %M%n    %m %n'
+#    }
+#);
+Log::Log4perl->init("/usr/local/pf/conf/log.conf");
+my $logger = Log::Log4perl->get_logger('pfcmd_vlan');

 my $switchFactory = new pf::SwitchFactory(
     -configFile => INSTALL_DIR . '/conf/switches.conf' );
(0001780)
obilodeau   
2010-11-26 11:26   
pfcmd_vlan now logs to logs/packetfence.log and if -verbose flag is on, it'll log both to STDOUT and logs/packetfence.log