ALIX and pfSense no longer compatible!



  • I have a few ALIX Boards and can't upgrade because the upgrade is crashing on different stages. Generaly pfsense upgrade are a nightmare since 2.2.x, so many time upgrades are hanging and i have to drive hundreds of kilometer because the crap not come back!

    So i see this in the log even pfsense says upgrade done .. rebooting!

    Box 1:
    [4/53] Extracting python27-2.7.13_3: …....... done
    Child process pid=42049 terminated abnormally: Killed

    Box 2:
    [53/53] Fetching libevent-2.1.8.txz: …....... done
    Checking integrity...Child process pid=66054 terminated abnormally: Killed

    Locking package pfSense-kernel-pfSense_wrap... done.
    __RC=1 __REBOOT_AFTER=10

    Box 3:
    [4/147] Upgrading python27 from 2.7.13_1 to 2.7.13_3…
    [4/147] Extracting python27-2.7.13_3:  4%Child process pid=20274 terminated abnormally: Killed

    Some boxes say upgrade done and rebooting but they dont switch the slice! If i switch the slice i have the old 2.3.3 system and i can switch back it still the old on both slices!

    If i watch inside the terminal i can see a bsdtar using cpu while a broadcast say box rebooting!? Is it not finish with extract and system starts a reboot?

    Does not mapper if i use pfSense-upgrade -d or pkg-static upgrade -f

    It sucks!



  • Box 4 is not coming back! So i have to drive tomorrow again! :-(

    On all APU boxes the uprgade is working, only Alix and Nano is not working.



  • I can confirm this problem also.

    Also combination of Alix and Nano-BSD, also crashes at the upgrade of python27, same error message.

    I also can not access the box remotely any more. I have to drive and get the box …

    Besides that I have another major problem, because fetching package data with https does not work. Http does.



  • My ALIX runs out of memory when I try to upgrade any more.

    In the upgrade log I see something like:

    Child process pid=96756 terminated abnormally: Killed

    And then in the main system log there's this:

    Mar 11 12:56:43 router.myersnet.net kernel: pid 96756 (pkg), uid 0, was killed: out of swap space


  • Rebel Alliance Developer Netgate

    If you have any packages installed or extra services active, you'll need to uninstall them or disable/stop them before upgrading in most cases.

    It can work fine, I still have an ALIX here that I upgrade with every release, and it never has any problems. But it's not doing much more than sitting around.



  • I just have System_Patches and nut installed, which I assumed would be small. I was also watching the Dashboard even though I was upgrading from the console, which probably didn't help.

    I haven't touched the system since the upgrade failed. Is it safe to try again? I'd like to avoid having to remove the motherboard to get at the CF card if something goes wrong, of course.


  • Rebel Alliance Developer Netgate

    If it happened late enough to be a problem you wouldn't be up and running right now. It should be OK to try again.

    And definitely don't watch on the dashboard. Visit Status > Services and shut down anything that isn't critical (nut, ipsec/openvpn, etc) and then run the upgrade from the console.

    Though I upgrade mine from the GUI and it's OK.



  • Thanks.



  • Proceed with upgrade? (y/N) y

    Cleaning secondary partition… done.
    Duplicating current slice... done.
    Restoring slice label... done.
    Testing duplicated partition integrity... done.
    Mounting second partition to run upgrade... done.
    Removing resolv.conf symlink from upgrade partition... done.
    Copying resolv.conf to upgrade partition... done.
    Downloading upgrade packages...
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up to date.
    Updating pfSense repository catalogue...
    Fetching meta.txz: . done
    Fetching packagesite.txz: .......... done
    Processing entries: .......... done
    pfSense repository update completed. 436 packages processed.
    All repositories are up to date.
    Checking for upgrades (150 candidates): .......... done
    Processing candidates (150 candidates): ... done
    The following 57 package(s) will be affected (of 0 checked):

    New packages to be INSTALLED:
    libevent: 2.1.8 [pfSense]

    Installed packages to be UPGRADED:
    unbound: 1.6.0 -> 1.6.1 [pfSense]
    strongswan: 5.5.1 -> 5.5.1_1 [pfSense]
    squidclamav: 6.14 -> 6.16 [pfSense]
    squid: 3.5.23 -> 3.5.26 [pfSense]
    sqlite3: 3.15.1_1 -> 3.17.0 [pfSense]
    smartmontools: 6.5_1 -> 6.5_2 [pfSense]
    python27: 2.7.13_1 -> 2.7.13_3 [pfSense]
    pkgconf: 1.1.0 -> 1.3.0,1 [pfSense]
    php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense]
    pftop: 0.7_7 -> 0.7_8 [pfSense]
    pfSense-upgrade: 0.22_1 -> 0.23 [pfSense]
    pfSense-rc: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense-pkg-squid: 0.4.36_3 -> 0.4.37 [pfSense]
    pfSense-pkg-openvpn-client-export: 1.4.2_2 -> 1.4.9 [pfSense]
    pfSense-kernel-pfSense_wrap: 2.3.2_1 -> 2.3.4 [pfSense-core]
    pfSense-default-config-serial: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense-base-nanobsd: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense: 2.3.3_1 -> 2.3.4 [pfSense]
    perl5: 5.24.1.r4_1 -> 5.24.1 [pfSense]
    pcre: 8.39_1 -> 8.40 [pfSense]
    openvpn-client-export: 2.4.1_1 -> 2.4.3_1 [pfSense]
    nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense]
    lzo2: 2.09 -> 2.10_1 [pfSense]
    libssh2: 1.8.0,2 -> 1.8.0,3 [pfSense]
    libsodium: 1.0.11_1 -> 1.0.12 [pfSense]
    libnghttp2: 1.18.0 -> 1.21.0 [pfSense]
    lha: 1.14i_6 -> 1.14i_7 [pfSense]
    ldns: 1.6.17_5 -> 1.7.0 [pfSense]
    krb5: 1.14.4 -> 1.15.1_4 [pfSense]
    ipmitool: 1.8.17_1 -> 1.8.18 [pfSense]
    gmp: 5.1.3_3 -> 6.1.2 [pfSense]
    glib: 2.46.2_4 -> 2.46.2_5 [pfSense]
    dhcp6: 20080615.1 -> 20080615.2 [pfSense]
    curl: 7.53.1_1 -> 7.54.0 [pfSense]
    clamav: 0.99.2_2 -> 0.99.2_3 [pfSense]
    ca_root_nss: 3.28.1 -> 3.30.2 [pfSense]
    c-icap-modules: 0.4.3 -> 0.4.5 [pfSense]
    c-icap: 0.4.3,2 -> 0.4.4,2 [pfSense]
    bind-tools: 9.11.0P3 -> 9.11.1P1 [pfSense]

    Installed packages to be REINSTALLED:
    vstr-1.0.15_1 [pfSense]
    openldap-client-2.4.44 [pfSense]
    ntp-4.2.8p10_2 [pfSense] (direct dependency changed: libevent)
    nettle-3.3 [pfSense]
    libxml2-2.9.4 [pfSense]
    libltdl-2.4.6 [pfSense]
    libidn-1.33_1 [pfSense]
    libiconv-1.14_10 [pfSense]
    libffi-3.2.1 [pfSense]
    libedit-3.1.20150325_2,1 [pfSense]
    json-c-0.12.1 [pfSense]
    idnkit-1.0_6 [pfSense]
    gettext-runtime-0.19.8.1_1 [pfSense]
    expat-2.2.0_1 [pfSense]
    dnsmasq-2.76,1 [pfSense] (options changed)
    cyrus-sasl-2.1.26_12 [pfSense]
    check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent)

    Number of packages to be installed: 1
    Number of packages to be upgraded: 39
    Number of packages to be reinstalled: 17

    The process will require 3 MiB more space.
    93 MiB to be downloaded.
    [1/57] Fetching vstr-1.0.15_1.txz: …....... done
    [2/57] Fetching unbound-1.6.1.txz: …....... done
    [3/57] Fetching strongswan-5.5.1_1.txz: …....... done
    [4/57] Fetching squidclamav-6.16.txz: ….... done
    [5/57] Fetching squid-3.5.26.txz: …....... done
    [6/57] Fetching sqlite3-3.17.0.txz: …....... done
    [7/57] Fetching smartmontools-6.5_2.txz: …....... done
    [8/57] Fetching python27-2.7.13_3.txz: …....... done
    [9/57] Fetching pkgconf-1.3.0,1.txz: …... done
    [10/57] Fetching php-xdebug-2.5.0.txz: …....... done
    [11/57] Fetching pftop-0.7_8.txz: ….... done
    [12/57] Fetching pfSense-upgrade-0.23.txz: .. done
    [13/57] Fetching pfSense-rc-2.3.4.txz: . done
    [14/57] Fetching pfSense-pkg-squid-0.4.37.txz: …..... done
    [15/57] Fetching pfSense-pkg-openvpn-client-export-1.4.9.txz: … done
    [16/57] Fetching pfSense-kernel-pfSense_wrap-2.3.4.txz: …....... done
    [17/57] Fetching pfSense-default-config-serial-2.3.4.txz: . done
    [18/57] Fetching pfSense-base-nanobsd-2.3.4.txz: …....... done
    [19/57] Fetching pfSense-2.3.4.txz: . done
    [20/57] Fetching perl5-5.24.1.txz: …....... done
    [21/57] Fetching pcre-8.40.txz: …....... done
    [22/57] Fetching openvpn-client-export-2.4.3_1.txz: …....... done
    [23/57] Fetching openldap-client-2.4.44.txz: …....... done
    [24/57] Fetching ntp-4.2.8p10_2.txz: …....... done
    [25/57] Fetching nginx-1.10.3_1,2.txz: …....... done
    [26/57] Fetching nettle-3.3.txz: …....... done
    [27/57] Fetching lzo2-2.10_1.txz: …....... done
    [28/57] Fetching libxml2-2.9.4.txz: …....... done
    [29/57] Fetching libssh2-1.8.0,3.txz: …....... done
    [30/57] Fetching libsodium-1.0.12.txz: …....... done
    [31/57] Fetching libnghttp2-1.21.0.txz: …....... done
    [32/57] Fetching libltdl-2.4.6.txz: ….. done
    [33/57] Fetching libidn-1.33_1.txz: …....... done
    [34/57] Fetching libiconv-1.14_10.txz: …....... done
    [35/57] Fetching libffi-3.2.1.txz: ….. done
    [36/57] Fetching libedit-3.1.20150325_2,1.txz: …....... done
    [37/57] Fetching lha-1.14i_7.txz: …. done
    [38/57] Fetching ldns-1.7.0.txz: …....... done
    [39/57] Fetching krb5-1.15.1_4.txz: …....... done
    [40/57] Fetching json-c-0.12.1.txz: ….. done
    [41/57] Fetching ipmitool-1.8.18.txz: …....... done
    [42/57] Fetching idnkit-1.0_6.txz: …....... done
    [43/57] Fetching gmp-6.1.2.txz: …....... done
    [44/57] Fetching glib-2.46.2_5.txz: …....... done
    [45/57] Fetching gettext-runtime-0.19.8.1_1.txz: …....... done
    [46/57] Fetching expat-2.2.0_1.txz: …....... done
    [47/57] Fetching dnsmasq-2.76,1.txz: …....... done
    [48/57] Fetching dhcp6-20080615.2.txz: …....... done
    [49/57] Fetching cyrus-sasl-2.1.26_12.txz: …....... done
    [50/57] Fetching curl-7.54.0.txz: …....... done
    [51/57] Fetching clamav-0.99.2_3.txz: …....... done
    [52/57] Fetching check_reload_status-0.0.7.txz: …. done
    [53/57] Fetching ca_root_nss-3.30.2.txz: …....... done
    [54/57] Fetching c-icap-modules-0.4.5.txz: …....... done
    [55/57] Fetching c-icap-0.4.4,2.txz: …....... done
    [56/57] Fetching bind-tools-9.11.1P1.txz: …....... done
    [57/57] Fetching libevent-2.1.8.txz: …....... done
    Checking integrity... done (1 conflicting)
      - libevent-2.1.8 [pfSense] conflicts with libevent2-2.0.22_1 [installed] on /usr/local/bin/event_rpcgen.py
    Checking integrity… done (0 conflicting)
    Conflicts with the existing packages have been found.
    One more solver iteration is needed to resolve them.
    The following 58 package(s) will be affected (of 0 checked):

    Installed packages to be REMOVED:
    libevent2-2.0.22_1

    New packages to be INSTALLED:
    libevent: 2.1.8 [pfSense]

    Installed packages to be UPGRADED:
    python27: 2.7.13_1 -> 2.7.13_3 [pfSense]
    perl5: 5.24.1.r4_1 -> 5.24.1 [pfSense]
    pcre: 8.39_1 -> 8.40 [pfSense]
    libnghttp2: 1.18.0 -> 1.21.0 [pfSense]
    ldns: 1.6.17_5 -> 1.7.0 [pfSense]
    glib: 2.46.2_4 -> 2.46.2_5 [pfSense]
    ca_root_nss: 3.28.1 -> 3.30.2 [pfSense]
    unbound: 1.6.0 -> 1.6.1 [pfSense]
    pkgconf: 1.1.0 -> 1.3.0,1 [pfSense]
    libsodium: 1.0.11_1 -> 1.0.12 [pfSense]
    lha: 1.14i_6 -> 1.14i_7 [pfSense]
    gmp: 5.1.3_3 -> 6.1.2 [pfSense]
    curl: 7.53.1_1 -> 7.54.0 [pfSense]
    strongswan: 5.5.1 -> 5.5.1_1 [pfSense]
    sqlite3: 3.15.1_1 -> 3.17.0 [pfSense]
    pfSense-upgrade: 0.22_1 -> 0.23 [pfSense]
    lzo2: 2.09 -> 2.10_1 [pfSense]
    libssh2: 1.8.0,2 -> 1.8.0,3 [pfSense]
    krb5: 1.14.4 -> 1.15.1_4 [pfSense]
    clamav: 0.99.2_2 -> 0.99.2_3 [pfSense]
    c-icap: 0.4.3,2 -> 0.4.4,2 [pfSense]
    squidclamav: 6.14 -> 6.16 [pfSense]
    squid: 3.5.23 -> 3.5.26 [pfSense]
    smartmontools: 6.5_1 -> 6.5_2 [pfSense]
    php-xdebug: 2.4.1_1 -> 2.5.0 [pfSense]
    pftop: 0.7_7 -> 0.7_8 [pfSense]
    pfSense-rc: 2.3.3_1 -> 2.3.4 [pfSense-core]
    openvpn-client-export: 2.4.1_1 -> 2.4.3_1 [pfSense]
    nginx: 1.10.2_3,2 -> 1.10.3_1,2 [pfSense]
    ipmitool: 1.8.17_1 -> 1.8.18 [pfSense]
    dhcp6: 20080615.1 -> 20080615.2 [pfSense]
    c-icap-modules: 0.4.3 -> 0.4.5 [pfSense]
    bind-tools: 9.11.0P3 -> 9.11.1P1 [pfSense]
    pfSense-pkg-squid: 0.4.36_3 -> 0.4.37 [pfSense]
    pfSense-pkg-openvpn-client-export: 1.4.2_2 -> 1.4.9 [pfSense]
    pfSense-kernel-pfSense_wrap: 2.3.2_1 -> 2.3.4 [pfSense-core]
    pfSense-default-config-serial: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense-base-nanobsd: 2.3.3_1 -> 2.3.4 [pfSense-core]
    pfSense: 2.3.3_1 -> 2.3.4 [pfSense]

    Installed packages to be REINSTALLED:
    libffi-3.2.1 [pfSense]
    gettext-runtime-0.19.8.1_1 [pfSense]
    libiconv-1.14_10 [pfSense]
    libxml2-2.9.4 [pfSense]
    expat-2.2.0_1 [pfSense]
    vstr-1.0.15_1 [pfSense]
    libltdl-2.4.6 [pfSense]
    json-c-0.12.1 [pfSense]
    openldap-client-2.4.44 [pfSense]
    nettle-3.3 [pfSense]
    libidn-1.33_1 [pfSense]
    libedit-3.1.20150325_2,1 [pfSense]
    idnkit-1.0_6 [pfSense]
    cyrus-sasl-2.1.26_12 [pfSense]
    ntp-4.2.8p10_2 [pfSense] (direct dependency changed: libevent)
    dnsmasq-2.76,1 [pfSense] (options changed)
    check_reload_status-0.0.7 [pfSense] (direct dependency changed: libevent)

    Number of packages to be removed: 1
    Number of packages to be installed: 1
    Number of packages to be upgraded: 39
    Number of packages to be reinstalled: 17

    The process will require 1 MiB more space.

    Locking package pfSense-pkg-openvpn-client-export… done.
    Locking package pfSense-pkg-squid... done.
    Unlocking package pfSense-pkg-openvpn-client-export... done.
    Unlocking package pfSense-pkg-squid... done.
    Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.

    Broadcast Message from root@.....                         
            (/dev/pts/0) at 17:20 CEST...

    Upgrade is complete.  Rebooting in 10 seconds.

    There is no abnormaly killed but after reboot it's still the old version! I don't have anything open, only the terminal is used.

    There must be a way to make upgrades saver because it becomes unuseable if every upgrade brings new troubles. As u can see in the posts there are many people with different troubles when running upgrades!



  • Wasn't there an issue at one point with them that the upgrade was successful but it just showed the old version?  Or was that a  dream?


  • Rebel Alliance Developer Netgate

    @ricle:

    There is no abnormaly killed but after reboot it's still the old version! I don't have anything open, only the terminal is used.

    If you connect to the console and manually tell it to boot from the other slice, does it show the new version? If so, does it keep booting the new version after a reboot?

    @ricle:

    There must be a way to make upgrades saver because it becomes unuseable if every upgrade brings new troubles. As u can see in the posts there are many people with different troubles when running upgrades!

    That is one of the reasons we are removing NanoBSD. It was intended to help with issues such as this but it never quite did. Even back when it was first added there were issues and confusion at times which led to it not being reliable, and it never did quite get to where it promised to be. And because it gets run primarily on CF/SD media, some of the failures are bad disks, but some people have a hard time believing that since when the disk is rewritten it sometimes works (because the disk remapped bad spots when fully rewritten), and so on.