Bug #9202
closedBug #9195 not fixed with Suricata re-install, un-install and fresh install (not keeping settings), or all package re-install
0%
Description
I have tried System -> Package Manager -> Installed Packages -> Suricata -> clicked Reinstall. Same issue (Bug #9195).
I have uninstalled Suricata without preserving settings and re-installed from scratch, although I re-used my SID management control files and Suppress lists. I still see the errors.
I tried Diagnostics -> Backup & Restore -> Backup & Restore -> Package Functions -> Reinstall Packages. I still see the errors.
My reference.config is:
cat /usr/local/etc/suricata/reference.config
config reference: arachNIDS http://www.whitehats.com/info/IDS
config reference: bugtraq http://www.securityfocus.com/bid/
config reference: cve http://cve.mitre.org/cgi-bin/cvename.cgi?name=
config reference: McAfee http://vil.nai.com/vil/content/v_
config reference: msb http://technet.microsoft.com/en-us/security/bulletin/
config reference: nessus http://cgi.nessus.org/plugins/dump.php3?id=
config reference: osvdb http://osvdb.org/show/osvdb/
config reference: url http://
However, with regard to the line "config reference: McAfee http://vil.nai.com/vil/content/v_", I am unable to resolve "vil.nai.com". Problem?
There is a "suricata.core" file in "/root". However, so far, no re-install has "fixed" the issue reported in Bug #9195.
I will try resetting to Factory Default and restore a backup of the SID management control files and Suppress lists. I assume I already effectively done this (i.e., with an uninstall and fresh install), but I will try after a reset to Factory Defaults. If still unsuccessful, I will try a fresh install of Suricata.
Note: I have opened a new bug report as I continue to have the issue after the suggestion that re-install would fix the issue. It has not.
Updated by Jim Pingle almost 6 years ago
- Status changed from New to Duplicate
The other bug report is still open. Add notes there, don't open a new issue for the same problem.
Updated by P L almost 6 years ago
Clearly, this is not the same bug report.
That was a bug with errors occuring with Suricata. This is a bug that the errors are not fixed with all available (tested) re-install options.
Those are different issues.