Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Fixed In:
11.6.0, 11.5.0 HF1, 11.4.1 HF9
Opened: Dec 26, 2013 Severity: 3-Major Related Article:
K15431
100% of CPU resources could be used by the websso process if it is not started properly. A WebSSO session should be started/restarted using bigstart script. However, if /etc/bigstart/scripts/websso.start script is running manually when previous websso.N proccesses are still working, then it will bring up new websso.N instances that will cause original websso.N proccess to spin in a loop and could use up to 100% of CPU resources.
original websso.N do not function properly and takes ~100% CPU
websso started manually
bigstart restart websso
Now you cannot start more than one instance of WebSSO for every MCPD channel number. For example, if websso.3 is running, then you cannot manually start websso -c 3.
