Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 42145 views
  • Users 0 members are here
Options
Suggested
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

Update from 9.315 to 9.351 failed cause of 9.317

MichaelMuenz

Today I wanted to update to the latest 9.351 from my 9.315 but recently there was 9.316 and 9.317 available.

Now the installation failed cause of failed dependencies:

2015:11:11-05:50:01 wall-2 auisys[22912]: You are currently running Version 9.317005, but Version 9.315002 is required for this up2date package.
2015:11:11-05:50:01 wall-2 auisys[22912]:
2015:11:11-05:50:01 wall-2 auisys[22912]: 1. Modules::Logging::msg:46() /</sbin/auisys.plx>Modules/Logging.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 2. Modules::Auisys::Installer::Systemstep::install:149() /</sbin/auisys.plx>Modules/Auisys/Installer/Systemstep.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 3. Modules::Auisys::Up2DatePackages::install:143() /</sbin/auisys.plx>Modules/Auisys/Up2DatePackages.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 4. Modules::Auisys::QueueIterator::process_qfiles:81() /</sbin/auisys.plx>Modules/Auisys/QueueIterator.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 5. main::main:300() auisys.pl
2015:11:11-05:50:01 wall-2 auisys[22912]: 6. main::top-level:35() auisys.pl
2015:11:11-05:50:01 wall-2 auisys[22912]: |=========================================================================
2015:11:11-05:50:01 wall-2 auisys[22912]: id="371J" severity="error" sys="system" sub="up2date" name="Fatal: Version conflict: required version: 9.315002 <=> current version: 9.317005" status="failed" action="install" package="sys"
2015:11:11-05:50:01 wall-2 auisys[22912]:
2015:11:11-05:50:01 wall-2 auisys[22912]: 1. Modules::Logging::alf:100() /</sbin/auisys.plx>Modules/Logging.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 2. Modules::Auisys::Installer::Systemstep::install:152() /</sbin/auisys.plx>Modules/Auisys/Installer/Systemstep.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 3. Modules::Auisys::Up2DatePackages::install:143() /</sbin/auisys.plx>Modules/Auisys/Up2DatePackages.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 4. Modules::Auisys::QueueIterator::process_qfiles:81() /</sbin/auisys.plx>Modules/Auisys/QueueIterator.pm
2015:11:11-05:50:01 wall-2 auisys[22912]: 5. main::main:300() auisys.pl
2015:11:11-05:50:01 wall-2 auisys[22912]: 6. main::top-level:35() auisys.pl
2015:11:11-05:50:01 wall-2 auisys[22912]: [CRIT-311] Firmware Up2Date installation failed
2015:11:11-05:50:22 wall-2 auisys[22912]: |=========================================================================
2015:11:11-05:50:22 wall-2 auisys[22912]: A serious error occured during installation! (20)

Any ideas?



This thread was automatically locked due to age.
Parents
  • 0

    Easiest way... call support.  Otherwise follow along at your own risk.

    If linux savvy, login via ssh and

    cd /var/up2date/sys 
    rm u2d-sys*

    Re-download the files as outlined in scott's post. You should be fine.

    Dirty way...

    change your version to the expected version in your error message (9.315002 in this case) by issuing the following on console/ssh

    echo 9.315002 > /etc/version

    and the failed update would work.

    Best way... If astaro.org was operational, you would have noticed that https://www.astaro.org/gateway-products/hardware-installation-up2date-licensing/59733-9-317-3-soft-release.html is 3 pages long. The reason is that you are not the first ones to have this problem:(

  • 0 in reply to Billybob
    Billybob,

    Thanks a lot for answering.

    Since this is on the passive node I'm wondering if I would need to set the node to active first so that I would be communicating with the second node. Otherwise my presumption is that SSH would be communicating with node one and none of what you have suggested would work. I have no idea if I'm right, I'm just asking since it is a high-availability cluster.

    Also you are absolutely correct that we would be able to see the answer at astaro.org if only Sophos would put all the content back up like they have promised. I can't for the life of me figure out why switching the site to read only removed most of the content but it is absolutely devastating not to have the information there to answer questions before having to ask questions over and over.

    Best Regards - HTG
    Frustrated Sophos Partner seeing all the things
    that brought me to Sophos slowly slip away.
    RIP astaro.org

Reply
  • 0 in reply to Billybob
    Billybob,

    Thanks a lot for answering.

    Since this is on the passive node I'm wondering if I would need to set the node to active first so that I would be communicating with the second node. Otherwise my presumption is that SSH would be communicating with node one and none of what you have suggested would work. I have no idea if I'm right, I'm just asking since it is a high-availability cluster.

    Also you are absolutely correct that we would be able to see the answer at astaro.org if only Sophos would put all the content back up like they have promised. I can't for the life of me figure out why switching the site to read only removed most of the content but it is absolutely devastating not to have the information there to answer questions before having to ask questions over and over.

    Best Regards - HTG
    Frustrated Sophos Partner seeing all the things
    that brought me to Sophos slowly slip away.
    RIP astaro.org

Children
  • 0 in reply to htguru

    On the master you can switch to the slave with:

    ha_utils ssh

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Unfiltered HTML