v0.0.12

Changes in this release:

• The caplin-process-diagnostics.sh script now handles ptrace 'access mode check' failures more gracefully. It detects when /proc/<pid>/exe is not readable by the script user (indicative of a ptrace 'access mode check' failure), and prompts the user to try rerunning the script as root. If the user chooses to continue regardless, the script runs a minimal set of diagnostics.
• The caplin-process-diagnostics.sh script now records the process's effective and real user names
• The caplin-process-diagnostics.sh script now records the script's effective and real user names
• The caplin-process-diagnostics.sh script now records the script version in the log file diagnostics.log
• Both scripts now support a new command-line option --version, which prints the script version and exits

v0.0.11

Changes in this release:

• Fixed iteration count for 'top' diagnostic on process id (PID). The number of iterations was 3 and is now 5.

v0.0.10

Changes in this release:

• Add timestamps to log messages
• Quote variables for compatibility with paths and filenames that contain spaces

v0.0.9

Changes in this release:

• To lessen any potential impact on other processes, lower the scheduling priority of the tar command that generates the final archive:

  nice -n 10 tar …
  

v.0.0.8

Changes in this release:

• Record the configuration files for Red Hat's Automatic Bug Reporting Tool (ABRT) if it is installed.

v0.0.7

Changes in this release:

• Record disk usage for all volumes. Because Caplin Platform log file locations can be reconfigured, diagnostic scripts cannot rely on log files being on the same volume as the process's or core file's binary.

v0.0.6

Changes in this release:

• Record /etc/security/limits.conf
• Record /etc/security/limits.d/*
• Record ulimit -aS and ulimit -aH for current user
• Use -h option for df
• Improve 'Quick start' section in README

v0.0.5

Reduce run time of caplin-process-diagnostics.sh to 20 seconds:

• Make core dump optional (remove from default diagnostics). Use --gcore option to run core dump.
• Reduce top diagnostics to 5 seconds
• Reduce vmstat diagnostics to 5 seconds
• Reduce interval between GDB stack traces to 1 second
• Reduce interval between Java stack traces to 1 second

v0.0.4

Changes in this release:

• Improvements to JVM stack traces in caplin-process-diagnostics.sh:
  • Stack traces are now generated three times, with ten seconds between each trace.
  • Stack traces now use the jcmd Thread.print option -l, to include locked ownable synchronizers in the trace.
• Corrections to README

v0.0.3

Changes to caplin-core-diagnostics.sh:

• Make the GNU Debugger (GDB) an optional dependency, but warn the user that if GDB is not installed, then shared libraries referenced in the core file must be collated manually at a later date. After Caplin Support receive the diagnostics archive from the user, Caplin Support will update the issue ticket with a list of libraries they require in order to analyse the core file.