Re: two opennms servers doing the same thing seperatly at the same place / Unmanaged & Managed state

On Tue, Jun 5, 2012 at 8:45 AM, Bakker, Sander de (DID)
<[email protected]> wrote:
>
> I am working in an environment where we have 1 production ONMS server that
> we are trying to set-up and one server that grew as a test ONMS server(both
> servers are in development).
> Both server are physical servers, both servers are in the same network(and
> have identical routes), both server use their own copy of the same database.
> The production server uses Postgres 8.1 the test server uses Postgres 8.4
>
> Somehow all the nodes on the test ONMS server are in an unmanaged state. In
> the web interface those nodes are configured as managed, i did a rescan but
> this did not help, i unmanaged a node by force and put it in managed again,
> and rescanned the node. Still the node is  unmanaged state on the test ONMS
> server.

Just a guess, but was there a substantial time lapse between copying
the database and starting up the 2nd server?  Or a time difference
between the servers?    If a service is down for 5 days it is
automatically marked as unmanaged and maybe some sort of time warp
would cause it.  A fresh copy of the working DB might fix it.

-- 
   Les Mikesell
      [email protected]

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-install mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-install