Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread Steve Yates
Huh, I should remember to look there first. So used to this list.  The "sort of scary" part is comments like "Same thing here. The page reported the upgrade had failed. We waited about two minutes and the page refreshed and we logged in. The upgrade had worked after all." Like it's

Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread WebDawg
I upgrade via the console now. Not to say that the GUI is broken, but I must have been a victim of when it was. I have seen what kpa is talking about in that forum thread too. It is why I always ssh in and update from console. On Wed, May 16, 2018 at 10:13 AM, Steve Yates

Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread Steve Yates
I've used the console in the recent past...there was something around the 2.3.3 upgrade where you had to switch it to the development branch and back again to get it to work: https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386 Overall seems like the GUI should work... --

Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread Vick Khera
I just did the upgrade from the console from 2.4.3 to 2.4.3_1 with no problems in the upgrade. I run on an official pfSense brand C2758 device. On Tue, May 15, 2018 at 11:28 PM, John Kline wrote: > Many of us a e seeing this. >

[pfSense] boot/loader.conf.local deleted upon reboot

2018-05-16 Thread Vick Khera
I run pfSense on an official pfSense branded C2758 system. It has a BMC controller that permits me to use a serial over LAN to COM2. In order to make the system console connect to COM2, the following line needs to be added to loader.conf or loader.conf.local: comconsole_port="0x2F8" in addition

Re: [pfSense] boot/loader.conf.local deleted upon reboot

2018-05-16 Thread PiBa
Looks like everything that has the word 'console' in there gets deleted from loader.conf.local.. I suppose the 'platform' is not one of these.?:     if ($specific_platform['name'] == 'RCC-VE' ||         $specific_platform['name'] == 'RCC' ||         $specific_platform['name'] == 'SG-2220') {    

Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread Vick Khera
On Wed, May 16, 2018 at 10:50 AM, WebDawg wrote: > I upgrade via the console now. Not to say that the GUI is broken, but > I must have been a victim of when it was. I have seen what kpa is > talking about in that forum thread too. It is why I always ssh in and > update from

Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-16 Thread WebDawg
I have to do these upgrades remotely, I have very little choice. What is the difference between executing the php installer via point and click and doing the upgrade via ssh? I see the entire upgrade, and the last thing I see before I get disconnected is the call for reboot. It is high risk

Re: [pfSense] boot/loader.conf.local deleted upon reboot

2018-05-16 Thread Vick Khera
On Wed, May 16, 2018 at 2:03 PM, PiBa wrote: > Looks like everything that has the word 'console' in there gets deleted > from loader.conf.local.. > > I suppose the 'platform' is not one of these.?: > if ($specific_platform['name'] == 'RCC-VE' || >