Update failed with HAVP and too small /tmp RAM disk

pete

Update stopped this morning. PFSense is working and console is showing it stopped at loading NTP client.

This is the first time I have had an issue with an update.

How can I fix this?

SSHing to the box and running top see two processes running IE: check_reload_status

pfsenseupdate224-1.jpg_thumb

pfsenseupdate224-2.jpg_thumb

pfsenseupdate224-3.jpg_thumb

pete

Downgraded back to pfSense-Full-Update-2.2.3-RELEASE-amd64.tgz manually.

Looked for a while that the downgrading worked and now seeing filesystem full messages.

/tmp write fail messages showing up….did actually see this messages with first update.

So it looks like the update stalled when reinstalling packages.

Shut off RAM usage and downgrade worked after a couple of reboots.

Going to try to update again....same issue being stuck at loading NTP...

Going to downgrade again to pfSense-Full-Update-2.2.3-RELEASE-amd64.tgz and leaving it alone for the time bean.

doktornotor

What packages have you installed? Also post the output of


df -h

pete

Thank you doktornotor.

I downgraded back to pfSense-Full-Update-2.2.3-RELEASE-amd64.tgz and was fine until I tried the upgrade again.

Now I am stuck again relating to my backup configurations?

I did a backup of my configuration before I updated.

The backup xml file saids its version 11.9 which was the first one with the RAM enabled.

I kept doing backups and later xml versions state 11.7.

I am still stuck even though it appears to be booting to version 2.2.3.

Still stopping here while starting 2.2.3 at loading the NTP client.

I was able to earlier downgrade and boot to version 2.2.3 with no issues.

doktornotor

Uhm… if you are running out of space in /tmp because you have moved it to ramdisk, then either increase the size considerably, or simply do NOT move things to ramdisk. This really has nothing to do with 2.2.4 nor any other pfSense version.

pete

Understood doktornotor.

Yup originally went to 100Mb on /var and /tmp. Its been fine except when I went to update it ran out of space in /tmp.

That said downgrading back to 2.2.3 and it is updating the packages installed with no issues right now.

Console booted up fine just now after the upgrading.

Packages that were installed have been the same now for a while.

Snort3, Squid, HAVP AV and a fail over gateway.

Only change over the last few months has been to use RAM.

I will leave the use of RAM off reboot a couple of times, back up configuration and try the update again….later though as I do not currently want to deal with this...

Thinking it has been only the issue of using RAM and setting it to 100Mb.

CPU, Memory and HD space are all fine. Concerned here about the 100% usage which appears to be not an issue though eh?

$ df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad6s1a     64G    4.9G     54G     8%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/md0       3.4M    168K    3.0M     5%    /var/run
devfs          1.0K    1.0K      0B   100%    /var/dhcpd/dev
/dev/md10      958M     12K    881M     0%    /var/tmp/havpRAM
procfs         4.0K    4.0K      0B   100%    /proc

sysinfo2.gif_thumb

sysinfo-1.gif_thumb

doktornotor

@pete:

Concerned here about the 100% usage which appears to be not an issue though eh?

$ df -h
Filesystem     Size    Used   Avail Capacity  Mounted on
/dev/ad6s1a     64G    4.9G     54G     8%    /
devfs          1.0K    1.0K      0B   100%    /dev
/dev/md0       3.4M    168K    3.0M     5%    /var/run
devfs          1.0K    1.0K      0B   100%    /var/dhcpd/dev
/dev/md10      958M     12K    881M     0%    /var/tmp/havpRAM
procfs         4.0K    4.0K      0B   100%    /proc

devfs is NOT the issue ;)

pete

Rebooted 2.2.3 twice and all is well except for the tickle to update.

Other than shutting off RAM use and backing up my configuration before the update are there any other recommendations suggested?

I understand this is a larger package.

I have not had any issues updating PFSense over the last year or so.

Should I disable or remove any of the packages installed?

It's not a big deal to reconfigure them.

doktornotor

Pretty much convinced the issue is due to HAVP. (And, really consider switching to C-ICAP; the HAVP upstream has been dead for years.)

pete

Thank you doktornotor.

Removed HAVP.

Rebooted and will try the update again.

pete

Thank you doktornotor for your help this morning and changing the title of the OP.

I couldn't wait so updated again. Update worked fine and all is well again.

2.2.4-RELEASE (amd64)
built on Sat Jul 25 19:57:37 CDT 2015
FreeBSD 10.1-RELEASE-p15

cmb

Glad to hear it, thanks for the follow up. I updated the thread title so the root cause was clear for others looking for potential problem areas.

doktornotor

@pete:

I couldn't wait so updated again. Update worked fine and all is well again.

2.2.4-RELEASE (amd64)
built on Sat Jul 25 19:57:37 CDT 2015
FreeBSD 10.1-RELEASE-p15

Good to hear that… ;)