Netgate SG-1000 microFirewall

Author Topic: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!  (Read 3144 times)

0 Members and 1 Guest are viewing this topic.

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1765
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #15 on: February 11, 2017, 03:09:19 pm »


Great, it's just a GUI issue. If you went ahead on GUI it would end up leaving you to right version. I'll work on a fix.

This same thing happened to me during the 2.3.2 stable release. Seemed I was the only one so I never complained but was on 2.3.3 snaps on that box from that day on.

Figured it was the loose nut behind the keyboard at the time.

P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline RonpfS

  • Hero Member
  • *****
  • Posts: 684
  • Karma: +96/-2
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #16 on: February 11, 2017, 03:13:28 pm »
Great, it's just a GUI issue. If you went ahead on GUI it would end up leaving you to right version. I'll work on a fix.
OK, I can't update today, maybe tomorrow.
2.3.5-RELEASE (amd64)
Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
pfBlockerNG 2.1.2_1/Dev, suricata 4.0.1

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1765
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #17 on: February 11, 2017, 03:17:18 pm »

What is the upgrade path from 2.3.2 release to 2.3.3rc ? via console or gui?



P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline M_Devil

  • Jr. Member
  • **
  • Posts: 97
  • Karma: +7/-0
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #18 on: February 12, 2017, 06:25:00 am »
Sorry, same question. You can ignore this
« Last Edit: February 12, 2017, 06:31:35 am by M_Devil »

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #19 on: February 12, 2017, 06:53:00 am »

What is the upgrade path from 2.3.2 release to 2.3.3rc ? via console or gui?

Doesn't matter. (The console does not have the wrong version bug.)
Do NOT PM for help!

Offline M_Devil

  • Jr. Member
  • **
  • Posts: 97
  • Karma: +7/-0
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #20 on: February 12, 2017, 06:58:36 am »
Web-GUI and console (13) does not show update to 2.3.3 RC.

Web-GUI
Code: [Select]
Current Base System 2.3.2_1
Latest Base System 2.3.2_1

Console
Code: [Select]
Enter an option: 13

>>> Updating repositories metadata...
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.
Your packages are up to date
*** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfRouter ***


Is there an upgrade path possible, or do we have to wait until release?
« Last Edit: February 12, 2017, 07:02:40 am by M_Devil »

Offline RonpfS

  • Hero Member
  • *****
  • Posts: 684
  • Karma: +96/-2
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #21 on: February 12, 2017, 12:08:23 pm »
FYI Yesterday when I saved an Alias, my system crashed and rebooted
Code: [Select]
i386
10.3-RELEASE-p16
FreeBSD 10.3-RELEASE-p16 #406 d88504507(RELENG_2_3): Fri Feb 10 08:41:18 CST 2017     root@ce23-i386-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense_wrap_vga

Crash report details:

No PHP errors found.

Filename: /var/crash/bounds
1

Filename: /var/crash/info.0
Dump header from device /dev/label/swap0
  Architecture: i386
  Architecture Version: 1
  Dump Length: 157184B (0 MB)
  Blocksize: 512
  Dumptime: Sat Feb 11 17:51:04 2017
  Hostname: pf100se.ici
  Magic: FreeBSD Text Dump
  Version String: FreeBSD 10.3-RELEASE-p16 #406 d88504507(RELENG_2_3): Fri Feb 10 08:41:18 CST 2017
    root@ce23-i386-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense_wrap_vga
  Panic String: double fault
  Dump Parity: 2075499036
  Bounds: 0
  Dump Status: good

Filename: /var/crash/info.last
Dump header from device /dev/label/swap0
  Architecture: i386
  Architecture Version: 1
  Dump Length: 157184B (0 MB)
  Blocksize: 512
  Dumptime: Sat Feb 11 17:51:04 2017
  Hostname: pf100se.ici
  Magic: FreeBSD Text Dump
  Version String: FreeBSD 10.3-RELEASE-p16 #406 d88504507(RELENG_2_3): Fri Feb 10 08:41:18 CST 2017
    root@ce23-i386-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense_wrap_vga
  Panic String: double fault
  Dump Parity: 2075499036
  Bounds: 0
  Dump Status: good
It remained stable after the reboot.

This morning I was able to update from the Web-GUI to

