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

Broken 7.008: Is It Safe To Go Back Into The Water?

James Bourne
I've advised all my customers to NOT install the 7.008 update given the disastrous repercussions it has wreaked over the last few days - ie. wiping your installs. I terminated our own ASG220 with it.

So I'm stuck ... is there a replacement 7.008 that doesn't destroy your ASG? Or a rollup of 7.008 and 7.009 that I can use in preference? I cannot/don't want to take the risk.

My only alternative is to reflash units but that is a nightmare in itself ...

Any help/ideas greatly appreciated.


This thread was automatically locked due to age.
Parents
  • 0
    I haven't seen any workarounds for the "7.008 update wipes config issue". Have you opened a support ticket for it?

    Out of 5 Astaro boxes we have in production, all 5 are running 6.311. One of those is a brand new installation and we still opted for v6.
  • 0 in reply to drees
    Good call. I'm half inclined to rollback. I'll lodge a ticket but I don't know where it will get me?
  • 0 in reply to kcng
    both are the same batch...

    both are running 512MB...... i suspected that i might have a faulty hardware... 

    cause both the environment has almost similiar network layout and load but one crashes often where as the other is fine...

    you views ?


    Two things to try; one is to reload the one that's breaking down on you with the SAI 7.009 image (you can get the ISO from your reseller, it is diffferent from the ASL ISO on the public download site) ... I have heard of some units that may have been loaded at the factory with an older build that caused problems until they were reloaded from scratch.  Or, RMA that unit and get another to try.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to James Bourne
    Hi 

    Just wondered if there was any new info on this. We suffered the 7.008 config wipe and are hesitent to apply any further up2dates at this time. We still run 7.007 but would like to be able to update to the latest version in confidence. 

    7.010 seems to address a number of issues that have been causing us problems. 

    Has anyone had any issues upgrading to 7.010?

    Thanks in Advance
  • 0 in reply to fr76
    7.009 and 7.010 appear to be stable. However, you will need to apply the dreaded (!) 7.008. Astaro updates are not incremental.
  • 0 in reply to James Bourne
    Hi,

    Thanks for that. Having to apply 7.008 does change my viewpoint on applying the up2dates.

    Last time we had to completely rebuild our ASG 320.

    Thanks,
  • 0 in reply to fr76
    The only advice I have received is apply 7.008 and pray (!) or reflash with 7.009. Both a pretty weak solutions.
  • 0 in reply to James Bourne
    Ok so if I select update on the 7.010 patch (skipping the 7.008) it will still apply the 7.008 first?

    If this is the case I am very concerned about doing this on our production Firewalls which are ASG220.  If Astaros line is try it and pray I am very dissappointed with them and this makes their product not enterprise friendly at all.
  • 0 in reply to tank
    Yes. Astaro updates are not rollups (ie. 7.010 doesn't include 7.008 and 7.009).
  • 0 in reply to James Bourne
    I would recommend that you up2date one version number at a time.  I would also recommend that you reboot before and after each update, particularly on a 220 with limited resources.  It would be a good idea to SSH into the box and run top, and watch for everything to settle down, particularly when getting ready to reboot after the 7.008 up2date.  I did this and didn't have any problems.  7.008 is rather large, and makes extensive changes, so give it plenty of time to complete the update.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    I wonder if rebooting the machine before applying the 7.008 update would may also help?
  • 0 in reply to drees
    That's what I suggest(ed)... just to be safe.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Reply Children
  • 0 in reply to BrucekConvergent
    Yes, you are right, read your post too quickly. [:)]
  • 0 in reply to drees
    An update on this entire 7.008 config wiping issue ... I found out from Gert (thanks Gert!) that that it was a bug due to race condition between two instances of the configuration database that affected slower machines only.

    On September 27 an updated 7.008 was made available that fixed the issue. So if you have been holding out updated to 7.008 and beyond, ssh into your machine and check the time stamp on 7.008 update:

    cd /var/up2date/sys
    ls -l *7.008*

    And you should see something like this:

    -rw-r--r-- 1 root root 107631385 Sep 27 13:45 u2d-sys-7.008.tgz.gpgpw 

    You should then be able to hopefully update to 7.008 and beyond without your config getting blatted.
Cookie Information Banner