Snaphot Server Broken?



  • I am getting Update Available on my AMD 64 2.1 Dashboard and have clicked and updated like 5 times today and it keeps saying update 10 January available.

    Now l am looking at it in my browser there is only a slew of 9 January updates:

    http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_HEAD/updates/



  • This may not be relevant but there are i386 updates dated 10-Jan-2013.



  • The snapshots are now coming up.

    There is a bug that no matter how many times I upgrade from the GUI, or even by uploading a snapshot I have downloaded, PFSENSE 2.1 appears to lose its mind and keeps saying a new snapshot is available.

    I upgraded using the tedious console way and it now knows it is up to date.

    It would be useful for the developers to consider writing a script that would list a short URL like BITLY next to each snapshot to make the Upgrade From Console easier to do.



  • @mromero:

    It would be useful for the developers to consider writing a script that would list a short URL like BITLY next to each snapshot to make the Upgrade From Console easier to do.

    Update from console:

    Hit 13 - Update from console
    Hit 1 - Source URL
    Hit auto - Automatic url, picks the one in updater settings (?)
    Hit y - Yes allow installation of unsigned image

    Wait for reboot


  • Rebel Alliance Developer Netgate

    There were some issues uploading snapshots yesterday, and I was rewriting some of the functions to save bandwidth later in the day.

    They should be all back to normal now. I upgraded a few VMs and they seem happy so far with the images that uploaded late last night.

    Also it should be a lot less likely now to get a broken/misleading version from the server.

    Before, it was uploading update images twice. Once under the "real" name and again under the latest-* names, and it didn't upload the version files until the end, so during any snapshot upload it would have been possible to update at some point and either get a partial file or one that didn't match the version.

    Now it simply does a symlink to the already-uploaded file and copies the version after that. Much faster, less prone to error, and saves a bunch of bandwidth for each snapshot run.



  • @jimp:

    Before, it was uploading update images twice. Once under the "real" name and again under the latest-* names, and it didn't upload the version files until the end, so during any snapshot upload it would have been possible to update at some point and either get a partial file or one that didn't match the version.

    Now it simply does a symlink to the already-uploaded file and copies the version after that. Much faster, less prone to error, and saves a bunch of bandwidth for each snapshot run.

    Way cool. Thank you for the update and improvements.


Locked