PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000731PacketFencecorepublic2009-06-15 08:032012-06-15 10:03
Reporterobilodeau 
Assigned Toobilodeau 
PriorityurgentSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version3.0.0 
Summary0000731: Can't locate object method "ping" via package "eth1" db.pm line 66
Descriptiondefine two internal interfaces, start pfmon:

thread failed to start: Can't locate object method "ping" via package "eth1"
    (perhaps you forgot to load "eth1"?) at /usr/local/pf/lib/pf/db.pm line 66 (0000001)
    (W threads)(S) The entry point function of threads->create() failed for some reason.
TagsNo tags attached.
fixed in git revision
fixed in mtn revision
Attached Filespatch file icon pf-1.8.3-multiple-interface-with-mode-arp-workaround.patch [^] (1,427 bytes) 2009-06-19 23:50 [Show Content]

- Relationships
related to 0001065closedobilodeau pfdhcplistener warnings / crashes since 1.9.0 or mod_perl? 

-  Notes
(0001279)
user4
2009-06-15 11:54

Issue seems to be related to the usage of Net::Pcap and the loop function.

See in particular http://search.cpan.org/~saper/Net-Pcap-0.16/Pcap.pm#LIMITATIONS [^] which mentions:
"At present, only one callback function and user data scalar can be current at any time as they are both stored in global variables."

This could maybe explain why the db_connect function is called with the wrong arguments when pfmon is running several arp threads on different interfaces.

One possible solution might be to create a pfarplistener daemon (similar to pfdhcplistener) and remove this functionality from pfmon (would be a nice cleanup anyway) and pfarplistener would have to be called with one (1) interface ... this way we are getting around the several Net::Pcap threads
(0001286)
treker (reporter)
2009-06-19 23:51

work around uploaded
(0001515)
obilodeau (reporter)
2010-04-19 16:25

Hi Treker,

I'm triaging for 1.8.8 and I'm interested in pushing your fix in there. Unfortunately, I know little of the arp mode and I've never done a setup in arp mode.

I'm kind of hoping you can give me the go / no-go for this patch as it is right now. What I don't understand is why using Net::PcapUtils instead of Net::Pcap would work-around the problem since Net::PcapUtils is identified as a wrapper around Net::Pcap?

Also why are you using PcapUtils' next insead of loop like it was done before? Maybe that's the part that fixed the issue and if it is, what's the consequence? Could it be that you don't get the error but you don't get a packet either..?

Anyway, the point is, if you tested it and you are sure that it works, then I'll merge it so let me know.

Thanks,
(0001532)
obilodeau (reporter)
2010-05-04 15:17

Waiting for feedback on issue. Re-targeting for 1.9.1 for now.
(0001533)
obilodeau (reporter)
2010-05-04 15:18

Reminder sent to: treker

Hi Treker,

Can you check note 0001515 I left in this bug. I am asking more information on your patch.

Thanks!
(0001661)
obilodeau (reporter)
2010-09-15 11:15

Starting to think that I'm experiencing this bug in another location in the code. See 0001065.
(0002795)
obilodeau (reporter)
2012-06-15 10:03

Fixed a long time ago by getting rid of the ARP mode ;)

- Issue History
Date Modified Username Field Change
2009-06-15 08:03 user4 New Issue
2009-06-15 08:03 user4 Status new => assigned
2009-06-15 08:03 user4 Assigned To => user4
2009-06-15 11:54 user4 Note Added: 0001279
2009-06-19 23:50 treker File Added: pf-1.8.3-multiple-interface-with-mode-arp-workaround.patch
2009-06-19 23:51 treker Note Added: 0001286
2009-07-16 17:25 obilodeau Category 1.8.4 => 1.8.5
2009-10-15 15:44 rbalzard Reporter user4 => aarchi10
2009-10-15 15:44 rbalzard Assigned To user4 =>
2009-10-15 15:44 rbalzard Category 1.8.5 => future
2010-03-01 13:22 obilodeau Reporter aarchi10 => obilodeau
2010-03-01 13:22 obilodeau Assigned To => obilodeau
2010-03-01 13:22 obilodeau Target Version => 1.8.8
2010-04-19 16:25 obilodeau Note Added: 0001515
2010-04-29 13:39 obilodeau Target Version 1.8.8 => 1.9.0
2010-05-04 15:17 obilodeau Note Added: 0001532
2010-05-04 15:17 obilodeau Status assigned => feedback
2010-05-04 15:17 obilodeau Target Version 1.9.0 => 1.9.1
2010-05-04 15:18 obilodeau Note Added: 0001533
2010-09-15 11:14 obilodeau Relationship added related to 0001065
2010-09-15 11:15 obilodeau Note Added: 0001661
2010-09-15 11:15 obilodeau Target Version 1.9.1 => 1.9.2
2010-09-22 16:02 obilodeau Target Version 1.9.2 => 1.9.3
2012-02-29 10:58 obilodeau Category future => core
2012-06-15 10:03 obilodeau Note Added: 0002795
2012-06-15 10:03 obilodeau Status feedback => closed
2012-06-15 10:03 obilodeau Resolution open => fixed
2012-06-15 10:03 obilodeau Fixed in Version => 3.0.0


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker