Upgrade to 2.1.3
-
@TMonster:
I have these packages installed:
-
squid
-
squidGuard
As for swap usage… no idea.
Do you have caching disabled in Squid? If not the Squid will be writing to your flash boot device continuously. Worse Squid will probably use your 1GB of RAM and start swapping to the flash unless you've taken steps to prevent it. That will burn through the write cycles on the flash in short order, especially if it's cheap flash. You may well have damage on the flash that has caused this.
Steve
-
-
After upgrading from 2.1.2 to 2.1.3, I lost installed packages (SNORT & OpenVPN Client Export). I am running 2.1.3 Nano-VGA-4GB (With RAM Disks). I needed to update both of the packages anyway, but was NOT what I expected from upgrade. :(
Ash,
-
I can't seem to download the 512mb upgrade… Is the 512mb nanobsd upgrade discontinued from 2.1.3 onward? :(
-
…I see the 512MB image for fresh install as well as upgrade in the pfsense.org mirror selection...
-
Yeah, when I try to download it, it's missing = 404 Not Found…
-
Do you have caching disabled in Squid?
No. Using ~1GB for cache
If not the Squid will be writing to your flash boot device continuously.
Hmmm… OK, using:
top -m ioI get:
PID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 90995 proxy 4 0 0 0 0 0 0.00% squidWhich looks like squid's hardly doing much (this is a home office firewall)
Worse Squid will probably use your 1GB of RAM and start swapping to the flash unless you've taken steps to prevent it.
OK, back to top, I get:
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 90995 proxy 1 44 0 154M 149M kqread 7:28 0.00% squidSo, it's not eating too much RAM.
That will burn through the write cycles on the flash in short order, especially if it's cheap flash. You may well have damage on the flash that has caused this.
Wouldn't the installation continue as normal though, with any bad sectors being caught by the underlying disk controller - just like a mechanical drive having bad sectors?
It's not like 1 or 2 files were corrupt and a quick fsck would fix it… I'm talking about /boot/kernel being completely empty here. From memory, only /boot/kernel/pfsense_kernel.txt existed... no .ko files, no kernel.gz, nothing.
I understand your caution over squid's cache on flash memory, but I can't see how that would cause the problem I'm describing.
-
Ok. I was perhaps being a bit alarmist there. You seem to have a good grip on what's actually happening. I was just concerned that you might have been running Squid without understanding the possible consequences.
I agree that a few bad sectors is unlikely to have caused your problem. I wouldn't personally rely on the flash controller to save me in that situation though.Steve
-
has anyone notice that this upgrade changes the 'Firewall Optimization Options' to 'conservative' ?? wtf?
-
has anyone notice that this upgrade changes the 'Firewall Optimization Options' to 'conservative' ?? wtf?
No, because it doesn't. No upgrade has ever touched that config option.
-
Using Pc engines APU1C with latest bios
Pfsense 2.1.2 x64 full install edition on a 20 GB USB 5400 rpm spinning HDD
My boss ran the install script from webgui over the weekend to 2.1.3 and now it cannot find it's kernel.
Running squid, lightsquid and openvpn
Thank god he didn't try it on the other one, 5 hours drive away in Toronto… :-[Any idea when the gold stars are going to be added to the forum?
** Edit
This was caused by not enough space. The pfsense partition I'm using is just over 4 GB since it was originally dd'd from a SD card. I restored to a HDD image from last week and then I deleted the squid cache tree ( rm -rfv /var/squid/cache/* )
Then I invoking the upgrade script and it completed without issue.
