Update from 2.4.3-p1 no go



  • I'm getting the error - see attached image.
    0_1545167603190_netgate_101010.jpg


  • Rebel Alliance Netgate Administrator

    What trouble shooting have you done?

    Our help documents, and blog post have some starting points:

    I would start on the blog: https://www.netgate.com/blog/pfsense-2-4-4-release-now-available.html

    I cannot stress this enough, please take a backup before doing any work.
    https://www.netgate.com/docs/pfsense/install/upgrade-guide.html



  • You are kidding, right?

    This is a clean install of 2.3 from Netgate repos.
    Upgraded and now this is the result I get when trying to update.
    That's after using "Update from console" from the console menu.
    That should just work no matter what.

    I run several pfsense installs mostly for small companies and at my place, nothing complicated, simple router setup. Wan + Lan interfaces only, not even third interface. No complicated firewall rules, mostly just port forwarding for a few remote desktops.
    Yesterday I did an Openvpn server setup at one place - another sad story which is a topic of it's own.
    All running on standard deskop computers and two installs are on Supermicro server boards (older ones from the early Intel i3 cpu generations).

    I have not had a single update from one version of pfsense to next that would go well.
    On most systems I can't even restart without the thing hanging and I have to go and hit the reset button.
    Last reliable version that actually worked was pfsense 2.0 and since then I would not dream to do a remote upgrade and since 2.3 even remote updates are not possible because the thing hangs on restart.

    I don't know if it's the BSD or the way you have it all put together but in any case, it's on you.
    If you can't get a distro running and rebooting reliably on a simple PC then something is majorly off with your quality.


  • LAYER 8 Netgate

    Your experience differs from most.



  • @derelict said in Update from 2.4.3-p1 no go:

    Your experience differs from most.

    Yes, I see this answer here on these new Facebook-like-forums a lot lately.
    It's never Netgate it's always the user doing something wrong.

    So when I pressed the numbers 1,3, Enter on the keyboard - what did I do wrong?


  • LAYER 8 Netgate

    I have no idea what that means.

    Sure there are problems and defects that crop up from time to time. You seem to be experiencing more than your fair share of them.




  • Banned

    TBH if using pfSense is such a big problem for you then use something else. Whining isn't going to help anything.

    Btw. in the time you wasted whining here you could have done multiple fresh installs with config restores.



  • @grimson said in Update from 2.4.3-p1 no go:

    TBH if using pfSense is such a big problem for you then use something else. Whining isn't going to help anything.

    Btw. in the time you wasted whining here you could have done multiple fresh installs with config restores.

    Are you a Microsoft employee?
    Or perhaps Microsoft bought Netgate?
    The quality of pfsense during last couple of years closely matches Microsoft Windows.
    Because you adhere to their way of doing things - "Just reinstall", no point finding why it's not working "Just do a fresh install".
    This basically makes pfsense not suitable for remote administration.
    Having to drive to a location every time there is a glitch with an update makes it a non contender for corporate firewall software.



  • The advice you were given was pragmatic and meant to get you back up & running quickly, which is usually desirable when your net access is downor your config seems irreparably broken..

    If you're really that upset then simply ask for a refund and move on, but I've worked with other firewalls in the past and I've had upgrade problems with ALL of them at one time or another. At least pfSense isn't a black box and you can poke around and make changes that might fix whatever issue you have. Try doing that on most other firewall appliances. I upgraded a Mikrotik 6 months ago and it blew away ALL of my configuration, including a complex QoS config. That's not to say that the 2.4.4 upgrade could have gone a little smoother, but that nothing is perfect.

    If you have a problem that can be reproduced then log it to redmine and they will fix it.


Log in to reply