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

How is the up2date from 7.011 to 7.1 going for you?

number2jcb
I have a single unit environment and don't have the balls to update on the same day anymore.  How is it going for the rest of you?


This thread was automatically locked due to age.
Parents
  • 0
    I've up2dated a few live units from 7.011 to 7.100; noted that on one 320, it took an extra 5 minutes or so after the 3 beeps that normally signify the unit is up and running for the webadmin to come online.  This was only a problem after the first reboot following the up2date installation.  THe other units didn't have this problem, but the key was that I didn't panic, and the 320 came up fine.  I upgraded one that was configured to use AD SSO for the HTTP proxy, and followed the recommendations in the release notes closely, and still the SSO part will not work properly.  It joined the AD domain fine, etc. just keeps reporting access denied.  I've started a case with Astaro on that one... so if you use AD SSO, that might be something to be cautious of ... I just switched the proxy back to standard mode in the meantime.

    Performance is good, so far I like it.

    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
  • 0
    I've up2dated a few live units from 7.011 to 7.100; noted that on one 320, it took an extra 5 minutes or so after the 3 beeps that normally signify the unit is up and running for the webadmin to come online.  This was only a problem after the first reboot following the up2date installation.  THe other units didn't have this problem, but the key was that I didn't panic, and the 320 came up fine.  I upgraded one that was configured to use AD SSO for the HTTP proxy, and followed the recommendations in the release notes closely, and still the SSO part will not work properly.  It joined the AD domain fine, etc. just keeps reporting access denied.  I've started a case with Astaro on that one... so if you use AD SSO, that might be something to be cautious of ... I just switched the proxy back to standard mode in the meantime.

    Performance is good, so far I like it.

    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.

Children
  • 0 in reply to BrucekConvergent
    Thanks, I have a 220 so I bet it will take even longer.  I will probably start the process at about 5am and hope it is up by 7am...

    Any 220 adopters?

    Thanks for the heads up on the SSO.  Did you remove the previous astaro from the domain before upgrading?
  • 0 in reply to number2jcb
    I deleted the computer account for the Astaro, yes.

    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
    Just finished up2date run:

    4 * ASG120 -> No Problem
    2 * ASG220 -> No Problem
    1 * ASG220-HA -> Problem HA-Slave wont to update [:S]

    No further problems with (re)joining ADS

    regards

    Gregor Kemter
  • 0 in reply to gkemter
    Update on my SSO Issue; support found the problem, I'm the first one to have it... a problem with winbindd not initializing because of an outdated winbindd.pid file in /var/locks... we deleted it and restarted the proxy, and it worked.  I've updated 2 other systems since, and no problems.. no SSO issues at all... I guess I was just unlucky with the one that acted up a little.

    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 have install the update on an asg 220 and at reboot busy 100% with no internet no ping totaly asg unavailable...

    so I use my backup 220
  • 0 in reply to nicebud
    I just did two 220 (Rev2) with 7.011 running in a HA setup.
    They didn’t have that much configuration since they were recently installed. 5 legs/ports used, including HA.
    All went well. One click and then I was just a happy observer.
    Node 2 (slave) updated first. Then they switched. Then Node 1 updated.
    Very smooth.

    I will probably do another 220 (Rev1) later this day. This one has a larger configuration though, including a handful of VPN-tunnels.
  • 0 in reply to Hansi
    Updated an ASG 320 using manual update as we did not have the update file yet. No problems. The interface is much faster!! Http Proxy seems quicker also. Great Job Astaro and Beta testers.
  • 0 in reply to Keith_M
    I myself applied it last night, and was surprised by the smooth response and the greatly improved interface.  Now I can use Opera to manage and stop firefox from hogging my system all day.  I don't use SSO right now so all is good.  We shall see what happens down the road.

    Good luck to the 220 that is locked at 100%.  Can you putty in?
  • 0 in reply to nicebud
    I have install the update on an asg 220 and at reboot busy 100% with no internet no ping totaly asg unavailable...

    so I use my backup 220

    I have had astaro boxes hang on an update before.  unplugging the server and repowering it usually kicked it in the pants and it got done with it's setup.  I usually waited an hour before going to that drastic step though.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • 0 in reply to William Warren
    I try waiting... but not resolve...

    new sai 7.100 iso so I install directly on it...

    can't putty because already format
Cookie Information Banner