Package install fails - Lzma library error corrupt input data



  • Hi there,

    When attempting to install Snort to a pfSense 2.3.2-RELEASE-p1 system, it fails with the following:

    Installing pfSense-pkg-snort…
    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.
    Checking integrity... done (0 conflicting)
    The following 9 package(s) will be affected (of 0 checked):

    New packages to be INSTALLED:
                    pfSense-pkg-snort: 3.2.9.2_16 [pfSense]
                    barnyard2: 1.13 [pfSense]
                    broccoli: 1.97,1 [pfSense]
                    GeoIP: 1.6.9 [pfSense]
                    mysql56-client: 5.6.30 [pfSense]
                    snort: 2.9.8.3 [pfSense]
                    luajit: 2.0.4_1 [pfSense]
                    daq: 2.0.6 [pfSense]
                    libdnet: 1.12_1 [pfSense]

    Number of packages to be installed: 9

    The process will require 58 MiB more space.
    [1/9] Installing GeoIP-1.6.9…
    [1/9] Extracting GeoIP-1.6.9: …....... done
    [2/9] Installing broccoli-1.97,1…
    [2/9] Extracting broccoli-1.97,1: …....... done
    [3/9] Installing mysql56-client-5.6.30…
    [3/9] Extracting mysql56-client-5.6.30:
    pkg: Fail to extract /usr/local/bin/mysql from package: Lzma library error: Corrupted input data
    [3/9] Extracting mysql56-client-5.6.30… done
    Failed

    I am using a proxy to reach outbound connectivity, however this is not hindering connections on 80 and 443, it passes all. Can anyone suggest a work around to get Snort installed please? Thanks.


  • Rebel Alliance Developer Netgate

    The packages on the server are fine, it must be getting corrupted locally or in transit. So either the upstream proxy or something on your own box



  • @jimp:

    The packages on the server are fine, it must be getting corrupted locally or in transit. So either the upstream proxy or something on your own box

    Thankyou for checking. Could it be possible that packages are different geographically? Perhaps failing checksum due to coming from a different pkg mirror geographically?

    The proxy is in Germany, whilst the pfSense FW is in east coast USA

    Additionally, seeing as I have you here, the reason for me using a proxy to update and install packages is due to pfSense (or pkg??) blocking our entire newly acquired /22. We've deployed a few pfSense boxes within this range and none of them can use pkg successfully. Yet I install the same release of pfSense with another IP from one of our other ranges (many to chose from) and they work fine. It's JUST the xx.xx.xx.xx (we actually split it up into 4x /24's but the parent block is a /22.

    Are you able to confirm or deny that? It's literally never worked with pkg on pfsense. It's like whoever maintains the centralised access list for pkg servers (or maybe just the pfsense repos??) blcoks the entire range.

    Thanks!


  • Rebel Alliance Developer Netgate

    If it is a newly allocated address range it might have still been in the bogons list, which gets updated once per month or so. Have you tried it in the last few days?


Log in to reply