Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    No Reboot After Update

    2.3-RC Snapshot Feedback and Issues - ARCHIVED
    5
    6
    1970
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • cwagz
      cwagz last edited by

      I was running yesterday's snapshot and just tried to update to the snapshot available now.  The system started patching and then stopped.  It never rebooted.  I rebooted it through the GUI and it still shows this on the main page:

      2.3-BETA (amd64)
      built on Sat Mar 26 19:54:12 CDT 2016

      It says it is up-to-date.  On the update page it shows:

      Current Base System 
      2.3.b.20160327.1212

      Latest Base System 
      2.3.b.20160327.1212

      This is the 3/27 build.  Did the update fail to complete?  Can I force it to re-update so the main page displays the correct build date?

      Thanks

      1 Reply Last reply Reply Quote 0
      • S
        Steve_B Developer Netgate last edited by

        Not all updates require a reboot.

        Als ik kan

        1 Reply Last reply Reply Quote 0
        • jimp
          jimp Rebel Alliance Developer Netgate last edited by

          @Steve_B:

          Not all updates require a reboot.

          ^ that.

          Kernel updates require a reboot, base system updates typically do not. If you are already on the most recent kernel when the update is run, then it updates the base and doesn't need to reboot the whole system.

          That sort of update will be less common once 2.3 is released, but it's still possible to see.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • cwagz
            cwagz last edited by

            Thanks Steve and Jim.

            It makes sense that a reboot would not always be required.

            I guess I was expecting to see the build date change from Sat Mar 26 to Sun Mar 27 on the dashboard after the update since the build itself seemed to have a 3/27 build date.  Does the date only apply to the kernel portion?

            Chad

            1 Reply Last reply Reply Quote 0
            • MikeV7896
              MikeV7896 last edited by

              Maybe an improvement for 2.3.1… rather than just say "Updates are available", list out what packages will be updated when the Update button is pressed. Obviously we can see what packages get updated as the update process goes, but it's nice to know what will be done before clicking the button. Plus, knowing if a reboot would be required because pfsense-kernel is among those being updated would allow for downtime planning in a business environment.

              The S in IOT stands for Security

              1 Reply Last reply Reply Quote 0
              • Raul Ramos
                Raul Ramos last edited by

                @virgiliomi:

                Maybe an improvement for 2.3.1… rather than just say "Updates are available", list out what packages will be updated when the Update button is pressed. Obviously we can see what packages get updated as the update process goes, but it's nice to know what will be done before clicking the button. Plus, knowing if a reboot would be required because pfsense-kernel is among those being updated would allow for downtime planning in a business environment.

                Agree. Or at least a reboot latter? scheduler reboot? update in a scheduler if any update? ok to much probably.

                pfSense:
                ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post