Skip to content

7.10-1

Latest
Latest
Compare
Choose a tag to compare
@MarkCRay MarkCRay released this 14 Oct 20:57
· 12 commits to master since this release
7.10-1
11f49be

LinuxKI version 7.10 is now available (10/14/2024)

This version of LinuxKI supports Linux Kernel versions through 6.8.13 as well as advanced CPU metrics for Intel Emerald Rapids processors. Version 7.10 also introduces the new Continuous Logging feature and Oracle Wait Event statistics. Continuous logging may be helpful in cases where an issue is very intermittent, but can be detected through a monitoring script, such as intermittent high CPU on a specific CPU core. With Continuous Logging, the KI data is continually logged to the in-memory kernel ring buffers until it is instructed to stop logging and proceed to create the LinuxKI dump. To start the continuous logging, use the "-d 0" option when executing the runki script:

$ cd /dev/shm 
$ runki -d 0

To stop the continuous logging, execute the following from from another terminal or from a script/program that is monitoring the server for a specific event:

$ /opt/linuxki/kiinfo -likiend

LinuxKI will try to identify the Oracle Wait Event times based on the Oracle functions found in the sched_switch stack traces. For example:

PID 1638775  oracleinst11
  PPID 1  /usr/lib/systemd/systemd
...
    ******** COMMON ORACLE WAIT EVENTS ********
       Count  AvgWaitMs  MaxWaitMs  TotWaitMs  WaitEvent
         388     37.725     43.116  14637.277  SQL*Net message from dblink
         105     34.374   2220.119   3609.242  SQL*Net message from client
        1328      0.042      0.217     55.433  DB asynchronous IO
          34      0.232      0.407      7.873  db file sequential read
           5      0.335      0.476      1.673  log file sync

Other fixes in this release include:

  • Fixed coredump and bad CPU LDOM values due to lscpu parsing issues
  • Fixed soft lockups/hangs when LiKI calls vfs_stat() on an NFS with a slow network
  • Fixed kiinfo -kitrace on live server showing no events due to first buffer being used is a SYNC buffer causing a negative timestamp
  • WinKI: Fixed RunQTime metrics if a thread terminates and the Thread ID is re-used during the trace
  • WinKI: Symbol Table information for some PDB files were not collected due to a wget failed on 1 PDB file

For more information, please see the LinuxKI MasterClass documentation.

Assets 4
Loading