Version 2.3.4 is available.

Jailer · May 5, 2017, 9:59 PM

The biggest issue I seem to have with upgrades is the extractions are taking forever. We'll maybe not quite forever but a really long time. Like about an hour. A few individual ones take probably 10 to 15 minutes.

Pretty sure that's not normal.

Intel(R) Pentium(R) 4 CPU 2.66GHz
2 GB RAM
Full install on USB 2 flash drive (idle, so don't think that is the cause)

This exact same behavior is reported by FreeNAS users that install to USB drives. Do yourself a favor and put a cheap SSD in there.

damir · May 5, 2017, 10:57 PM

Well, what i did … as i wrote in this thread ... as 2.3.4 did not work, and i did not have a backup of config from 2.3.3, i upgraded to experimental which worked just fine, made a backup of config and then installed fresh install of 2.3.4 and restored the same backup.

Everything is working fine, and running latest stable version.

JasonAU · May 5, 2017, 11:08 PM

Upgraded fine on my PC Engines APU2 I like the WAN Up time display as I have my ADSL setup to recycle every night

empbilly · May 6, 2017, 2:13 AM

For who was able to update, what is the content of the file /usr/local/etc/pkg/repos/pfSense.conf after the upgrade?

A Former User · May 6, 2017, 2:34 AM

Just performed the upgrade via the web interface and no issues here.

Contents of /usr/local/etc/pkg/repos/pfSense.conf


FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

empbilly · May 6, 2017, 2:49 AM

@tortue:

Just performed the upgrade via the web interface and no issues here.

Contents of /usr/local/etc/pkg/repos/pfSense.conf


FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

Thanks tortue!! My pfsense still does not want to show the update. I tried edit directly to the file and upgrade via shell with option 13, but without success. My dns is ok and I can install packages.

I do not know why it does not work !!!

NOYB · May 6, 2017, 5:35 AM

@Jailer:

@NOYB:

The biggest issue I seem to have with upgrades is the extractions are taking forever. We'll maybe not quite forever but a really long time. Like about an hour. A few individual ones take probably 10 to 15 minutes.

Pretty sure that's not normal.

Intel(R) Pentium(R) 4 CPU 2.66GHz
2 GB RAM
Full install on USB 2 flash drive (idle, so don't think that is the cause)

This exact same behavior is reported by FreeNAS users that install to USB drives. Do yourself a favor and put a cheap SSD in there.

Well I doubt an SSD for the interface of that era is cheep. Even HDD for that era are getting pretty spendy. Haven't looked, but pretty sure SSD is not on the table for 2002 era Dell Inspiron 5100 notebook. I'm okay with it as is with the exception of the upgrades extraction taking so long. Other than that it serves me well for home use.

I could throw the other notebook a colleague donated to me at it to see if it makes any difference. It at least isn't ancient.

Since there is very little activity being indicated, I wonder if maybe the USB driver, or something, is somehow blocking? An hour? The entire USB device could be written/copied in less time. I used to make dup copies of 4 GB USB flash drives on this machine in about 7 minutes or so. That was with earlier versions of FreeBSD. The USB driver has probably changed since then.

kpa · May 6, 2017, 8:05 AM

Check what the mount options are used for the root filesystem on your installation. If it's not using soft-updates the write performance will be absolutely terrible on USB memory.

dorap · May 6, 2017, 9:02 AM

@kpa:

I used the console update (option 13) this time and everything went fine.

I just used the web gui to update my apu2c4 from 2.3.3_1 and everything went fine. I just need to copy the custom amd cpu temperature kernel modul (amdtemp.ko) to /boot/kernel. After reloading the module (or rebooting the system) the temperatures are reported again.

biggsy · May 6, 2017, 9:03 AM

Just updated 2.3.2_1 through the GUI and it said it was going to update to 2.3.3_1 but updated to 2.3.4 instead.

Once it finished, OpenBGP kept restarting every 90 seconds or so.

While looking at the logs I noticed that there were also entries saying that vmWare tools was not running.

Had to reinstall both packages.

k625 · May 6, 2017, 11:41 AM

Hello,

After upgrade to 2.3.4 it shows

Version 2.3.4-RELEASE (i386)
built on Wed May 03 15:22:11 CDT 2017
FreeBSD 10.3-RELEASE-p16

The system is on the latest version.

Platform nanobsd (2g)

Everything is working fine, but why is -p16 and not -p19?
How to update the version of FreeBSD?

Tnx

doktornotor · May 6, 2017, 11:42 AM

Already discussed here: https://forum.pfsense.org/index.php?topic=129998.0

k625 · May 6, 2017, 12:05 PM

I did everything as well in https://forum.pfsense.org/index.php?topic=129998.0 with the same result that is unsuccessfully.

Thx

doktornotor · May 6, 2017, 12:14 PM

Yeah, I'm pointing out that there's an already existing thread about the issue, no need to duplicate it.

M3PH · May 6, 2017, 2:18 PM

I just did the update and it went fine. Only took a couple of minutes but I do have an old Dell desktop with a 50GB HDD and an AMD Athlon 2 x2 B22 with 8GB of ram which is super overkill for what I need it for. It did scare me by retrying to load the interface 4 times at the end of the update but it worked out. I did notice that the processor was running hotter than normal by about 10C but it seems to have calmed down now.

I'm more annoyed that my 35 day uptime streak got broken ;D >:( ::)

Sealr0x · May 6, 2017, 6:55 PM

Just upgraded. No problem! :D :D
Thnx for your excellent work!
Running : c-icap, clamd, dhcpd, dpinger, ntopng, ntpd, snort, squid, squidGuard, sshd and unbound.

dread · May 6, 2017, 5:08 PM

Hi,

Upgaded yesterday. pfSense SG-4860, pfBlockerNG and Snort. Mostly just simple setup.

I had no problems, thanks for developers!

Crispix · May 6, 2017, 5:43 PM

Success! SG-4860 upgraded just fine. Reboot took several minutes longer than usual, which of course is normal for an upgrade, but always a bit of a sweat.

Also ran
pfSsh.php playback generateguicert
from the shell to generate a new certificate for that Chrome issue, thanks for putting that in the release notes.

colinstu · May 6, 2017, 7:01 PM

For some reason the update still isn't showing for me?

I tried rebooting too, no change. Going to the update page too, also doesn't see anything new. ideas?

NOYB · May 6, 2017, 8:53 PM

@kpa:

Check what the mount options are used for the root filesystem on your installation. If it's not using soft-updates the write performance will be absolutely terrible on USB memory.


cat /etc/fstab
# Device                    Mountpoint      FStype  Options         Dump    Pass#
/dev/ufsid/570dcd05b61eb735          /         ufs       rw            1        1
/dev/label/swap0                  none        swap       sw            0        0


mount
/dev/ufsid/570dcd05b61eb735 on / (ufs, local, journaled soft-updates)
devfs on /dev (devfs, local)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)


tunefs -p /dev/ufsid/570dcd05b61eb735
tunefs: POSIX.1e ACLs: (-a)                                disabled
tunefs: NFSv4 ACLs: (-N)                                   disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 enabled
tunefs: soft update journaling: (-j)                       enabled
tunefs: gjournal: (-J)                                     disabled
tunefs: trim: (-t)                                         disabled
tunefs: maximum blocks per file in a cylinder group: (-e)  4096
tunefs: average file size: (-f)                            16384
tunefs: average number of files in a directory: (-s)       64
tunefs: minimum percentage of free space: (-m)             8%
tunefs: space to hold for metadata blocks: (-k)            6408
tunefs: optimization preference: (-o)                      time
tunefs: volume label: (-L)

A little surprised by the device "/dev/ufsid/570dcd05b61eb735". Was expecting something like "/dev/da0s1a".

Looks like it is mounted with journaled soft-updates.
"FreeBSD 9.0 introduced a journaling supplement to soft updates…"
https://en.wikipedia.org/wiki/Soft_updates
https://www.freebsd.org/releases/9.0R/relnotes-detailed.html#FS

Don't recall the version at which updates started taking a long time but it very well may have been around the time of leaving FreeBSD 8.x.
Could the journaling supplement to soft updates cause write performance issues for USB flash drives? It's unclear to me.

https://www.freebsd.org/doc/handbook/configtuning-disk.html