PacketFence - BTS - PacketFence
View Issue Details
0001466PacketFenceweb adminpublic2012-06-13 19:552012-06-15 09:20
barryq 
obilodeau 
normalmajorsometimes
resolvedno change required 
3.3.2 
3.4.0 
0001466: Changing node category produces error
When changing the node category either from "No Category" to a defined category, or from a defined category to "No Category" the following error is produced:

Error: Problems executing 'PFCMD node edit a0:6c:ec:d2:a8:81 pid="<hidden>", category="guest", status="reg", bypass_vlan="", voip="no", detect_date="2012-06-13 16:47:07", regdate="2012-06-13 16:47:12", unregdate="", last_arp="", last_dhcp="2012-06-13 16:47:28", lastskip="", notes="AUTO-REGISTERED"'

Command not understood. (pfcmd grammar test failed at line 209.)
No tags attached.
Issue History
2012-06-13 19:55barryqNew Issue
2012-06-14 09:12obilodeauStatusnew => assigned
2012-06-14 09:12obilodeauAssigned To => obilodeau
2012-06-14 09:16obilodeauNote Added: 0002768
2012-06-14 13:20barryqNote Added: 0002783
2012-06-14 14:07obilodeauNote Added: 0002784
2012-06-14 14:07obilodeauStatusassigned => feedback
2012-06-14 20:36barryqNote Added: 0002793
2012-06-15 09:20obilodeauNote Added: 0002794
2012-06-15 09:20obilodeauStatusfeedback => resolved
2012-06-15 09:20obilodeauFixed in Version => 3.4.0
2012-06-15 09:20obilodeauResolutionopen => no change required

Notes
(0002768)
obilodeau   
2012-06-14 09:16   
I would assume there's an illegal character in pid. Sorry for the obscure error message.

These are allowed:

&=?()/,0-9a-zA-Z_*.-:;@ +!^[]|#

Before 3.4.0 backslashes weren't allowed. That was fixed in 3.4.0. All characters that could be interpreted in the shell need to be quoted.

If you are sure that it isn't this let me know and I'll tell you how to turn on the parser debugger.
(0002783)
barryq   
2012-06-14 13:20   
That would explain why the problem doesn't occur every time. I think you are right about the backslashes in the PID. I will get the to the upgrade today or tomorrow and let you know.
(0002784)
obilodeau   
2012-06-14 14:07   
sounds good
(0002793)
barryq   
2012-06-14 20:36   
I've updated to 3.4.0 and I can't reproduce the error. But I couldn't produce it consistently before anyway. I guess we should just close this and if it pops up again I can open a new ticket.
(0002794)
obilodeau   
2012-06-15 09:20   
Sounds good. Thanks!