/build/static/layout/Breadcrumb_cap_w.png

Patches hung up in a downloading state after upgrade

Three weeks ago I upgraded to 7.0. I have a detect that runs on Monday and a deploy that goes out Wednesday night. It worked as I suspected the first two weeks. Since then I am seeing the majority of my machines in a Downloading state the following Thursday and then there is no movement. Last week I had 5% complete and today just 1%. Is there a new setting in 7.0 that needs to be made/set/adjusted? Is there anything new that needs to be done with the download in 7.0? Is anyone else seeing this?

Thanks for the help.  
Asked 7 years ago 582 views
1 Comment   [ + ] Show comment
  • I am seeing this too. Every system is hung in the detecting, or deploying state. I've adjusted the Detect and Deploy timeouts to the longest, 5 hour, setting. After the 5 hours, systems show a "error" in the Patch Schedule section.
    How many systems are you running your schedule on? I have 394 systems. But only about 150+- are connected at a time when my schedule runs. I've not had any issues in the past, when running that many, even when it's over 200 at once. - griffith.109@osu.edu 7 years ago

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