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

Up2date from 9.210-20 to 9.304-9 hangs on slave node

Hi,

got a problem. I scheduled to update our utm 220 from 9.210-20 to 9.304-9 for yesterday. Now today I see that the Up2date process is still shown on the slave node and I cannot stop it or reboot the slave node?

Can somebody help?
Is there a way to fix this on slave node? Or do I have to do a hard reboot on the machine directly on monday -,-?

And no there is no possibility to get access to the logs because of 9.210...


Help [:S]

greetz
Philipp


This thread was automatically locked due to age.
Parents
  • Philipp, you should immediately get a support case opened at Sophos.  Someone will need to go in at the command line to check that.  It's possible that just rebooting the node would work, but I wouldn't try that without convincing myself that it was the right thing to do.

    By the way, If you have four Up2Dates showing on the Up2Date page instead of just one to 9.304, Sophos or your reseller will need to delete those at the command line.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Philipp, you should immediately get a support case opened at Sophos.  Someone will need to go in at the command line to check that.  It's possible that just rebooting the node would work, but I wouldn't try that without convincing myself that it was the right thing to do.

    By the way, If you have four Up2Dates showing on the Up2Date page instead of just one to 9.304, Sophos or your reseller will need to delete those at the command line.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data