Project

General

Profile

Actions

Bug #9895

open

snort reinstallation failed

Added by Viktor Gurov over 4 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Snort
Target version:
-
Start date:
11/14/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.5.0
Affected Plus Version:
Affected Architecture:

Description

got such errors during snort pkg update:

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-pkg-snort from 4.0_8 to 4.0_9...
[1/1] Extracting pfSense-pkg-snort-4.0_9: .......... done
Removing snort components...
Menu items... done.
Services... done.
Loading package instructions...
pfSense-pkg-snort-4.0_8: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.0_8/APACHE20
pfSense-pkg-snort-4.0_8: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.0_8/LICENSE
pfSense-pkg-snort-4.0_8: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.0_8/catalog.mk
pkg-static: Fail to rename /var/db/snort/sidmods/.disablesid-sample.conf.Nty7DJxy3BbR -> /var/db/snort/sidmods/disablesid-sample.conf:No such file or directory
Failed

looks like this bug https://redmine.pfsense.org/issues/7310 which is marked as resolved

pfSense 2.5.0.a.20191113.1923

Actions #1

Updated by Michael Spears over 3 years ago

Unable to reproduce this on 2.5.0.a.20200910.1250.

Actions #2

Updated by Viktor Gurov over 3 years ago

same on 2.5.0.a.20201022.1850

[1/1] Upgrading pfSense-pkg-snort from 4.1.2_1 to 4.1.2_2...
[1/1] Extracting pfSense-pkg-snort-4.1.2_2: .......... done
Removing snort components...
Menu items... done.
Services... done.
Loading package instructions...
pfSense-pkg-snort-4.1.2_1: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_1/APACHE20
pfSense-pkg-snort-4.1.2_1: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_1/LICENSE
pfSense-pkg-snort-4.1.2_1: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_1/catalog.mk
pkg-static: Fail to rename /var/db/snort/sidmods/.pkgtemp.disablesid-sample.conf.NDqe4k68Nroh -> /var/db/snort/sidmods/disablesid-sample.conf:No such file or directory
Failed

snort config is empty

workaround:
uninstall/install

Actions #3

Updated by Viktor Gurov over 2 years ago

same issue on 2.6.0.a.20210622.0100:

Number of packages to be upgraded: 1
[1/1] Upgrading pfSense-pkg-snort from 4.1.2_4 to 4.1.3_5...
[1/1] Extracting pfSense-pkg-snort-4.1.3_5: .......... done
Removing snort components...
Menu items... done.
Services... done.
Loading package instructions...
pfSense-pkg-snort-4.1.2_4: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_4/APACHE20
pfSense-pkg-snort-4.1.2_4: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_4/LICENSE
pfSense-pkg-snort-4.1.2_4: missing file /usr/local/share/licenses/pfSense-pkg-snort-4.1.2_4/catalog.mk
pkg-static: Fail to rename /var/db/snort/sidmods/.pkgtemp.disablesid-sample.conf.Bj8pb7KZED5z -> /var/db/snort/sidmods/disablesid-sample.conf:No such file or directory
Failed

Another solution: https://forum.netgate.com/topic/128894/solved-snort-fails-after-os-update/4

Actions #4

Updated by Bill Meeks over 2 years ago

Viktor Gurov wrote:

same issue on 2.6.0.a.20210622.0100:
[...]

Another solution: https://forum.netgate.com/topic/128894/solved-snort-fails-after-os-update/4

I have personally never seen this bug in my virtual machine testing, and I reinstall Snort (and also delete first, then reinstall) a number of times during testing of a given release. I think this same error message has been reported in the past with the Suricata package.

I am not sure what is causing the issue. It's like the package archive itself is somehow corrupted. Note the messages about missing files. I assume that pkg itself is the source of those logged messages. The files logged in the messages are not touched by the Snort GUI package code at all. They are solely manipulated (deleted or installed) by pkg itself as part of removing and/or installing the package. And it is complaining about the older version of those files. It's like the "install of the new version" is trying to share time and space with the "removal of the older version", and they are colliding.

Actions

Also available in: Atom PDF