How to track iwstat ID, Thread?

Hi

Can someone explain about how to track the ID and Thread from the IWSTAT results?

There are more QueryTasks operations are running , new QT operations are starting and it seems never ending unless I do a reset. Couldn't able to find much from logs.

Thanks in advance.
John

Find more posts tagged with

Comments

Adam Stoller

Hi

Can someone explain about how to track the ID and Thread from the IWSTAT results?

There are more QueryTasks operations are running , new QT operations are starting and it seems never ending unless I do a reset. Couldn't able to find much from logs.

Thanks in advance.
John

Are you talking about iwlsat and iwrmat - used to list and/or remove commands registered with iwat - or are you talking about things like iwatpub, iwatsubmit, etc.?

jstephan

Are you talking about iwlsat and iwrmat - used to list and/or remove commands registered with iwat - or are you talking about things like iwatpub, iwatsubmit, etc.?

Hi ghoti,

Thanks for your response, I want to track the results of "iwstat -c" command.

For ex, I want to track the ID and Thread on the following result that I get from "iwstat" command

[HTML]ID Thread User Duration Store Operation
0x3990d2db 0xe04deba0 pop 0.000 - GetServerStatus
0x492901ac 0xd02ccaa1 23.4343 - QueryTasks
[/HTML]

Best
John

Adam Stoller

Hi ghoti,

Thanks for your response, I want to track the results of "iwstat -c" command.

For ex, I want to track the ID and Thread on the following result that I get from "iwstat" command

[HTML]ID Thread User Duration Store Operation
0x3990d2db 0xe04deba0 pop 0.000 - GetServerStatus
0x492901ac 0xd02ccaa1 23.4343 - QueryTasks
[/HTML]

Best
John

Whoops - sorry about my earlier response - I read "iwat" where you said "iwstat" ("maybe it's time I get a thicker set of lenses" - to paraphrase My Cousin Vinny ;-)

I don't believe there is any way to track the internal operations of the process threads - if that's what you're looking to do. However, I'd suggest contacting Support if this is a re-occurring issue (and let us know what happens).

If you're on a Unix system, you could do something like:

% iwstat -i 10 -c | grep QueryTasks

and you'd be able to monitor the existence of the thread.

You could also (on Unix or Windows) use the iwabort CLT to attempt to kill the thread process, but I would not recommend doing that until you talk to Support.

QueryTask itself, seems like a rather odd thing to be running with that kind of duration - perhaps the workflow store is corrupted? Again, I'd check with Support.

Snap 2016-06-14 at 09.36.44.png

Snap 2016-06-14 at 09.38.28.png

jstephan

Whoops - sorry about my earlier response - I read "iwat" where you said "iwstat" ("maybe it's time I get a thicker set of lenses" - to paraphrase My Cousin Vinny ;-)

I don't believe there is any way to track the internal operations of the process threads - if that's what you're looking to do. However, I'd suggest contacting Support if this is a re-occurring issue (and let us know what happens).

If you're on a Unix system, you could do something like:
% iwstat -i 10 -c | grep QueryTasks
and you'd be able to monitor the existence of the thread.

You could also (on Unix or Windows) use the iwabort CLT to attempt to kill the thread process, but I would not recommend doing that until you talk to Support.

QueryTask itself, seems like a rather odd thing to be running with that kind of duration - perhaps the workflow store is corrupted? Again, I'd check with Support.

ghoti++, thanks for the response. I will contact support and update the results.

Hithardha

Hi,

You got any reply from support. I am also seeing so many "QueryWorkFlows" in my system. This system going very slow and it is getting resolved when we restart the services. Please help here if you have resolution. Thank you in advance.

Adam Stoller

Hi,

You got any reply from support. I am also seeing so many "QueryWorkFlows" in my system. This system going very slow and it is getting resolved when we restart the services. Please help here if you have resolution. Thank you in advance.

Besides posting to an old thread - what have you done to try and diagnose the problem?

Hithardha

Hi Ghoti,

Thanks for the reply. Yes i have verified the active jobs, also purged the old workflows and contacted the support too. I am working with support already and i thought I will get some solution here as already some one has faced the same. Thank you.