Symptoms:
yyyy-mm-ddThh:mm:ss [36425]ERROR:session_management:Session Available check failed: No JSON object could be decoded Traceback (most recent call last): File "/opt/vmware/share/htdocs/vami/backend/session_management.py", line 113, in sessionsAvailable cls.expiredSession(ConfigManager(f))): File "/usr/lib/applmgmt/base/py/vmware/vherd/base/config_manager.py", line 25, in __init__ object_hook=lambda d: defaultdict(ConfigManager.defaultFactory,d)) File "/usr/lib/python2.7/json/__init__.py", line 291, in load **kw) File "/usr/lib/python2.7/json/__init__.py", line 352, in loads return cls(encoding=encoding, **kw).decode(s) File "/usr/lib/python2.7/json/decoder.py", line 364, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode raise ValueError("No JSON object could be decoded") ValueError: No JSON object could be decoded Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware vCenter Server 7.0.x
VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.5.x
The issue occurs when any of the files in the directory (/var/vmware/applmgmt/session/) is not a valid JSON string.
The VAMI uses the Python script session_management.py to manage the user sessions. For each session, a file with a UUID as the name is created that contains the username, csrfToken, startTime, and lastaccessTime. For each login attempt, all of these files are opened and parsed. If a parse error is thrown, the login fails.
To resolve this issue: