pfSense Gold Subscription

Author Topic: Update from 2.4.1 to 2.4.2 dev failed  (Read 585 times)

0 Members and 1 Guest are viewing this topic.

Offline bimmerdriver

  • Sr. Member
  • ****
  • Posts: 502
  • Karma: +19/-3
    • View Profile
Update from 2.4.1 to 2.4.2 dev failed
« on: October 25, 2017, 10:54:19 pm »
I was running 2.4.1 since it was released and tried to switch over to 2.4.2 dev. The update failed. Below is a screen capture of the console. freebsd boots, but pfsense is non-functional. I was going to download a snapshot and reinstall, but I thought I'd ask if anyone wants me to look at any files that may indicate what happened before I blow it away.

Offline doktornotor

  • Hero Member
  • *****
  • Posts: 8553
  • Karma: +958/-278
  • Not a pfSense employee, they cannot fire me...
    • View Profile
Re: Update from 2.4.1 to 2.4.2 dev failed
« Reply #1 on: October 26, 2017, 06:19:06 am »
Try reinstalling with next snapshot. Or fix the buggy line yourself - https://github.com/pfsense/pfsense/commit/b0b70737ba38c5b7daca2ba779c5d71159e0ce05#diff-c3916603d3e9accb83275e3ccbddf6e6

Then there's another bug introduced and fixed: https://github.com/pfsense/pfsense/commit/c48651648ceea6bfa4cd83af815af26cabc7d8e1#diff-c3916603d3e9accb83275e3ccbddf6e6

And then there are probably other bugs, and you'll be better off leaving the 2.4.2 thing alone until someone does some QA actually, because this is getting absurd. Not sure which snapshot has both of these fixed, and similar issues would be avoided if someone actually at least tried to load the GUI after making the above broken code changes.
Do NOT PM for help!

Offline ivor

  • Administrator
  • Sr. Member
  • *****
  • Posts: 586
  • Karma: +134/-125
    • View Profile
    • Netgate
Re: Update from 2.4.1 to 2.4.2 dev failed
« Reply #2 on: October 26, 2017, 12:55:33 pm »
And then there are probably other bugs, and you'll be better off leaving the 2.4.2 thing alone until someone does some QA actually, because this is getting absurd. Not sure which snapshot has both of these fixed, and similar issues would be avoided if someone actually at least tried to load the GUI after making the above broken code changes.

You're welcome to help with testing.
Need help fast? Commercial support: https://www.netgate.com/support/

Offline bimmerdriver

  • Sr. Member
  • ****
  • Posts: 502
  • Karma: +19/-3
    • View Profile
Re: Update from 2.4.1 to 2.4.2 dev failed
« Reply #3 on: October 27, 2017, 07:33:33 pm »
I downloaded and installed the 2.4.1 release. I'll try updating to the 2.4.2 snapshot later.
« Last Edit: October 27, 2017, 07:36:48 pm by bimmerdriver »

Offline bullet92

  • Jr. Member
  • **
  • Posts: 53
  • Karma: +0/-0
    • View Profile
Re: Update from 2.4.1 to 2.4.2 dev failed
« Reply #4 on: November 04, 2017, 04:08:40 am »
My firewall failed to update drom 2.4.1 to 2.4.2.
My setup is a physical machine with SSD and intel sata controller. It hangs at boot, says it can't start the kernel. Installation came from an upgrade 2.3.4 --> 2.4.1 Trying to boot the 2.4.0 memstick (i need 2.4.0 or 2.4.2 for PPP VLAN support) and i riceive the same (almost) error. I have an old HP server board (SE316M1) with 2 E5620 and 24G RAM. Now i'm testing my RAM machine,

Offline bimmerdriver

  • Sr. Member
  • ****
  • Posts: 502
  • Karma: +19/-3
    • View Profile
Re: Update from 2.4.1 to 2.4.2 dev failed
« Reply #5 on: November 04, 2017, 11:11:19 am »
My firewall failed to update drom 2.4.1 to 2.4.2.
My setup is a physical machine with SSD and intel sata controller. It hangs at boot, says it can't start the kernel. Installation came from an upgrade 2.3.4 --> 2.4.1 Trying to boot the 2.4.0 memstick (i need 2.4.0 or 2.4.2 for PPP VLAN support) and i riceive the same (almost) error. I have an old HP server board (SE316M1) with 2 E5620 and 24G RAM. Now i'm testing my RAM machine,
That's a different problem than I had. I since successfully updated to 2.4.2. Not sure how much success you will have going directly from 2.3.4 to 2.4.1. If your RAM checks out, you might want to try installing freebsd 11.1 (not pfsense) to see if it's a compatibility issue.