Moved up from Nanobsd 2.3.1 to full 2.3.2, Can't get squid re installed.



  • So as stated I have moved up to the full version at 2.3.2 I installed from a memstick installer. I got into the webconfigurator and immediately did a restore to my most recent stable backup. Everything went fine except for squid. I have removed it from my conf.xml, I’ve looked all over to see if I could find a trace of it that might be causing the issue below. But alas, I can’t…Help me out what am I doing wrong?

    >>> Installing pfSense-pkg-squid... 
    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 4 package(s) will be affected (of 0 checked):
    
    New packages to be INSTALLED:
    	pfSense-pkg-squid: 0.4.21 [pfSense]
    	squid: 3.5.19_1 [pfSense]
    	squidclamav: 6.14 [pfSense]
    	c-icap-modules: 0.4.3 [pfSense]
    
    Number of packages to be installed: 4
    
    The process will require 10 MiB more space.
    [1/4] Installing squid-3.5.19_1...
    ===> Creating groups.
    Using existing group 'squid'.
    ===> Creating users
    Using existing user 'squid'.
    install: not found
    pkg: PRE-INSTALL script failed
    Failed
    
    


  • Bumping as I’ve been stumped I utilized a php script to clear out anything in my config.xml I’ve gone through almost every directory and searched about single forum post fix and tried it…Help.



  • I have the same problem. Both Squid and Squid Guard throw the same error. Afterward the web interface hangs up and cannot be restarted from the command line. The whole system must be rebooted. This is from a clean install freshly downloaded with only IPs configured.

    I first saw this problem when I attempted to upgrade from 2.3.1 to 2.3.2 yesterday morning.

    I also have a pfSense appliance. It does not have this problem. It’s upgrade was flawless. It appears to be only with the community version. When I did the update from 2.3.1 to 2.3.2 on the community version the whole package manager failed and could not be accessed without a fresh install as mentioned above. However, the above problem, with Squid and Squid Guard remains, even with the fresh, unconfigured install.

    I did not come from Nanbsd, but from the full 2.3.1 CE.

    I-7 16gigs Ram 128gig SSD (tried with a mechanical drive too - no joy) / Yeah way way overkill. It’s really zippy though!



  • That’s the issue here.
    https://redmine.pfsense.org/issues/6643

    To work around it, run:

    tar xv -C / -f /usr/local/share/pfSense/base.txz ./usr/bin/install
    


  • Yes - thank-you. I was just about to begin directory diving. I would have moved the ‘install’ from my pfSense appliance. This saved me a lot of work. Lots of good info here. I am very glad to know more about the tarball.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy