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

Last Modified: Oct 17, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1

Fixed In:
13.0.0, 12.1.5

Opened: Feb 24, 2016

Severity: 3-Major

Symptoms

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.

Impact

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

Conditions

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.

Workaround

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

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips