New post
Question
· May 3, 2023

Mirroring. Error message: Failed InstanceLookup (agent probably not running): instance not found

#Mirroring #InterSystems IRIS

Hello everyone!
Maybe someone will tell me what could be the reason for such messages in the message.log file

05/03/23-06:46:27:155 (6584) 0 [Utility.Event] [SYSTEM MONITOR] Mirror state: Member type = Failover, Status = Transition
05/03/23-06:46:27:350 (1620) 1 [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found
05/03/23-06:46:27:351 (1620) 2 [Utility.Event] Failed to become either Primary or Backup at startup
05/03/23-06:46:27:725 (1620) 1 [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found

ISCAgent service is running.

Product version: IRIS 2023.1
$ZV: IRIS for Windows (x86-64) 2022.1.3 (Build 668U) Fri Apr 7 2023 12:37:55 EDT
Discussion (6)2
Log in or sign up to continue
Sergey Petrov · May 4, 2023

Thanks for the answer. But the ISCAgent service is installed and running. The ISCAgent service was the first thing I checked. Restarting the service does nothing.

>> [Utility.Event] Failed InstanceLookup (agent probably not running): instance not found 
The WRC says that this error indicates a problem with the locally installed agent.

0 0
Sergey Petrov · May 5, 2023

We were able to resolve the issue. The WRC noticed an error in the configuration. As it turned out, the agent's address was incorrectly specified on this server. Instead of a locally installed agent, there was an arbiter address causing this error. In the mirror configuration, I changed the agent address for this server and everything worked fine.

1 0