Bug ID 839597: Restjavad fails to start if provision.extramb has large value

Last Modified: Nov 08, 2019

Bug Tracker

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

Known Affected Versions:
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.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, 12.1.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 15.0.0, 15.0.1

Opened: Oct 16, 2019
Severity: 3-Major

Symptoms

Rolling restarts of restjavad every few seconds typically due to failure to start and reports messages in daemon log: daemon.log: emerg logger: Re-starting restjavad The system reports similar message at the command line. No obvious cause is logged in rest logs.

Impact

This impacts the ability to use the REST API to manage the system

Conditions

-- System DB variable provision.extramb has an unusually high value*: + above ~2700-2800MB for v12.1.0 and earlier. + above ~2900-3000MB for v13.0.0 and later. -- On v13.0.0 and later, sys db variable restjavad.useextramb needs to have the value 'true' *A range of values is shown. When the value is above the approximate range specified, constant restarts are extremely likely, and within tens of MB below that point may be less frequent. To check the values of these system DB varaiables use: tmsh list sys db provision.extramb tmsh list sys db restjavad.useextramb

Workaround

If needing sys db restjavad.useextramb to have the value 'true', keep sys db provision.extramb well below the values listed (e.g., 2000 MB work without issue). To set that at command line: tmsh modify sys db provision.extrammb value 2000 If continual restarts of restjavad are causing difficulties managing the unit on the command line: 1. Stop restjavad (you can copy this string and paste it into the command line on the BIG-IP system): tmsh stop sys service restjavad 2. Reduce the large value of provision.extramb if necessary. 3. Restart the restjavad service: tmsh start sys service restjavad

Fix Information

None

Behavior Change