0001644: Cannot start configurator after installation - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001644

PacketFence

configuration

public

2013-05-27 08:08

2015-02-18 10:59

Reporter

roelof

Assigned To

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

open

Platform

OS Version

Product Version

4.0.0

Target Version

Fixed in Version

Summary

0001644: Cannot start configurator after installation

Description

# /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.

Additional Information

Centos 6.4 x64, fully up to date
PacketFence version 4.01,
web browser IE9, IE10 & Chrome

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0003308) colvinb (reporter) 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 (administrator) 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.

Issue History
Date Modified	Username	Field	Change
2013-05-27 08:08	roelof	New Issue
2013-05-30 03:01	colvinb	Note Added: 0003308
2015-02-18 10:59	lmunro	Note Added: 0003940
2015-02-18 10:59	lmunro	Status	new => closed