Two fundamental commands you will use to see what the query and update servers are currently doing in an Asset Control installation are:
- qsti = query server thread information
- usti = update server thread information
Use these two commands to confirm that Asset Control is up and running as well as to get an understanding of how busy the system is.
Here is what the output of qsti typically looks like:
acdba@acbox:~$ qsti
Thread 0: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.026694 secs ()]
Thread 1: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008836 secs ()]
Thread 2: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.009342 secs ()]
Thread 3: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008593 secs ()]
Thread 4: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.009282 secs ()]
Thread 5: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.009267 secs ()]
Thread 6: Idle since 20/12/2018 10:06:05 [4 reqs served, longest: 0.024703 secs ()]
Thread 7: Idle since 20/12/2018 10:06:05 [4 reqs served, longest: 0.008729 secs ()]
Thread 8: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008945 secs ()]
Thread 9: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.012763 secs ()]
Thread 10: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.013543 secs ()]
Thread 11: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008410 secs ()]
Thread 12: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008171 secs ()]
Thread 13: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.008621 secs ()]
Thread 14: Idle since 20/12/2018 10:06:00 [3 reqs served, longest: 0.009039 secs ()]
Thread 15: running AC_CALC_QRY(inverse(M);) for user 100, proc time = 1.148722 secs [3 reqs served, longest: 0.012436 secs ()]
Thread 16: Idle since 17/03/2019 20:52:12 [2 reqs served, longest: 0.023370 secs (AC_LOGON)]
Thread 17: Idle since 20/12/2018 10:06:00 [0 reqs served, longest: 0.000000 secs ()]
Thread 18: Idle since 20/12/2018 10:06:00 [0 reqs served, longest: 0.000000 secs ()]
load: 0%, request buf size: 1024, next in/out: 2/2, request logging: 0. Up since Thu Dec 20 10:06:00 2018
run query buf size: 1024, next in/out: 0/0
Above all, this lets you see how many threads are reserved for the query server. You will also see if threads are currently idle or busy (together with some detail about the nature of the request), how many requests they processed and what their longest processing time was.
The output of usti is very similar:
acdba@acbox:~$ usti
Thread 0: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.089978 secs ()]
Thread 1: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.016705 secs ()]
Thread 2: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.011991 secs ()]
Thread 3: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.010692 secs ()]
Thread 4: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.010504 secs ()]
Thread 5: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.027585 secs ()]
Thread 6: Idle since 20/12/2018 10:06:08 [6 reqs served, longest: 0.163055 secs ()]
Thread 7: Idle since 20/12/2018 10:06:08 [6 reqs served, longest: 0.010013 secs ()]
Thread 8: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.009449 secs ()]
Thread 9: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.009510 secs ()]
Thread 10: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.011461 secs ()]
Thread 11: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.011125 secs ()]
Thread 12: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.010642 secs ()]
Thread 13: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.010160 secs ()]
Thread 14: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.009609 secs ()]
Thread 15: Idle since 20/12/2018 10:06:04 [5 reqs served, longest: 0.009132 secs ()]
Thread 16: Idle since 17/03/2019 20:48:05 [4 reqs served, longest: 0.029309 secs (AC_LOGON)]
load: 0%, request buf size: 1024, next in/out: 2/2, request logging: 0. Up since Thu Dec 20 10:06:04 2018
state: 2, logging ON
Of the available options for these two commands, the one I want to mention here is -k <threadNumber>, e.g.:
acdba@acbox:~$ qsti -k 2
This will attempt to kill the processing of request handled by thread 2. The usage for usti is the same.