PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000578PacketFencecorepublic2009-02-10 11:342012-02-29 10:57
Reportermaikel 
Assigned Touser4 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versiondevel 
Target VersionFixed in Version 
Summary0000578: startup error when networks.conf is empty
Description /etc/init.d/packetfence start
Starting PacketFence...Empty file treated as error at /usr/lib/perl5/site_perl/5.8.8/Log/Log4perl/Logger.pm line 896
Additional InformationCompilation failed in require at /usr/local/pf/bin/pfcmd line 32.
BEGIN failed--compilation aborted at /usr/local/pf/bin/pfcmd line 32.

TagsNo tags attached.
fixed in git revision
fixed in mtn revision
Attached Files

- Relationships

-  Notes
(0001083)
maikel (reporter)
2009-02-10 11:51

It is most likely due to networks.conf when digging into the code.
The file is left empty from configurator.pl
(0001084)
user4
2009-02-10 11:56

this could be the reason for this issue ... in fact, the networks.conf file should be able to contain no data since it's currently used for remote, routed networks (i.e. subnets which can't be defined through the interfaces)
(0001085)
user4
2009-02-10 12:04

fixed in mtn revision aad047ec0d21bb7dc613243dc290de1c5960f0d1

- Issue History
Date Modified Username Field Change
2009-02-10 11:34 maikel New Issue
2009-02-10 11:50 user4 Status new => assigned
2009-02-10 11:50 user4 Assigned To => user4
2009-02-10 11:51 maikel Note Added: 0001083
2009-02-10 11:56 user4 Note Added: 0001084
2009-02-10 12:03 user4 Category 1.8.0 => 1.8.1
2009-02-10 12:03 user4 Summary startup error => startup error when networks.conf is empty
2009-02-10 12:04 user4 Status assigned => closed
2009-02-10 12:04 user4 Note Added: 0001085
2009-02-10 12:04 user4 Resolution open => fixed
2010-04-15 17:54 obilodeau Category 1.8.1 => 1.8.x
2012-02-29 10:57 obilodeau Category 1.8.x => core


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker