PacketFence - BTS - PacketFence
View Issue Details
0001644PacketFenceconfigurationpublic2013-05-27 08:082015-02-18 10:59
roelof 
 
normalmajoralways
closedopen 
4.0.0 
 
0001644: Cannot start configurator after installation
# /usr/local/pf/bin/pfcmd service httpd start
 Checking configuration sanity...
 FATAL - please define exactly one management interface
 FATAL - internal network(s) not defined!
 FATAL - Unable to connect to your database. Please verify your connection settings in conf/pf.conf and make sure that it is started.
 FATAL - networks.conf cannot be empty when services.dhcpd is enabled
 FATAL - networks.conf cannot be empty when services.named is enabled
 WARNING - We have been unable to load your configuration. Are you sure you ran configurator.pl?

 To start web configurator, the files above must be created whereas it's the job of configurator.
Centos 6.4 x64, fully up to date
 PacketFence version 4.01,
 web browser IE9, IE10 & Chrome
No tags attached.
Issue History
2013-05-27 08:08roelofNew Issue
2013-05-30 03:01colvinbNote Added: 0003308
2015-02-18 10:59lmunroNote Added: 0003940
2015-02-18 10:59lmunroStatusnew => closed

Notes
(0003308)
colvinb   
2013-05-30 03:01   
I have experienced the same issue.
Centos 6.4 x64, fully up to date
 PacketFence version 4.01
(0003940)
lmunro   
2015-02-18 10:59   
Obsolete bug tracker entries.
PF 4 introduced changes that either make these irrelevant or impossible to reproduce.

New issues are moving to github issues.