2.3.3-RC (i386)
built on Sat Feb 11 14:28:24 CST 2017
FreeBSD 10.3-RELEASE-p16


2.3.5-RELEASE (amd64)
Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
pfBlockerNG 2.1.2_1/Dev, suricata 4.0.1

Offline kpa

  • Hero Member
  • *****
  • Posts: 1188
  • Karma: +132/-6
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #22 on: February 12, 2017, 12:40:01 pm »
Confirmed, even though the update via the GUI offers 2.3.4 on the stable branch going ahead with the updated gives you '2.3.3.r.20170211.1424' (2.3.3-RC).

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1765
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #23 on: February 12, 2017, 01:48:13 pm »

What is the upgrade path from 2.3.2 release to 2.3.3rc ? via console or gui?

Doesn't matter. (The console does not have the wrong version bug.)

Ill re-state..

What is the upgrade path from 2.3.2 Release?      If we go ahead and update a box that is now on release are we going to get 2.3.3rc or what the GUI states 2.3.4 snap??

Im not talking about the bug.    ;)

P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +956/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #24 on: February 12, 2017, 03:45:01 pm »
No you won't get any snap. Really easy to try from console, there's nothing upgraded till you confirm it.
Do NOT PM for help!

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1765
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #25 on: February 12, 2017, 06:57:38 pm »
No you won't get any snap. Really easy to try from console, there's nothing upgraded till you confirm it.

That was my first thought as well but-   It does in fact want to upgrade to 2.3.4a


Code: [Select]
Enter an option:
Message from syslogd@xxxxx at Feb 12 16:50:43 ...
office php-fpm[98316]: /index.php: Successful login for user 'memyselfI' from: 172.31.125.54
13

>>> Updating repositories metadata...
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.
>>> Upgrading pkg... done.
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: .. done
pfSense-core repository update completed. 12 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 427 packages processed.
>>> Upgrading pfSense-repo... done.
>>> Unlocking package pfSense-kernel-pfSense... done.
The following 104 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        webp: 0.5.2 [pfSense]
        giflib: 5.1.4 [pfSense]
        libnghttp2: 1.18.0 [pfSense]
        norm: 1.5r6 [pfSense]
        liblz4: 131 [pfSense]
        libwww: 5.4.0_6 [pfSense]
        json-c: 0.12.1 [pfSense]

