When opening a support ticket it is often very useful to include a boksinfo snapshot to assist FoxT in resolving your BoKS issue.


boksinfo takes a snapshot of the system it is run on. The main purpose of this snapshot is to help FoxT Customer Services solve BoKS issues. The snapshot includes system information like:

  • OS name and release
  • System activity
  • System configuration
  • Process listings
  • Network configuration

And BoKS information like:

  • BoKS version
  • BoKS ENV file
  • The boks_errlog file (last part if big)
  • BoKS audit logs (last entries)
  • BoKS directory listings
  • The nodekey (a short checksum of the hash i.e not the nodekey or hash of the nodekey itself. This hash algorithm is built in to the hostkey command: hostkey -c and can be used as a simple mechanism to check that the same nodekey is stored in $BOKS_etc/nodekey as defined in the database for this host without actually exposing the key itself)
  • The bcastaddr file (if it exists)
  • BoKS database size
  • boksdiag listings
  • BoKS parameters


Run the command boksinfo, located in $BOKS_sbin (default: /opt/boksm/sbin/), as root. This will run a number of OS-specific checks and collect various BoKS-related information to produce a complete picture of how the system and BoKS is setup. It also contains the last 5000 lines from the BoKS error log, although sometimes this is not enough and you will be asked to provide the full boks_errlog from $BOKS_var (default: /var/opt/boksm/).

Once the operation has completed, boksinfo reports where it has stored the snapshot. The default location is

"$BOKS_var/boksinfo/boksinfo...tar.gz" but this can be changed using the '-o' option.

For additional uses, please see the man page for boksinfo.


There are updated versions of the boksinfo script available as Hotfixes for BoKS Manager 6.5 and 6.6. For BoKS 6.5 use hotfix TFS100913-011843 and for 6.6 use HFBM-0019.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018