Extremely slow update 2.3.3 -> 2.3.4



  • Yesterday I decided to update to the current version. From the web gui everything looked fine until my APU2 was supposed to reboot. Even after waiting 10 minutes the web gui was not able to re-connect. I was also not able to ssh to the box. So I decided to re-power the box and it was running again. Internet access was ok and web gui was usable again. The only problem was sshd, which could not be started.

    Today I started to investigate a bit more and found that the box is still on 2.3.3. The dashboard claimed that I'm on a newer release than the current version - actually the box was still at 2.3.3. system/update showed "Current Base System 2.3.3  and "Latest Base System …"??? But I was able to update again, which I started after connecting the serial console.

    The web gui again showed no problem but was again not able to re-connect to the box within ten minutes. Checking the serial console showed that the update was still on its way. In total it took about 90 minutes to complete! After that everything was running fine and I'm now on 2.3.4.

    I did several updates on this box over the last time and they never took as long as this one. Normally I would expect something like less than ten minutes to complete the process. Do I have to expect update durations like this on all future updates?





  • Mine was extremely slow refreshing and downloading the packages too and its on an SSD, so not a USB Flash problem.

    After upgrading I'm also still getting "Unable to check for updates"/"Unable to retrieve package information" from the WebUI and updating the package manager from the shell is painfully slow.

    I see no obvious indication the SSD is failing, although "dd bs=1M count=256 if=/dev/zero of=test" only gives me 12MiB/s which seems usually low.  When I first installed pfSense I'm sure it got more like 200MiB/s.

    Otherwise though everything works fine and CPU usage remains low, so its really weird that its only package management showing a problem.



  • I'm using a SD card but I don't know, how this is connected to the system. Up to now this was not an issue. This really was the first update, which took this enormous amount of time.



  • My system was also very slow to update and the update failed. I've been using fpsense for a couple of years and never had this occur before.



  • @Alex:

    Mine was extremely slow refreshing and downloading the packages too and its on an SSD, so not a USB Flash problem.

    After upgrading I'm also still getting "Unable to check for updates"/"Unable to retrieve package information" from the WebUI and updating the package manager from the shell is still painfully slow.

    I have the same issues. I've just updated to 2.3.4 and it's constantly seems to refresh packages every 11 seconds….
    /rc.start_packages: Restarting/Starting all packages.



  • @YoMarK:

    @Alex:

    Mine was extremely slow refreshing and downloading the packages too and its on an SSD, so not a USB Flash problem.

    After upgrading I'm also still getting "Unable to check for updates"/"Unable to retrieve package information" from the WebUI and updating the package manager from the shell is still painfully slow.

    I have the same issues. I've just updated to 2.3.4 and it's constantly seems to refresh packages every 11 seconds….
    /rc.start_packages: Restarting/Starting all packages.

    Won't that just be the dashboard constantly re-trying to see if there is a new update?  Does it happen with the WebUI not open?

    That said I haven't seen that myself, I just see "pkg update" spawning.

    I have noticed something odd, that I tried to go to the Update settings and the WebUI hung while the console showed:

    root   44337   0.0  0.2  45336  8128  -  I     8:21PM     0:00.01 pkg update
    root   44440   0.0  0.2  45336  8884  -  I     8:21PM     0:00.01 pkg update
    root   47848   0.0  0.2  45336  8112  -  I     8:21PM     0:00.02 /usr/sbin/pkg search -R --raw-format json-compact pfSense-pkg-*
    root   47937   0.0  0.2  45336  8872  -  I     8:21PM     0:00.01 /usr/sbin/pkg search -R --raw-format json-compact pfSense-pkg-*
    
    

    Is it normal for those to be called TWICE?



  • As a follow up I tried "pkg-static upgrade -f" got:

    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 for upgrades (147 candidates):  44%
    
    pfSense-kernel-pfSense-2.3.4 is locked and may not be modified
    Checking for upgrades (147 candidates): 100%
    Processing candidates (147 candidates): 100%
    The following 146 package(s) will be affected (of 0 checked):
    
    Installed packages to be REINSTALLED:
            pkg-1.10.1_1 [pfSense]
            xinetd-2.3.15_2 [pfSense]
            wrapalixresetbutton-0.0.7 [pfSense]
            wol-0.7.1_3 [pfSense]
            whois-5.1.5_1 [pfSense]
            vstr-1.0.15_1 [pfSense]
            voucher-0.1_2 [pfSense]
            unbound-1.6.1 [pfSense]
            uclcmd-0.1_1 [pfSense]
            strongswan-5.5.1_1 [pfSense]
            sshlockout_pf-0.0.2 [pfSense]
            ssh_tunnel_shell-0.1 [pfSense]
            sqlite3-3.17.0 [pfSense]
            smartmontools-6.5_2 [pfSense]
            scponly-4.8.20110526_2 [pfSense]
            rrdtool-1.6.0_1 [pfSense]
            relayd-5.5.20140810_2 [pfSense]
            rate-0.9_1 [pfSense]
            radvd-1.9.1 [pfSense]
            qstats-0.1_1 [pfSense]
            python27-2.7.13_3 [pfSense]
            php56-zlib-5.6.30 [pfSense]
            php56-xmlwriter-5.6.30 [pfSense]
            php56-xmlreader-5.6.30 [pfSense]
            php56-xml-5.6.30 [pfSense]
            php56-tokenizer-5.6.30 [pfSense]
            php56-sysvshm-5.6.30 [pfSense]
            php56-sysvsem-5.6.30 [pfSense]
            php56-sysvmsg-5.6.30 [pfSense]
            php56-sqlite3-5.6.30 [pfSense]
            php56-sockets-5.6.30 [pfSense]
            php56-simplexml-5.6.30 [pfSense]
            php56-shmop-5.6.30 [pfSense]
            php56-session-5.6.30 [pfSense]
            php56-readline-5.6.30 [pfSense]
            php56-posix-5.6.30 [pfSense]
            php56-pfSense-module-0.13 [pfSense]
            php56-pdo_sqlite-5.6.30 [pfSense]
            php56-pdo-5.6.30 [pfSense]
            php56-pcntl-5.6.30 [pfSense]
            php56-openssl-5.6.30 [pfSense]
            php56-opcache-5.6.30 [pfSense]
            php56-mcrypt-5.6.30 [pfSense]
            php56-mbstring-5.6.30 [pfSense]
            php56-ldap-5.6.30 [pfSense]
            php56-json-5.6.30 [pfSense]
            php56-hash-5.6.30 [pfSense]
            php56-gettext-5.6.30 [pfSense]
            php56-filter-5.6.30 [pfSense]
            php56-dom-5.6.30 [pfSense]
            php56-curl-5.6.30 [pfSense]
            php56-ctype-5.6.30 [pfSense]
            php56-bz2-5.6.30 [pfSense]
            php56-bcmath-5.6.30 [pfSense]
            php56-5.6.30 [pfSense]
            php-xdebug-2.5.0 [pfSense]
            php-suhosin-0.9.38_3 [pfSense]
            pftop-0.7_8 [pfSense]
            pfSense-upgrade-0.22_1 [pfSense]
            pfSense-repo-2.3.4 [pfSense]
            pfSense-rc-2.3.4 [pfSense-core]
            pfSense-pkg-pfBlockerNG-2.1.1_8 [pfSense]
            pfSense-pkg-darkstat-3.1.3_4 [pfSense]
            pfSense-pkg-System_Patches-1.1.6_1 [pfSense]
            pfSense-pkg-RRD_Summary-1.3.2_2 [pfSense]
            pfSense-default-config-2.3.4 [pfSense-core]
            pfSense-base-2.3.4 [pfSense-core]
            pfSense-Status_Monitoring-1.6.1_3 [pfSense]
            pfSense-2.3.4 [pfSense]
            perl5-5.24.1 [pfSense]
            pecl-zmq-1.1.3_2 [pfSense]
            pecl-ssh2-0.13 [pfSense]
            pecl-rrd-1.1.3_4 [pfSense]
            pecl-radius-1.4.0.b1 [pfSense]
            pecl-intl-3.0.0_7 [pfSense]
            pcre-8.40 [pfSense]
            openvpn23-2.3.14 [pfSense]
            openldap-client-2.4.44 [pfSense]
            oniguruma5-5.9.6_1 [pfSense]
            ntp-4.2.8p10_2 [pfSense]
            norm-1.5r6 [pfSense]
            nginx-1.10.3_1,2 [pfSense]
            nettle-3.3 [pfSense]
            mpd5-5.8 [pfSense]
            mpd4-4.4.1_1 [pfSense]
            miniupnpd-1.9.20160113,1 [pfSense]
            minicron-0.0.2 [pfSense]
            lzo2-2.10_1 [pfSense]
            lua52-5.2.4 [pfSense]
            links-2.13,1 [pfSense]
            lighttpd-1.4.45_1 [pfSense]
            libzmq4-4.1.5 [pfSense]
            libxml2-2.9.4 [pfSense]
            libucl-0.8.0 [pfSense]
            libssh2-1.8.0,3 [pfSense]
            libsodium-1.0.12 [pfSense]
            libpdel-0.5.3_6 [pfSense]
            libnghttp2-1.21.0 [pfSense]
            libmcrypt-2.5.8_3 [pfSense]
            libltdl-2.4.6 [pfSense]
            libidn-1.33_1 [pfSense]
            libiconv-1.14_10 [pfSense]
            libffi-3.2.1 [pfSense]
            libevent-2.1.8 [pfSense]
            libedit-3.1.20150325_2,1 [pfSense]
            libdaemon-0.14_1 [pfSense]
            ldns-1.7.0 [pfSense]
            json-c-0.12.1 [pfSense]
            isc-dhcp43-server-4.3.5 [pfSense]
            isc-dhcp43-relay-4.3.5 [pfSense]
            isc-dhcp43-client-4.3.5 [pfSense]
            ipmitool-1.8.18 [pfSense]
            indexinfo-0.2.6 [pfSense]
            igmpproxy-0.1_3,1 [pfSense]
            idnkit-1.0_6 [pfSense]
            icu-58.2,1 [pfSense]
            grepcidr-2.0 [pfSense]
            gmp-6.1.2 [pfSense]
            glib-2.46.2_5 [pfSense]
            gettext-runtime-0.19.8.1_1 [pfSense]
            filterlog-0.1_4 [pfSense]
            filterdns-1.0_9 [pfSense]
            expiretable-0.6_1 [pfSense]
            expat-2.2.0_1 [pfSense]
            dpinger-2.0 [pfSense]
            dnsmasq-2.76,1 [pfSense]
            dmidecode-3.0 [pfSense]
            dhcpleases6-0.1_2 [pfSense]
            dhcpleases-0.3_1 [pfSense]
            dhcp6-20080615.2 [pfSense]
            darkstat-3.0.719 [pfSense]
            curl-7.54.0 [pfSense]
            cpustats-0.1_1 [pfSense]
            cpdup-1.18 [pfSense]
            clog-1.0.1 [pfSense]
            choparp-20150613 [pfSense]
            check_reload_status-0.0.7 [pfSense]
            ca_root_nss-3.30.2 [pfSense]
            bwi-firmware-kmod-3.130.20 [pfSense]
            bsnmp-ucd-0.4.2 [pfSense]
            bsnmp-regex-0.6_1 [pfSense]
            bind-tools-9.11.1 [pfSense]
            beep-1.0_1 [pfSense]
            ataidle-2.7.2 [pfSense]
            aggregate-1.6_1 [pfSense]
            GeoIP-1.6.10 [pfSense]
    
    Number of packages to be reinstalled: 146
    
    10 MiB to be downloaded.
    

    Does that mean 44% of the packages were not correctly upgraded to 2.3.4 or just that its going to attempt to reinstall everything?

    I let it go ahead but its taking FOREVER (over an hour now to download 40/146)!  Frustrating when before it would have taken a matter of seconds.

    Its just bizarre, system and interrupt are low, I just can't see what is slowing it down as running curl for a test download while all this is going on I get:

    [2.3.4-RELEASE][root@Router.lan]/root: curl http://ipv4.download.thinkbroadband.com/512MB.zip > test
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100  512M  100  512M    0     0  8237k      0  0:01:03  0:01:03 --:--:-- 8893k
    
    


  • After doing that and a reboot the dashboard finally is telling me I'm on the latest version.

    Installed packages in the WebUI is still broken though.  Its still calling "/usr/sbin/pkg search -R –raw-format json-compact pfSense-pkg-*" and from the command line that gives:

    [2.3.4-RELEASE][root@Router.lan]/root: /usr/sbin/pkg search -R --raw-format json-compact pfSense-pkg-*
    /usr/sbin/pkg: No match.
    

    Available packages and installing packages DOES seem to be working from the WebUI now though, just very very very slowly.

    Example, it took about 40 minutes to install "pfSense-pkg-suricata". :o

    It spends AGES on "Updating * repository catalogue…" then downloads each package at a few KB/s with a huge delay between each file.  The actual package installation went at normal speed.



  • I figured out what was going on here.  It seems to be some change in IPv6 behaviour where because I still have an IPv6 tunnel enabled but am not actually using it, pkg is still trying to use IPv6 for some reason so stalls.

    Ticking "prefer IPv4 over IPv6" in Advanced settings fixed the problem.



  • Yes, that's basically the same as using a dual WAN with the other WAN set to disabled but forcing the system to still try to use the disabled WAN connection, it will be slow because everything will first have to wait for the timeout to occur.



  • I still believe it was a glitch as it had been working fine on this configuration previously.

    Good news is that on pfSense 2.4.0 RC I finally have been able to get my ISPs native IPv6 to work anyway, so it should no longer be an issue.



  • As far as I understand it the bind() system call with AF_INET6 set will succeed on a system that has a broken IPv6 interface enabled but the following connect() system call will timeout. If it was working for you previously suggests that the IPv6 interface was properly disabled (set to IFDISABLED state) but now it was enabled for some reason.



  • And just to keep an old thread endlessly alive..

    Upgraded 2.3.2 to 2.3.4_1 and it took just under 4hrs. I found this thread about 30 mins into the upgrade. I used the webGUI, the platform is nanobsd, the hardware is ancient AMD BE-2350.

    It did give me time to cobble together a newer system based on a MSI AM1M mobo, 4GB RAM, AMD 5350 cpu. I was able to restore the nanobsd config to the new 'full' platform. I'm always using HP NC365T quad port NIC cards - I've had great luck with them. You just have to remember the top port is igb3 and the bottom is igb0.

    This was the office router. I have a home one I plan to upgrade via console. We've rolled out 10-15 of these to our clients. Yes, there's some kind of bug in this process, but, a big THANKS! to the pfSense team and their continued commitment.


Log in to reply