This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

System shows up to date but firmware is waiting

Hi.  I have a UTM running 9.308.

My UTM is on an extremely saturated 3Mb private network that connects to the internet through another UTM.  We have an up2date cache, but it's on the other side of the slow network.

The box is almost out of disk space, having downloaded 20 firmware updates, but it shows as up to date and doesn't give a GUI button to apply the ones that have downloaded.

How can I apply the firmware that has downloaded?

loginuser@001-sophos:/var/up2date/sys > ls
u2d-sys-9.308016-309003.tgz.gpg u2d-sys-9.315002-316004.tgz.gpg u2d-sys-9.350012-351003.tgz.gpg u2d-sys-9.357001-358003.tgz.gpg
u2d-sys-9.309003-310011.tgz.gpg u2d-sys-9.316004-317005.tgz.gpg u2d-sys-9.351003-352006.tgz.gpg u2d-sys-9.358003-404005.tgz.gpg
u2d-sys-9.310011-311003.tgz.gpg u2d-sys-9.317005-318005.tgz.gpg u2d-sys-9.352006-353004.tgz.gpg u2d-sys-9.404005-405005.tgz.gpg
u2d-sys-9.311003-312008.tgz.gpg u2d-sys-9.318005-319005.tgz.gpg u2d-sys-9.353004-354004.tgz.gpg u2d-sys-9.405005-406003.tgz.gpg
u2d-sys-9.312008-313003.tgz.gpg u2d-sys-9.319005-320002.tgz.gpg u2d-sys-9.354004-355001.tgz.gpg u2d-sys-9.406003-407003.tgz.gpg
u2d-sys-9.313003-314013.tgz.gpg u2d-sys-9.320002-321002.tgz.gpg u2d-sys-9.355001-356003.tgz.gpg u2d-sys-9.407003-408004.tgz.gpg
u2d-sys-9.314013-315002.tgz.gpg u2d-sys-9.321002-350012.tgz.gpg u2d-sys-9.356003-357001.tgz.gpg

loginuser@001-sophos:/var/up2date/sys > df
Filesystem     1K-blocks Used Available Use% Mounted on
/dev/sda6          5412452 4935016 179456 97% /
udev                  2021764 92 2021672 1% /dev
tmpfs 2021764 0 2021764 0% /dev/shm
/dev/sda1 338875 15003 301856 5% /boot
/dev/sda5 19853456 2865420 15905720 16% /var/storage
/dev/sda7 26079448 6721044 17944008 28% /var/log
/dev/sda8 1452844 186196 1174796 14% /tmp
tmpfs 2021764 0 2021764 0% /var/sec/chroot-httpd/dev/shm
tmpfs 2021764 0 2021764 0% /var/storage/chroot-reverseproxy/dev/shm
tmpfs 2021764 9428 2012336 1% /var/storage/chroot-http/tmp
tmpfs 2021764 116 2021648 1% /var/storage/chroot-smtp/tmp/ram



This thread was automatically locked due to age.
Parents
  • seems your root directory is full.

    switch up2date download to manual.

    remove newest updates from /var/up2date/sys

    (rm u2d-sys-9.4*)

    wait some minutes ... now you should see updates ready for installation.

    ... otherwise post up2date log.


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • seems your root directory is full.

    switch up2date download to manual.

    remove newest updates from /var/up2date/sys

    (rm u2d-sys-9.4*)

    wait some minutes ... now you should see updates ready for installation.

    ... otherwise post up2date log.


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
  • Before you start, set 'Firmware Download Interval' to "Manual" in WebAdmin.  Then do deletes as Dirk said.  After the deletes, just in case, run /sbin/auisys.plx --showdesc

    After that, apply the Up2Dates in WebAdmin.  Set 'Firmware Download Interval' back to it's original setting when done.

    You might have to delete more with so many Up2Dates to do.

    Visit here occasionally to look for threads about recent Up2Dates.  You will see quickly how far you can Up2Date safely.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Sophos support helped out here.  Somehow the system overlooked one update.  We manually applied it, and the subsequent updates manually from the command line without reboot, up until the last, which I then scheduled with the auto installer.  That worked fine and we are up to date.