Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 42140 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.
  • 0

    It seems that you updated to 9.317 first.  The correct up2date files from 9.317-5 are ftp.astaro.de/.../u2d-sys-9.317005-350012.tgz.gpg and ftp.astaro.de/.../u2d-sys-9.350012-351003.tgz.gpg.  If you loaded the 9.315-9.350 file, you will need to manually delete it from shell at /var/up2date/sys/ before applying the ones referenced above.

    __________________
    ACE v8/SCA v9.3

    ...still have a v5 install disk in a box somewhere.

    http://xkcd.com
    http://www.tedgoff.com/mb
    http://www.projectcartoon.com/cartoon/1
  • 0 in reply to Scott_Klassen
    Hey Scott,
    I just pushed "Update to latest version". My HA is now in state Master->9315, Slave->9317 (UP2DATE FAILED).
    So I just login via SSH and delete the file and try it again, or have I something special to do on unit 2 (slave)?

    Thanks
    Michael
  • 0

    My problem is almost the same for 9.315 to 9.351 but 1/2.

    Node 2 which usually updates first failed. When I tried again, Node 1 updated successfully.

    Now what? Node 2 shows no sign of wanting to update automatically, and Up2Date shows no updates.

    Rebooting Node 2 did not help either.

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

  • 0 in reply to MichaelMuenz
    Looks like we both had the same problem and were typing about the problem at the same time. LOL Hopefully Scott knows what to do when HA nodes get out of sync.

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

  • 0 in reply to htguru
    htguru, I didn't touch anything after failed update, so my first unit is untouched and the other one is 9.317.
    I think I will reboot the second machine and see what happens. After that I'll update only to 9.317, so both units are same.

    Any suggestions Scott?
  • 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

  • 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)
  • 0

    Sorry guys, been out all day. Just got home. As Scorpion king says, from the Master run ha_utils ssh to connect to the Slave and be able to run commands on it.

    __________________
    ACE v8/SCA v9.3

    ...still have a v5 install disk in a box somewhere.

    http://xkcd.com
    http://www.tedgoff.com/mb
    http://www.projectcartoon.com/cartoon/1
  • 0 in reply to Scott_Klassen

    Thanks to Scott, Billybob and scorpionking.

    After piecing together the above posts, I was able to fix my ha cluster with a little more help from *gasp* the Sophos Knowledge-base.

    https://www.sophos.com/en-us/support/knowledgebase/120870.aspx

    So assuming your slave is out, how I fixed it was:

    ssh loginuser to master

    ha_utils ssl

    password again

    cd /var/up2date/sys

    ls

    I got:

    u2d-sys-9.315002-350012.tgz.gpg  u2d-sys-9.317005-350012.tgz.gpg  u2d-sys-9.350012-351003.tgz.gpg

    So rather then delete all as Billybob wrote, I used:

    su root

    rm u2d-sys-9.315002-350012.tgz.gpg

    This left only the files Scott suggested.

    I then took a look at things by typing ha_utils with out the ssl part:

    ha_utils

    and got something like this:

    - Status -----------------------------------------------------------------------

    Current mode: HA SLAVE with id 2 in state UP2DATE-FAILED

    -- Nodes --------------------------------------------------- eth1 alive --------

    SLAVE: 2 Node2 198.19.250.2 9.317005 UP2DATE-FAILED since Wed Nov 11 02:50:01 2015

    MASTER: 1 Node1 198.19.250.1 9.351003 ACTIVE since Wed Nov 11 02:49:37 2015

    finally I ran:

    /etc/init.d/ha restart

    BAM! It did the rest and rebooted, then synced the slave. Watch the HA Live Log from WebAdmin. All should be well after about 7-10 min. You can also look at "watch up2date in progress" on the up2date page and the up2date live log.

    I am back to Node 1 ACTIVE, Node 2 READY with both on 9.351-3.

    MichaelMuenz, you may need to tinker with the above a little since your units are in different states but do it soon since from what I gather the whole HA is actually down when a unit is in state UP2DATE-FAILED.

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

Unfiltered HTML