Nanobsd manual upgrade from web gui using file upload takes ages



  • im on the nanobsd on alix and have noticed upgrade using file upload method takes more than 10 mins just to upgrade compared to auto update or console update, the fastest being console which starts upgrading as soon as file has been downloaded, then comes the web gui auto update which takes some time after it has downloaded and the slowest being manual file upload from web gui which downloads the file quickly but then takes very long to start the upgrade process



  • Well its the way they work that makes that like that.
    The file upload takes the file in chunks to the file server.
    The parts get reassembled together and than extracted …...

    No real issue from that really.



  • isnt it same when doing from console or auto update and bytheway y is manual file upload a lot slower than web gui auto update, auto update starts upgrading as soon as it finishes the file download where as file upload method takes almost 10mins for the upgrade to start only, not to mention another 5mins to complete the upgrade process and reboot



  • I told you the methods that run ok just download a file in the background and update with that.
    With manual update you send the file to the server in chunks which need to get reassembled after.
    That is how it works and some work is done from php some from the webserver.

    The other methods just do a simple download without any other work to do when the download finishes.



  • so there is no workaround this?
    during 2.0.1 it was a lot faster and also in my upgrade log i see a few errors, no idea what they r related to



  • Not sure if you put the errors here i can check.
    Other than that i have not pursued this much.



  • currently im on the latest snap, the next snap ill do manually and send the upgrade report but usually the log is huge so ill just paste the error messages



  • I would really like to have the reinstalling of packages as optional.
    Varnish and Squid take ages to upgrade and therefore significantly increase the down time of the router after an upgrade.

    I also noticed that pfblocker turns off after an upgrade. This may be due to the package itself and maybe is even deliberate.
    I'm using it to create some aliases for a port 25 block (It blocks all outgoing traffic to port 25 except for my home country).

    I would really like to be able to upgrade without these packages being reinstalled.


  • Rebel Alliance Developer Netgate

    @frater:

    I would really like to have the reinstalling of packages as optional.
    Varnish and Squid take ages to upgrade and therefore significantly increase the down time of the router after an upgrade.

    I also noticed that pfblocker turns off after an upgrade. This may be due to the package itself and maybe is even deliberate.
    I'm using it to create some aliases for a port 25 block (It blocks all outgoing traffic to port 25 except for my home country).

    I would really like to be able to upgrade without these packages being reinstalled.

    Impossible on NanoBSD. On NanoBSD the update is written to a completely different slice on the CF/disk.
    There is no way to preserve or copy the packages from one slice to the other effectively. It would break more than you'd think it would help.

    If you're upgrading often enough that it's a problem, then you should probably not update so often, as you'll just end up wearing out that CF sooner rather than later. :-)


Locked