/build/static/layout/Breadcrumb_cap_w.png

Lockup After Test Report

We have our report person attempting to use KACE to gather data and create custom reports for us. However, he keeps locking up KACE. I'm assuming it's locking up the database.

Does anyone know of a way to unlock/fix this without using the console to reboot the entire K1000 box?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: dchristian 12 years ago
Red Belt
0
I think you should open a ticket with support.

Take it from somebody who writes bad queries, it shouldn't put THAT much of a hit on the box.

Is it anytime you run a report or only a certain one?
Posted by: afincher 12 years ago
Senior Purple Belt
0
It's normally just a bad query that causes the lock up. I'll open up a ticket (once the reboot finishes).

Thanks.
Posted by: GillySpy 12 years ago
7th Degree Black Belt
0
A simple thing they can do is put a limit on their query. most of the time the performance hit is on the data stream and limiting the results can help a lot. Some tools like MySQL workbench have an implied limit.

E..g
select * from MACHINE LIMIT 1000

If you think he is locking it up then he is doing so as the R1 user. If you connect as the R1 user you can see your own processes with the command:
SHOW FULL PROCESSLIST;

If hie statement is not "locked" but yours is (or the UI) is then his statement is the culprit.

If he needs help query writing he'll get more free help here then he from support as it is not the kbox that is broken in that case. If it's something that should work but should have an index or is a mysql bug then we can spot it and send him on to support.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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