Why won't Archive manager start? "WARNING: Two servers <hostname X> port 0xbafe and <hostname Y> port 0xbafe have the same service Landscape <landscape handle Z> Service Type "Events" and precedence 10."

Document ID : KB000072652
Last Modified Date : 07/03/2018
Show Technical Document Details
Introduction:
On our Linux system, we have no graphical user interface, so use launchinstdbapp to start the Archive Manager.

Archive fails to start and we see the following in  ArchMgr.out: 

Mar 05 18:33:27 : ArchMgr started as user 'spectrum' 
Mar 05 18:33:27 : ArchMgr validating database. 
Mar 05 18:38:03 : ArchMgr successfully connected to MySQL daemon 
Mar 05 18:38:03 : ArchMgr loaded DDM database with landscape handle <landscape handle Z>
Mar 05 18:38:52 : "WARNING: Two servers <hostname X> port 0xbafe and <hostname Y> 
port 0xbafe have the same service Landscape <landscape handle Z> Service Type "Events" and precedence 10."
Mar 05 18:38:55 : ArchMgr has successfully connected to the SpectroSERVER. 
Mar 05 18:38:55 : Closing all client connections... 
Mar 05 18:38:55 : Stopping CORBA communication... 
Mar 05 18:38:55 : Closing database 
Mar 05 18:38:55 : ArchMgr is shutting down... 
The Archive Manager has been shutdown because it could not determine its precedence. The most likely causes: 
1) Fault-tolerance is not fully established. 
Mar 05 18:38:55 : ArchMgr has successfully shut down. 
 
Question:
Why do see the following warning in ArchMgr.out:
 "WARNING: Two servers <hostname X> port 0xbafe and <hostname Y> port 0xbafe have the same service Landscape <landscape handle Z> Service Type "Events" and precedence 10."
Environment:
Linux with no graphical user interface
Answer:
The hostname of the primary SpectroServer, had been changed by accident, to <hostname x> while the SpectroSERVER was running.
The landscape map showed correctly, until the Archive manager was started using launchinstdbapp and the new incorrect hostname appeared in the entry for the events. 
This must be resolved from the OS level. 

A possible workaround is to use the secondary archive manager, if you have one available.