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

[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' ||
> $specific_platform['name'] == 'RCC' ||
> $specific_platform['name'] == 'SG-2220') {
> $data[] = 'comconsole_port="0x2F8"';
>
>
No, sadly it is not. It is "Super Micro C2758" which has both a physical
COM1 and a virtual COM2, so you can't really force the choice upon someone.

Reading the code, I don't see how all "console*" lines would be removed,
but maybe I misunderstand how the pattern matching is working.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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') {
        $data[] = 'comconsole_port="0x2F8"';


Op 16-5-2018 om 14:48 schreef 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 to enabling the serial console via the GUI.

I've run it this way for years with prior versions of pfSense. It seems now
with version 2.4.3 (possibly earlier 2.4.x, not sure) upon reboot the
/boot/loader.conf.local file gets deleted. Thus the symptoms are that you
create the file, reboot and get serial console, but the file gets removed
during the boot. So on your next boot, no console over SoL.

Ideally, there would be a menu on the GUI for serial console to select the
COM port, but I requested that forever ago and it doesn't seem to be
important enough to get implemented.

The /etc/inc/pfsense-utils.inc file appears to try to filter the
loader.conf.local to remove duplicate settings and delete it if it ends up
empty.  This is done by the function load_loader_conf() which seems like it
does the right thing but clearly it is not including the above line and
thus the file gets deleted. It is easily reproduced by just putting that
single line above into the file and rebooting pfSense.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold



___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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 compared to serial, but when you are doing the job
remotely, and the pfsense device is your core router, how do I log in
and see the serial data?

On Wed, May 16, 2018 at 12:20 PM, Vick Khera  wrote:
> 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 console.
>>
>
> Wow. I call that a high risk upgrade method. Once it logs you out of ssh,
> you just sit there and hope it comes back up. You need to hook your serial
> port (or virtual serial port if you have a BMC that supports that) up as
> the real device console so you can monitor the entire process.
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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 console.
>

Wow. I call that a high risk upgrade method. Once it logs you out of ssh,
you just sit there and hope it comes back up. You need to hook your serial
port (or virtual serial port if you have a BMC that supports that) up as
the real device console so you can monitor the entire process.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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...

--

Steve Yates
ITS, Inc.

-Original Message-
From: List  On Behalf Of WebDawg
Sent: Wednesday, May 16, 2018 9:50 AM
To: pfSense Support and Discussion Mailing List 
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

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  wrote:
> 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 
> running in the background despite the failure?  And I ran it a second time 
> during this?  That's what "KPA" posted last night: "The WebGUI upgrade still 
> seems to suffer from the same problem as it did a while ago which is that it 
> gets disconnected from the real upgrade run and reports a failure when the 
> upgrade is actually running successfully in the background."
>
> --
>
> Steve Yates
> ITS, Inc.
>
> -Original Message-
> From: List  On Behalf Of John Kline
> Sent: Tuesday, May 15, 2018 10:29 PM
> To: pfSense Support and Discussion Mailing List 
> Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata
>
> Many of us a e seeing this.
> See:https://forum.pfsense.org/index.php?topic=147853.0
>
>
>
>
> On Tuesday, May 15, 2018, 7:53 PM, Steve Yates  wrote:
>
> I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an 
> SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately 
> fails, but if I try again it works.  I click the pending-update icon on the 
> dashboard to go to System Update and it detects the update.  I start and I 
> get:
>
> ">>> Updating repositories metadata... done.
> 2.4.3_1 version of pfSense is available"
>
> Then a red bar at the top of the page, "System update failed!"
>
> If I click the already-highlighted System Update tab again, confirm the 
> update, it then immediately installs.
>
> Is anyone else seeing this?
>
> --
>
> Steve Yates
> ITS, Inc.
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
>
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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  wrote:
> 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 
> running in the background despite the failure?  And I ran it a second time 
> during this?  That's what "KPA" posted last night: "The WebGUI upgrade still 
> seems to suffer from the same problem as it did a while ago which is that it 
> gets disconnected from the real upgrade run and reports a failure when the 
> upgrade is actually running successfully in the background."
>
> --
>
> Steve Yates
> ITS, Inc.
>
> -Original Message-
> From: List  On Behalf Of John Kline
> Sent: Tuesday, May 15, 2018 10:29 PM
> To: pfSense Support and Discussion Mailing List 
> Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata
>
> Many of us a e seeing this.
> See:https://forum.pfsense.org/index.php?topic=147853.0
>
>
>
>
> On Tuesday, May 15, 2018, 7:53 PM, Steve Yates  wrote:
>
> I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an 
> SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately 
> fails, but if I try again it works.  I click the pending-update icon on the 
> dashboard to go to System Update and it detects the update.  I start and I 
> get:
>
> ">>> Updating repositories metadata... done.
> 2.4.3_1 version of pfSense is available"
>
> Then a red bar at the top of the page, "System update failed!"
>
> If I click the already-highlighted System Update tab again, confirm the 
> update, it then immediately installs.
>
> Is anyone else seeing this?
>
> --
>
> Steve Yates
> ITS, Inc.
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
>
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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 running in the 
background despite the failure?  And I ran it a second time during this?  
That's what "KPA" posted last night: "The WebGUI upgrade still seems to suffer 
from the same problem as it did a while ago which is that it gets disconnected 
from the real upgrade run and reports a failure when the upgrade is actually 
running successfully in the background."

--

Steve Yates
ITS, Inc.

-Original Message-
From: List  On Behalf Of John Kline
Sent: Tuesday, May 15, 2018 10:29 PM
To: pfSense Support and Discussion Mailing List 
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0 




On Tuesday, May 15, 2018, 7:53 PM, Steve Yates  wrote:

I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an 
SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately 
fails, but if I try again it works.  I click the pending-update icon on the 
dashboard to go to System Update and it detects the update.  I start and I get:

">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"

Then a red bar at the top of the page, "System update failed!"

If I click the already-highlighted System Update tab again, confirm the update, 
it then immediately installs.

Is anyone else seeing this?

--

Steve Yates
ITS, Inc.

___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold



___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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 to enabling the serial console via the GUI.

I've run it this way for years with prior versions of pfSense. It seems now
with version 2.4.3 (possibly earlier 2.4.x, not sure) upon reboot the
/boot/loader.conf.local file gets deleted. Thus the symptoms are that you
create the file, reboot and get serial console, but the file gets removed
during the boot. So on your next boot, no console over SoL.

Ideally, there would be a menu on the GUI for serial console to select the
COM port, but I requested that forever ago and it doesn't seem to be
important enough to get implemented.

The /etc/inc/pfsense-utils.inc file appears to try to filter the
loader.conf.local to remove duplicate settings and delete it if it ends up
empty.  This is done by the function load_loader_conf() which seems like it
does the right thing but clearly it is not including the above line and
thus the file gets deleted. It is easily reproduced by just putting that
single line above into the file and rebooting pfSense.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

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

[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.
> See:https://forum.pfsense.org/index.php?topic=147853.0
>
>
>
>
> On Tuesday, May 15, 2018, 7:53 PM, Steve Yates  wrote:
>
> I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is
> an SG-3100 and one is a PC.  On both, both times, the upgrade almost
> immediately fails, but if I try again it works.  I click the pending-update
> icon on the dashboard to go to System Update and it detects the update.  I
> start and I get:
>
> ">>> Updating repositories metadata... done.
> 2.4.3_1 version of pfSense is available"
>
> Then a red bar at the top of the page, "System update failed!"
>
> If I click the already-highlighted System Update tab again, confirm the
> update, it then immediately installs.
>
> Is anyone else seeing this?
>
> --
>
> Steve Yates
> ITS, Inc.
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
>
>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold