PacketFence - BTS - PacketFence
View Issue Details
0000578PacketFencecorepublic2009-02-10 11:342012-02-29 10:57
maikel 
user4 
normalmajoralways
closedfixed 
devel 
 
0000578: startup error when networks.conf is empty
 /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
Compilation failed in require at /usr/local/pf/bin/pfcmd line 32.
BEGIN failed--compilation aborted at /usr/local/pf/bin/pfcmd line 32.

No tags attached.
Issue History
2009-02-10 11:34maikelNew Issue
2009-02-10 11:50user4Statusnew => assigned
2009-02-10 11:50user4Assigned To => user4
2009-02-10 11:51maikelNote Added: 0001083
2009-02-10 11:56user4Note Added: 0001084
2009-02-10 12:03user4Category1.8.0 => 1.8.1
2009-02-10 12:03user4Summarystartup error => startup error when networks.conf is empty
2009-02-10 12:04user4Statusassigned => closed
2009-02-10 12:04user4Note Added: 0001085
2009-02-10 12:04user4Resolutionopen => fixed
2010-04-15 17:54obilodeauCategory1.8.1 => 1.8.x
2012-02-29 10:57obilodeauCategory1.8.x => core

Notes
(0001083)
maikel   
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