Bug ID 575919: Running concurrent TMSH instances can result in error in access to history file

Last Modified: Nov 14, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,

Fixed In:
13.0.0, 12.1.5

Opened: Feb 24, 2016
Severity: 3-Major


TMSH writes to the ~/.tmsh-history-username file whenever a command is issued. Running concurrent instances of TMSH can result in a race condition in writing this file.


Updating the history file fails, so the file does not reflect the actual history of the commands that have been issued.


Running multiple instances can cause one instance of TMSH to lock the history file while the other is trying to access it, resulting in an error.


Only run a single instance of TMSH.

Fix Information

Running concurrent TMSH instances no longer results in error in access to history file.

Behavior Change