K1000 slowed to a crawl after v.8.0.318 upgrade
Upgraded to v.8.0.318 The K1000 has slowed to a crawl... more than 60 second response time between clicks.
- Waited 48 hours to see if it would resolve.
- Rebooted with same result,
- Rebooted again with database check and have same result.
5 Comments
[ + ] Show comments
-
Ours is useable, but much slower than prior to the update. Rebooting doesn't resolve. Changing virtual performance parameters has no effect. Everything appears to be working; just slower than molasses. - markh4799 6 years ago
-
Check DNS entry, make sure that the primary DNS is not down or unreachable. If the primary DNS is not valid for the appliance, then it will slow down the entire appliance even if there is a secondary DNS entry. - WooLian 6 years ago
-
Primary DNS was point to old DNS server... This was it! Thank you! - CTSSC 6 years ago
-
Thank you ... thank you ... thank you!!!! Changing our primary DNS server worked and now everything is working correctly. It took support over a week and they never found a fix ...but this did the trick! Our primary DNS was pointed to an old server and our secondary DNS was set for Google at 8.8.8.8. I changed the primary DNS to Google's server and it worked. Everything is back up to speed and working correctly so far! - markturnerx 6 years ago
-
I dont have the wait time of 60 seconds, but I do have slow load times in inventory compared to version 7. It takes about 10 seconds to load device detail and other software inventory as well. Anyone else have this problem? - agahlbeck 6 years ago
-
It might be related to one (or more) of several items described under - K1000 slow performance (150659) https://support.quest.com/kb/150659. Modify the items listed in that article and see if that helps improve the performance. - WooLian 6 years ago
-
Tried everything so far still slow performance when using inventory. Have a support ticket in, thanks! - agahlbeck 6 years ago
-
Just to update the past comments. We had Quest look at our K1000 and saw nothing wrong in the logs but did say it was lagging. We deployed the new 8.13 ovf template and restored it back and now it is running the way it should. - agahlbeck 6 years ago
Answers (2)
Please log in to answer
Posted by:
dstarrisom
6 years ago
Haven't seen the same problem. If virtual, have you monitored CPU/memory usage and, if necessary, added additional? Also, if virtual, how is disk IO?
Posted by:
Giuliano.Maria
6 years ago
In our case, it was also very slow ... the task tranferency rate was adjusted .. it improved very little ... and I noticed that the display option of the system was removed.
Remembering that we do not intend to acquire any extra apliance ...
deception and regret