Installed packages to be UPGRADED:
        wol: 0.7.1_2 -> 0.7.1_3 [pfSense]
        vnstat: 1.14 -> 1.15 [pfSense]
        unbound: 1.5.9 -> 1.6.0 [pfSense]
        uclcmd: 0.1 -> 0.1_1 [pfSense]
        tiff: 4.0.6_2 -> 4.0.7_1 [pfSense]
        strongswan: 5.5.0 -> 5.5.1 [pfSense]
        sqlite3: 3.13.0 -> 3.15.1_1 [pfSense]
        python27: 2.7.12 -> 2.7.13_1 [pfSense]
        png: 1.6.21 -> 1.6.27 [pfSense]
        php56-zlib: 5.6.26 -> 5.6.30 [pfSense]
        php56-xmlwriter: 5.6.26 -> 5.6.30 [pfSense]
        php56-xmlreader: 5.6.26 -> 5.6.30 [pfSense]
        php56-xml: 5.6.26 -> 5.6.30 [pfSense]
        php56-tokenizer: 5.6.26 -> 5.6.30 [pfSense]
        php56-sysvshm: 5.6.26 -> 5.6.30 [pfSense]
        php56-sysvsem: 5.6.26 -> 5.6.30 [pfSense]
        php56-sysvmsg: 5.6.26 -> 5.6.30 [pfSense]
        php56-sqlite3: 5.6.26 -> 5.6.30 [pfSense]
        php56-sockets: 5.6.26 -> 5.6.30 [pfSense]
        php56-simplexml: 5.6.26 -> 5.6.30 [pfSense]
        php56-shmop: 5.6.26 -> 5.6.30 [pfSense]
        php56-session: 5.6.26 -> 5.6.30 [pfSense]
        php56-readline: 5.6.26 -> 5.6.30 [pfSense]
        php56-posix: 5.6.26 -> 5.6.30 [pfSense]
        php56-pfSense-module: 0.12 -> 0.13 [pfSense]
        php56-pdo_sqlite: 5.6.26 -> 5.6.30 [pfSense]
        php56-pdo: 5.6.26 -> 5.6.30 [pfSense]
        php56-pcntl: 5.6.26 -> 5.6.30 [pfSense]
        php56-openssl: 5.6.26 -> 5.6.30 [pfSense]
        php56-opcache: 5.6.26_1 -> 5.6.30 [pfSense]
        php56-mcrypt: 5.6.26 -> 5.6.30 [pfSense]
        php56-mbstring: 5.6.26 -> 5.6.30 [pfSense]
        php56-ldap: 5.6.26 -> 5.6.30 [pfSense]
        php56-json: 5.6.26 -> 5.6.30 [pfSense]
        php56-hash: 5.6.26 -> 5.6.30 [pfSense]
        php56-gettext: 5.6.26 -> 5.6.30 [pfSense]
        php56-filter: 5.6.26 -> 5.6.30 [pfSense]
        php56-dom: 5.6.26 -> 5.6.30 [pfSense]
        php56-curl: 5.6.26 -> 5.6.30 [pfSense]
        php56-ctype: 5.6.26 -> 5.6.30 [pfSense]
        php56-bz2: 5.6.26 -> 5.6.30 [pfSense]
        php56-bcmath: 5.6.26 -> 5.6.30 [pfSense]
        php56: 5.6.26 -> 5.6.30 [pfSense]
        php-xdebug: 2.4.0 -> 2.4.1_1 [pfSense]
        php-suhosin: 0.9.38 -> 0.9.38_3 [pfSense]
        pftop: 0.7_6 -> 0.7_7 [pfSense]
        pfSense-rc: 2.3.2_1 -> 2.3.4.a.20170211.1331 [pfSense-core]
        pfSense-pkg-Status_Traffic_Totals: 1.1_1 -> 1.2_1 [pfSense]
        pfSense-kernel-pfSense: 2.3.2_1 -> 2.3.4.a.20170211.1331 [pfSense-core]
        pfSense-default-config: 2.3.2_1 -> 2.3.4.a.20170211.1331 [pfSense-core]
        pfSense-base: 2.3.2_1 -> 2.3.4.a.20170211.1331 [pfSense-core]
        pfSense-Status_Monitoring: 1.4.4_2 -> 1.6.1_3 [pfSense]
        pfSense: 2.3.2_1 -> 2.3.4.a.20170211.1326 [pfSense]
        perl5: 5.20.3_15 -> 5.24.1.r4_1 [pfSense]
        pecl-zmq: 1.1.3_1 -> 1.1.3_2 [pfSense]
        pecl-ssh2: 0.12 -> 0.13 [pfSense]
        pecl-rrd: 1.1.3_3 -> 1.1.3_4 [pfSense]
        pecl-radius: 1.3.0 -> 1.4.0.b1 [pfSense]
        pcre: 8.39 -> 8.39_1 [pfSense]
        p5-Socket: 2.021 -> 2.024 [pfSense]
        p5-Net-SSLeay: 1.74 -> 1.78 [pfSense]
        p5-Net-SMTP-SSL: 1.03 -> 1.04 [pfSense]
        p5-IO-Socket-SSL: 2.029 -> 2.038 [pfSense]
        p5-IO-Socket-IP: 0.37 -> 0.38 [pfSense]
        openvpn: 2.3.11 -> 2.4.0 [pfSense]
        nut: 2.7.4 -> 2.7.4_1 [pfSense]
        ntp: 4.2.8p8 -> 4.2.8p9_1 [pfSense]
        nginx: 1.10.1,2 -> 1.10.2_3,2 [pfSense]
        nettle: 3.2 -> 3.3 [pfSense]
        links: 2.9,1 -> 2.13,1 [pfSense]
        libzmq4: 4.1.4_1 -> 4.1.5 [pfSense]
        libssh2: 1.7.0,2 -> 1.8.0,2 [pfSense]
        libsodium: 1.0.8 -> 1.0.11_1 [pfSense]
        libiconv: 1.14_9 -> 1.14_10 [pfSense]
        libgd: 2.1.0_7,1 -> 2.2.4,1 [pfSense]
        jpeg-turbo: 1.4.2 -> 1.5.1 [pfSense]
        isc-dhcp43-server: 4.3.4 -> 4.3.5 [pfSense]
        isc-dhcp43-relay: 4.3.4_1 -> 4.3.5 [pfSense]
        isc-dhcp43-client: 4.3.4 -> 4.3.5 [pfSense]
        indexinfo: 0.2.4 -> 0.2.6 [pfSense]
        idnkit: 1.0_5 -> 1.0_6 [pfSense]
        glib: 2.46.2 -> 2.46.2_4 [pfSense]
        git: 2.9.0 -> 2.11.0_3 [pfSense]
        gettext-runtime: 0.19.8.1 -> 0.19.8.1_1 [pfSense]
        expat: 2.1.1_2 -> 2.2.0_1 [pfSense]
        dhcp6: 20080615_7 -> 20080615.1 [pfSense]
        curl: 7.50.3 -> 7.52.1_1 [pfSense]
        ca_root_nss: 3.25 -> 3.28.1 [pfSense]
        bind-tools: 9.10.4P2 -> 9.11.0P3 [pfSense]

