Cowboy Denny Posted May 8 Share Posted May 8 The best way to troubleshoot this is to run qkview in verbose so you can identify where the qkview is getting hung up on. If qkview is currently hung press CTRL + C to break out of it. Now when running qkview run it with a -v like this qkview -s0 -v You will get an output similar to this Executing Module: [qknsyncd.so] Module [qknsyncd.so] execution time: 0.015643 Executing Module: [qkcloud.so] Module [qkcloud.so] execution time: 0 Executing Module: [qkafm.so] Module [qkafm.so] execution time: 0 Executing Module: [qkasm.so] Module [qkasm.so] execution time: 0 Executing Module: [qkfips.so] Module [qkfips.so] execution time: 0 Executing Module: [sccp_aom.so] Module [sccp_aom.so] execution time: 0 Executing Module: [qkshared.so] qkshared.so is where the qkview for me stopped for more than 5min and would go no further. (NOTE: qkview is not considered hung until it doesn't move past a certain point after 5min, for example the qkshared.so it never went past this point for much more then 5min) So I broke out of qkview hang up by typing CTRL + C and then I ran the following tmsh restart /sys service statsd After the command completes you can run tmsh show /sys memory Then try and run your qkview command again and hopefully this time it works. Link to comment Share on other sites More sharing options...
Recommended Posts