RESOLVED - syslog-ng (3.6.2_3 on 2.2.1-RELEASE (i386)): Installation failed

  • Hello, fresh install:

    2.2.1-RELEASE (i386)
    built on Fri Mar 13 08:16:53 CDT 2015
    FreeBSD 10.1-RELEASE-p6

    Trying to add syslog-ng service:

    3.6.2_3 pkg.v.1.0.6
    platform: 2.2

    Installation of syslog-ng FAILED!
    Beginning package installation for syslog-ng .
    Downloading package configuration file... done.
    Saving updated package information... done.
    Downloading syslog-ng and its dependencies... 
    Checking for package installation... 
     Downloading ...  (extracting)
     Verifying Checksum...SKIP_ARCHLINES: 68
     Archive checksum: 4c8b424b35e188b17dab1e6e1469576acd745bf28838a9a1baa49de872174483
     Saved checksum: 4c8b424b35e188b17dab1e6e1469576acd745bf28838a9a1baa49de872174483
     Extracting to: /usr/pbi/syslog-ng-i386
     TOTALFILES: 11173
     tar: Failed to set default locale
     x ./
     x ./local/
     x ./etc/
     x ./rc.d/
     x ./pbimeta/
     x ./virtbase/
     x ./linux/
     x ./run/
     x ./pbiconf/
     x ./bin/
     x ./.pbi-hash-list
     tar: Lzma library error:  No progress is possible
     tar: Error exit delayed from previous errors.
     ERROR: Failed extracting /tmp/apkg_syslog-ng-3.6.2_3-i386.pbi
    of syslog-ng-3.6.2_3-i386 failed!
    Installation aborted.Removing package...
    Starting package deletion for syslog-ng-3.6.2_3-i386...done.
    Removing syslog-ng components...
    Tabs items... done.
    Menu items... done.
    Services... done.
    Loading package instructions...
    Include file could not be found for inclusion.
    Deinstall commands... 
    Not executing custom deinstall hook because an include is missing.
    Removing package instructions...done.
    Auxiliary files... done.
    Package XML... done.
    Configuration... done.
    Failed to install package.
    Installation halted.

  • It's strange, but today I successfully installed syslog-ng packet.

  • Sometimes thats just how it goes.  Trust me.  Something was different.

    Maybe a reboot?  Package updated?  Who knows?

Log in to reply