PacketFence - BTS - PacketFence
View Issue Details
0001264PacketFencecorepublic2011-09-08 14:212011-10-24 20:24
obilodeau 
obilodeau 
normalminorsometimes
closedfixed 
LinuxRHEL / CentOS5
 
3.0.03.0.0 
0001264: iptables error on first start
# service packetfence start
Starting PacketFence...Checking configuration sanity...
iptables-save v1.3.5: Can't initialize: iptables who? (do you need to insmod?)

iptables-save v1.3.5: Can't initialize: iptables who? (do you need to insmod?)

iptables-save v1.3.5: Can't initialize: iptables who? (do you need to insmod?)

Probably caused by the fact that iptables never ran on a new system.
No tags attached.
Issue History
2011-09-08 14:21obilodeauNew Issue
2011-09-13 09:29obilodeauStatusnew => assigned
2011-09-13 09:29obilodeauAssigned To => obilodeau
2011-09-13 13:54obilodeauNote Added: 0002200
2011-09-13 14:08obilodeauNote Added: 0002201
2011-09-13 14:08obilodeauStatusassigned => resolved
2011-09-13 14:08obilodeauFixed in Version => trunk
2011-09-13 14:08obilodeauResolutionopen => fixed
2011-09-21 22:07obilodeauFixed in Versiontrunk => 3.0.0
2011-09-21 22:15obilodeauNote Added: 0002235
2011-09-21 22:16obilodeauStatusresolved => closed
2011-10-24 20:24obilodeauTarget Version+1 => 3.0.0

Notes
(0002200)
obilodeau   
2011-09-13 13:54   
Fresh CentOS 5.6 vm install, disabled se-linux and getting the iptables error on first start.
(0002201)
obilodeau   
2011-09-13 14:08   
If we leave the system's firewall enabled (instead of shutting it down like we tell to do in the current documentation) there's no error on startup.

We will update the doc to say to leave the minimal firewall running when installing packetfence.
(0002235)
obilodeau   
2011-09-21 22:15   
fix released in 3.0