0001752: Fresh Snort install fails to start after rules update script is run - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001752

PacketFence

scanning

public

2013-12-04 14:18

2013-12-04 14:25

Reporter

thedeco

Assigned To

francis

Priority

low

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

Linux

RHEL / CentOS

OS Version

Product Version

4.0.6-2

Target Version

Fixed in Version

4.1.0

Summary

0001752: Fresh Snort install fails to start after rules update script is run

Description

After a fresh install of Snort and running the update_rules.pl script, Snort cannot start up by default.

Checking /var/log/messages show the following error:

FATAL ERROR: Unable to open rules file "/usr/local/pf/var/conf//usr/local/pf/conf/snort/emerging-virus.rules": No such file or directory.

It appears the update_rules script failed to install this one rule set in conf/snort directory even though it is present in the violations.conf file by default.

Steps To Reproduce

Fresh install of PacketFence 4.0.6-2

service packetfence stop
yum install snort
run the rules update located /usr/local/pf/addons/snort/update_rules.pl
service packetfence start
service snortd status

Additional Information

I was able to start Snort after removing the emerging-virus.rules from the list of Snort rules in violations.conf file

Tags

No tags attached.

fixed in git revision

7d72045e2a72f82e1b1e6811e7b6aafdfeba4dc1

fixed in mtn revision

Attached Files

Relationships

Notes
(0003476) francis (administrator) 2013-12-04 14:25	Fixed two months ago. https://github.com/inverse-inc/packetfence/commit/7d72045e2a72f82e1b1e6811e7b6aafdfeba4dc1 [^] https://github.com/inverse-inc/packetfence/commit/02160bac4ee9dddc928b85279bb70707e2daef9c [^]

Issue History
Date Modified	Username	Field	Change
2013-12-04 14:18	thedeco	New Issue
2013-12-04 14:25	francis	fixed in git revision	=> 7d72045e2a72f82e1b1e6811e7b6aafdfeba4dc1
2013-12-04 14:25	francis	Note Added: 0003476
2013-12-04 14:25	francis	Status	new => resolved
2013-12-04 14:25	francis	Fixed in Version	=> 4.1.0
2013-12-04 14:25	francis	Resolution	open => fixed
2013-12-04 14:25	francis	Assigned To	=> francis