Installed packages to be REINSTALLED:
        rrdtool-1.6.0_1 [pfSense] (direct dependency changed: perl5)
        p5-Mozilla-CA-20160104 [pfSense] (direct dependency changed: perl5)
        p5-GSSAPI-0.28_1 [pfSense] (direct dependency changed: perl5)
        p5-Error-0.17024 [pfSense] (direct dependency changed: perl5)
        p5-Digest-HMAC-1.03_1 [pfSense] (direct dependency changed: perl5)
        p5-Authen-SASL-2.16_1 [pfSense] (direct dependency changed: perl5)
        net-snmp-5.7.3_11 [pfSense] (direct dependency changed: perl5)
        miniupnpd-1.9.20160113,1 [pfSense] (options changed)

Number of packages to be installed: 7
Number of packages to be upgraded: 89
Number of packages to be reinstalled: 8

The process will require 23 MiB more space.
90 MiB to be downloaded.

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N)
P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline mir

  • Jr. Member
  • **
  • Posts: 93
  • Karma: +9/-0
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #26 on: February 12, 2017, 07:00:30 pm »
No you won't get any snap. Really easy to try from console, there's nothing upgraded till you confirm it.
This is what I see:
Enter an option: 13

>>> Updating repositories metadata...
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.
>>> Unlocking package pfSense-kernel-pfSense... done.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
   scponly-4.8.20110526_2 [pfSense] (options changed)

Number of packages to be reinstalled: 1

19 KiB to be downloaded.

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N)

Offline raidflex

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +1/-0
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #27 on: February 17, 2017, 11:49:49 am »
So how do we update to 2.3.3 RC build if we are currently on 2.3.2 stable? When I go to the development branch I see 2.3.4.

Offline chpalmer

  • Hero Member
  • *****
  • Posts: 1765
  • Karma: +93/-3
    • View Profile
    • Home of Cablenut
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #28 on: February 17, 2017, 11:57:58 am »
So how do we update to 2.3.3 RC build if we are currently on 2.3.2 stable? When I go to the development branch I see 2.3.4.

YMMV and anything else to tell you your on your own but-

This was my method..
Go to system/update/update settings and set it to "snapshots"     (sounds like you already did.)
Now set it to "Stable (Default)"

Go back to "System Update" tab and see what it reports..   You may have to run " pkg upgrade pkg" from the console to get it to work.  (I did on one box and got it to work. Second box seemed to just work.)



P.S. statements made by me are not necessarily condoned by the management of this fine organization.  http://badmodems.com

Offline raidflex

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +1/-0
    • View Profile
Re: HEADS UP: To get 2.3.3 RC builds, switch to "stable" in update settings!
« Reply #29 on: February 17, 2017, 12:09:52 pm »
So how do we update to 2.3.3 RC build if we are currently on 2.3.2 stable? When I go to the development branch I see 2.3.4.

YMMV and anything else to tell you your on your own but-

This was my method..
Go to system/update/update settings and set it to "snapshots"     (sounds like you already did.)
Now set it to "Stable (Default)"

Go back to "System Update" tab and see what it reports..   You may have to run " pkg upgrade pkg" from the console to get it to work.  (I did on one box and got it to work. Second box seemed to just work.)

Thanks for the help, it still shows no updates available on stable and only 2.3.4 on development. I also tried pkg upgrade pkg and it shows 0 updates available.