Alix 2D13 - Have you upgrade to 2.3 ? Did it go okey?
-
[…]
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.I see a lot of comments saying that RW should be set instead of the default ( RO ) for NanoBSD : why is that ? ???
My current boot slice is in RO but I haven't seen any problems so far
Many CF/SD cards, especially slower ones, are dreadfully slow switching between RW and RO. When functions in the system attempt to switch it on and off a lot, that leads to huge slowdowns on such cards. Even fast cards can get sluggish. In the worst cases, when the card is moving from RW to RO, it blocks other functions.
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed or defaulted to RW soon.
-
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon
Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.
-
The RO switch is a safety belt, not a requirement. It has outlived its usefulness. Likely will be removed to defaulted to RW soon
Yes, given the (seeming to get worse - maybe just aging of media) slowness of CF cards with recent releases, and that actually the system underneath is good about not doing unneeded writes anyway, this seems a good thing to do. It will save loads of forum posts.
Part of this is that the OS used to play fast & loose with filesystem actions. They completed quick but were NO-OPs and didn't properly sync all data in a safe way. I wrote volumes about that back when we first took out the dangerous patches. I suspect FreeBSD 10.3 might be even safer in how it handles remounting, leading to another slow-down, but I have not yet run an in-depth analysis as I did before. Part of the issue is from pkg needing read/write access to its databases and it can't keep them in RAM disks.
-
just want to share my experience
upgraded from 2.2.6 to 2.3 on ALIX.2D3 4 hours ago. ran into the same issue with web interface slowness and dashboard stuck on obtaining update status as well. CPU was 100% used.
change to permanent read/write and disable automatic dashboard auto-update fixed the issue. CPU usage back down to around 4%.
compared to 2.2.6, web interface seems a bit slower on a low power system like ALIX.2D3.
other than that, OpenVPN tunnel, Zabbix Agent LTS are working as expected after the upgrade. Zabbix reported host information change and Zabbix agent version changed after the pfSense upgrade.
going to try upgrading RCC-VE 2440 box later tonight.
-
For what it's worth, I had a very smooth transition from 2.2 -> 2.3. The new UI looks beautiful, and I appreciate the huge amount of new improvements that the team's worked on. Thanks to those who got this out!
-
Hello,
I did the upgrade yesterday on my home Alix, everything stopped to work, pfSense did not boot anymore.The only way I had to restore pfSense was choosing 1 (pfSense 2.2.6) as boot option during the start-up. If I keep the serial console cable connected and I boot with 2.3, the console gets full of garbage chars right after the boot selection.
Also, all the VPNs were disabled after the boot, both IPSec and PPTP, and the dashboard was completely empty.
The upgrade was made using the Auto Upgrade feature. I will try again after having disabled pfBlockerNG (looks like has issues to update the database), in the while I leave you this feedback.
If someone has some information about the console issue after the boot will be appreciated.
Thanks,
Michele -
The only way I had to restore pfSense was choosing 1 (pfSense 2.2.6) as boot option during the start-up. If I keep the serial console cable connected and I boot with 2.3, the console gets full of garbage chars right after the boot selection.
Also, all the VPNs were disabled after the boot, both IPSec and PPTP, and the dashboard was completely empty.
What garbage on the console specifically? Sounds like you had it at a wrong baud rate.
PPTP is gone, so that is disabled. But the IPsec config doesn't get touched during upgrade. The dashboard being blank also indicates some kind of issue. Trying upgrade again after first uninstalling all packages is a good idea.
-
@cmb:
What garbage on the console specifically? Sounds like you had it at a wrong baud rate.
true, even if the Alix sends at 9600bps during the POST, and the console is configured in pfSense at 9600bps.
I am upgrading now, I will update this thread ASAP! ;)
Thanks,
Michele -
Ok, after I set the serial speed to 111500 I was able to see the console.
During the 2.3 boot it hangs at:
Generating RRD graphs…Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc12a67ea stack pointer = 0x28:0xd32de6d8 frame pointer = 0x28:0xd32de6e0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 38891 (ping) [ thread pid 38891 tid 100068 ] Stopped at bcopy+0x1a: repe movsl (%esi),%es:(%edi)then it goes in boot loop.
The only way to recover was setting back the serial at 9600bps and booting with 2.2.6.
I can give the full dump from the console if necessary.
Thanks,
Michele -
It didn't work even after a full RRD clear through the web interface then rebooting, it continue stopping at "Generating RRD graphs".
For now I can only boot on 2.2.6.
Thanks,
Michele -
Upgrade is done and I'm trying to Duplicate boot slice in Diagnostics / NanoBSD.
Clicking on Duplicate and after some time getting an empty page and the following in the log:Apr 15 09:52:20 gw.lan nginx: 2016/04/15 09:52:20 [error] 43594#0: *16 upstream timed out (60: Operation timed out) while reading upstream, client: 192.168.5.61, server: , request: "POST /diag_nanobsd.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "gw.lan", referrer: "http://gw.lan/diag_nanobsd.php"I have already tried to do it twice. How I can make sure that duplication is [not] completed without reboot?
-
Upgrade is done and I'm trying to Duplicate boot slice in Diagnostics / NanoBSD.
Clicking on Duplicate and after some time getting an empty page and the following in the log:Apr 15 09:52:20 gw.lan nginx: 2016/04/15 09:52:20 [error] 43594#0: *16 upstream timed out (60: Operation timed out) while reading upstream, client: 192.168.5.61, server: , request: "POST /diag_nanobsd.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket:", host: "gw.lan", referrer: "http://gw.lan/diag_nanobsd.php"I have already tried to do it twice. How I can make sure that duplication is [not] completed without reboot?
Same problem here. Tried to duplicate the slice and the webinterface timed out. But i saw a running "dd" process even after i closed and
reopened the webinterface so i think the duplication went ok. But i am not sure. -
For those who are seeing "Device busy" or similar and unable to force the disk read-write, try the following (preferably from the console):
umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf
Not something we'd normally recommend but somehow it seems that just the /cf slice is getting wedged for some people at the OS level.
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.
That worked - thanks a lot!!
And it seems to also have fixed the endless "Obtaining update status…". Looks like I'm all set. 8)
-
sorry but a little bit OT..
I upgraded my alix2d13 to 2.3 and everthing runs smoothly..I have seperate AP connected on my lan port..Im moving on new apartment on 2 floors and im thinking to put a minipci card on my alix and put my AP on second floor..running a utp cable is not ideal..would you recommend me a N capable mpci card on our alix??TIA -
I can't get SquidGuard to do a blacklist update. It starts to move the bar and then stops. The screen is reverted to the status before the attempt to load the file. I have deleted the package and did a fresh install with the same results. No error is reported.
After a save and checking the Common ACL the Target Rules list does not show the blacklist.
-
My home Alix upgrade went fine - I only use the AutoConfigBackup, blinkled and Notes packages - I do not use RRD graphing and the CF card is mounted r/w.
Looking through the upgrade log afterwards I found this towards the end of the log:
Misc log: fdisk: invalid fdisk partition table found bsdlabel: /dev/ada0s3: no valid label found bsdlabel: /dev/ada0s3: no valid label found bsdlabel: /dev/ada0s3: no valid label found tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale tar: Failed to set default locale shutdown: [pid 33238]Odd since the CF card has never been used for anything except this machine, I'm assuming that it's just a glitch but it might interest the developers - the rest of the log was fine, no errors and the box is working well - no speed issues. Yes the CPU does run around 50-100% utilization but it's not a big CPU, it's probably time to budget for an upgrade. I disabled the RRD graphs about a year ago to lower the CPU load so this is nothing new.
-
I upgraded from 2.2.6 to 2.3 couple weeks back and the overall net performance has been very poor. Connections to webmail, youtube, google time out every once in a while. I have to refresh web pages or apps frequently.
I did switch the filesystem to permanently rw mode and I don't generally have any problem with the UI or endless "getting update status…" issue.
I don't have any "not-installed-by-default" packages installed and I don't have anything going on the box other than basic routing. I even moved my wireless AP and everything from OPT1 to LAN and have disabled OPT1 interface altogether.
The disabling OPT1 interface did seem to work for first couple of days but now that it has been more than a week I would say it didn't help and the performance is poor.
If there anything else I can check, change to at least acceptable performance from the system?
Please help.
-
I must be one of the few who had very little issues with 2.3 on Alix 2D13. For the record, I run a 60/10 cable connections, 2 WANs (same cable modem, 2 different IPs), 4 LANs (1 with IPV6), 1 OpenVPN server, 3 OpenVPN tunnels 24/7 (to work and VPN providers), basic traffic shaper (using the wizard with some small tweaks). For packages I have PFBlocker and OpenVPN CLient Export.
I upgraded to 2.3 from 2.2.6 without any problems (I was already running in R/W). Performance wise, once I disabled the auto update check, the UI was as responsive as it was in 2.2.x for me.
I had an odd issue with Gateway Monitoring where I had to set the payload to 1 instead of 0, but after that it worked. The other day I installed a 2.3.1 Dev build and it also went very smoothly.
I have zero problems when it comes to downloads, uploads and latency. I can use my full bandwidth from any of my LAN clients. I'm sure that's all I can squeeze out of that hardware, but so far it is working better than I expected.
-
Just upgraded from version 2.1 to 2.3, somehow if I enable proxy, all the traffic will be directed to https, all my users cannot access a lot of the websites, and my users also could access ftp site eventhough I have opened the port on firewall on LAN port, otherwise all works fine.
