Suricata on pfSense plus 23.01 fails to install

trunet

This is a new install (installed 2 days ago). Installed pfSense 2.6 from ISO, than upgraded to 22 and than 23.01.

It shows:
pfSense-pkg-suricata installation failed!

>>> Installing pfSense-pkg-suricata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 9 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	hyperscan: 5.4.0 [pfSense]
	libnet: 1.2,1 [pfSense]
	libpcap: 1.10.1_2 [pfSense]
	libyaml: 0.2.5 [pfSense]
	nspr: 4.35 [pfSense]
	nss: 3.84 [pfSense]
	pfSense-pkg-suricata: 6.0.10_1 [pfSense]
	py39-yaml: 5.4.1 [pfSense]
	suricata: 6.0.10 [pfSense]

Number of packages to be installed: 9

The process will require 39 MiB more space.
8 MiB to be downloaded.
[1/9] Fetching libyaml-0.2.5.pkg: .......... done
pkg-static: cached package libyaml-0.2.5: missing or size mismatch, fetching from remote
[2/9] Fetching libyaml-0.2.5.pkg: .......... done
pkg-static: cached package libyaml-0.2.5: missing or size mismatch, cannot continue
Consider running 'pkg update -f'
Failed

bmeeks

Something appears to be wrong with your pkg utility setup.

trunet

@bmeeks Would you know how to fix it?

bmeeks

@trunet said in Suricata on pfSense plus 23.01 fails to install:

@bmeeks Would you know how to fix it?

Did your Internet connection have any issues during the attempted install? The error message is basically saying it either failed to download one of the required dependency files, or else the file it got was corrupted and the checksum/size did not match up with what was anticipated.

First, I would repeat the install attempt to see if it works the second time. If it fails again, then I'm not sure what could be wrong. One thing I do know is that package builds were just turned back on this morning for 23.01. They had been temporarily disabled following the 23.01 rollout last week. Perhaps you were unlucky enough to attempt a package install before everything got fully up and running on the Netgate side ???