There are two symptoms which can cause this problem -
1. The alarms dashboard on the Federator (master) server displays events that have been deleted on the Federated (child) servers
2. Alarms cannot be deleted or acknowledged on the master server, or they may reappear
Usernames and passwords are not synchronized between master and child.
If a user does not exist or has a different password, it is not possible to clear and/or acknowledge alarms originating from the child server.
Usernames and corresponding passwords need to be the same on the master and all children.
In the Management log the following errors occur:
Note: IP address and user name have been hashed with xxxxxx
2009-03-26 12:34:54.606 WARN [Utility-1-thread-2] com.quest.nitro.service.federation.RemoteServer - An attempt to get data from the remote server "jnp://xxxxxxxxxxxxxxx" failed due to an unexpected error (most likely originating on the remote server).
java.lang.SecurityException: Bad user name or password: xxxxxxxxxxx
at com.quest.nitro.service.security.util.SecUtils.acquireSecurityContext(SecUtils.java:932)
at com.quest.nitro.service.federation.RemoteAlarmAccessService.clearAlarm(RemoteAlarmAccessService.java:154)
at sun.reflect.GeneratedMethodAccessor834.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
..............
-------------------------------------------------------------------------------------------
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center