Command "palladion-print-logged-users" can not be executed
(Doc ID 3011160.1)
Last updated on MARCH 19, 2024
Applies to:
Oracle Communications Session Monitor - Version 5.2 and laterInformation in this document applies to any platform.
Symptoms
The customer was facing an issue where they cannot execute palladion-print-logged-users.
Changes
This started happening after an upgrade from V5.1 to V5.2):
Below is the error customer can encounter while executing the command:
[root@h01lab ~]# source /opt/oracle/ocsm/ocsm_env.sh
[root@ht01lab ~]# palladion-print-logged-users
Traceback (most recent call last):
File "/opt/oracle/ocsm/usr/bin/palladion-print-logged-users", line 8, in <module>
users = s.usermanagement.getActiveUsers()
File "/usr/lib64/python3.9/xmlrpc/client.py", line 1122, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python3.9/xmlrpc/client.py", line 1464, in __request
response = self.__transport.request(
File "/usr/lib64/python3.9/xmlrpc/client.py", line 1166, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib64/python3.9/xmlrpc/client.py", line 1182, in single_request
return self.parse_response(resp)
File "/usr/lib64/python3.9/xmlrpc/client.py", line 1354, in parse_response
return u.close()
File "/usr/lib64/python3.9/xmlrpc/client.py", line 668, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault 1: "<class 'KeyError'>:'user_info'">
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |