Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 460 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

HA Active/Passiv not working after update to 7.404

ShaolinSam
Hi,

i've two 425 with 7.403 installed. Today I started the Up2Date process for 7.404. The up2date on the slave machine runs without any problems. Then the up2date process starts on the other ASG425. Since two hours the state is Up2Date. 

In the HA-Log i can see, which comes every 30 seconds:
2009:07:23-12:53:37 astarov7-2 ctsyncd: ctsyncd started
2009:07:23-12:53:37 astarov7-2 ctsyncd: tuple-cache initialized (hashsize 512)
2009:07:23-12:53:37 astarov7-2 ctsyncd: seq-cache initialized (hashsize 64)
2009:07:23-12:53:37 astarov7-2 ctsyncd: joined mcast group 224.0.0.82:1999
2009:07:23-12:53:37 astarov7-2 ctsyncd: announcement failed: Operation not permitted

And ASG sends an email with the following message:
HA SELFMON WARN: Running during up2date process, aborting! Retry in one hour...

Can anyone help me?


This thread was automatically locked due to age.
  • 0
    After a manual initialized reboot of the slave machine it came up again. In the up2date log i could see that up2date was restarted and finished successfully with another reboot.
    Can i be save, that up2date has run without any errors?
  • 0 in reply to ShaolinSam
    I suspect that this is OK, but I suggest that you report this to Astaro as a bug by submitting a ticket to Astaro Support.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    FWIW, we just experienced the exact same thing upgrading from 7.403 to 7.405 (upgrading both 7.404 and 7.405 at once).

    Initiated the upgrade, the slave at the time installed the updates, rebooted and took over master duties, but then the new slave never applied the updates and rebooted as expected.

    Checking the logs showed the same messages as ShaolinSam on the slave.

    Forcing a reboot of the slave went OK and when it came back up, it installed the pending updates, rebooted and now everything looks OK.
  • 0 in reply to drees
    Hi!

    Just had the same issue on two 320s updating from 7.502 to 7.504.

    Reboot slave solved it.

    Did any of you guys submit a ticket with Astaro? What was their response?

    \ aste
Cookie Information Banner