In my particular case, the alix box was upgraded over the years from 2.0 (when i replaced my WRAP running 1.2), with pretty much every release between 2.0 and 2.1.5. Since it is my home office, I would always upgrade that first to make sure everything worked before upgrading the production boxes at the office and data center.
Like I said, a simple reboot solved it, so it literally could have been any of a million things that just failed on that one boot. On Tue, Sep 9, 2014 at 12:04 PM, Jeremy Porter <jpor...@electricsheepfencing.com> wrote: > Two things would be helpful, did the system start as a clean 2.1.4 or > was it upgraded from a previous version, if so what versions? > I've seen a couple of odd cases, but usually where a system was upgraded > several times. There might have been an issue around 2.03(p1) or so. > We haven't been able to replicate the problem in the lab, so its > possible there is a specific upgrade path that errors. > > > On 9/9/2014 7:21 AM, Vick Khera wrote: >> To be clear, this only happened to me on the 2.1.4 -> 2.1.5 upgrade. >> >> On Tue, Sep 9, 2014 at 8:20 AM, Vick Khera <vi...@khera.org> wrote: >>> On Mon, Sep 8, 2014 at 8:05 PM, Karl Fife <karlf...@gmail.com> wrote: >>>> Has anyone else observed that the serial console stops working after a >>>> WebGUI update? >>> On my ALIX home office router, the serial console disappeared until I >>> did a second reboot. On my higher-end routers running on "real" >>> computers there was no problem with the serial port consoles. >> _______________________________________________ >> List mailing list >> List@lists.pfsense.org >> https://lists.pfsense.org/mailman/listinfo/list > > _______________________________________________ > List mailing list > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
