PacketFence - BTS - PacketFence
View Issue Details
0001315PacketFencecorepublic2011-10-20 11:302011-10-24 20:17
obilodeau 
obilodeau 
normalminoralways
closedfixed 
 
3.0.23.0.2 
53cee866bf422b7e84b41afbc9ece33e9299caa6
0001315: false error on de-registration
Oct 20 11:26:38 pfmon(1) WARN: Error trying to run command: /usr/local/pf/bin/pfcmd manage deregister 
00:00:aa:ac:46:a2 called from nodes_maintenance. Child exited with non-zero value 1 (pf::util::pf_run)



The warning is a false positive.
No tags attached.
Issue History
2011-10-20 11:30obilodeauNew Issue
2011-10-21 09:36obilodeauStatusnew => assigned
2011-10-21 09:36obilodeauAssigned To => obilodeau
2011-10-21 09:38obilodeauNote Added: 0002370
2011-10-21 10:11obilodeaumtn revision => 53cee866bf422b7e84b41afbc9ece33e9299caa6
2011-10-21 10:11obilodeauNote Added: 0002371
2011-10-21 10:11obilodeauStatusassigned => resolved
2011-10-21 10:11obilodeauFixed in Version => +1
2011-10-21 10:11obilodeauResolutionopen => fixed
2011-10-24 20:15obilodeauTarget Version+1 => 3.0.2
2011-10-24 20:15obilodeauNote Added: 0002379
2011-10-24 20:16obilodeauStatusresolved => closed
2011-10-24 20:17obilodeauFixed in Version+1 => 3.0.2

Notes
(0002370)
obilodeau   
2011-10-21 09:38   
Looking through the logs, I find more of them:

Oct 20 16:25:35 pfsetvlan(11) WARN: Error trying to run command: /usr/local/pf/bin/pfcmd_vlan -deauthenticateDot1x -switch 10.0.0.4 -mac 00:1b:b1:8b:82:13 called from handleTrap. Child exited with non-zero value 255 (pf::util::pf_run)

It seems that we haven't paid much attention to the meaningfulness of our exit codes...
(0002371)
obilodeau   
2011-10-21 10:11   
Unable to reproduce the pfcmd_vlan one. I fixed the manage deregister one.
(0002379)
obilodeau   
2011-10-24 20:15   
fix released in 3.0.2