Forum Discussion

Kelemvor's avatar
Kelemvor
Icon for Professor rankProfessor
30 days ago

Changed the IP of my collector server and now it shows as offline...

Hi,

We had to change the subnet of our Collector and it now shows as offline in the LM portal even though the server is up and running and the LM Services are both running and everything seems fine.  Is there somewhere I need to manually update the IP or anything like that?

Thanks.

6 Replies

  • Mike_Moniz's avatar
    Mike_Moniz
    Icon for Professor rankProfessor
    30 days ago

    Where within the LM Portal are you seeing this? The Resources tab? The Collector section of Settings? As this is in AWS are you using LM Cloud (where it auto-adds AWS resources) or as a "traditional" device? If you look at the logs on the collector server, does it report errors communicating with the portal?

    • Kelemvor's avatar
      Kelemvor
      Icon for Professor rankProfessor
      30 days ago

      The collector shows Down on the Collectors page in Settings.  This is in AWS but it's just a regular Windows server acting as a plain-old Collector.  I finally got with support and they had me upload some logs and opened a ticket.  The logs are huge so I didn't know what to look for myself.
      I can browse the internet and go to logicmonitor.com just fine.

      • Mike_Rodrigues's avatar
        Mike_Rodrigues
        Icon for Product Manager rankProduct Manager
        29 days ago

        Kelemvor​ The IP of the collector doesn't really matter; as long as it can hit our servers it should be fine.

        One caveat, if you're cloning collector VMs you just need to make sure you don't have 2 running under the same collector ID.

        I'm not sure where you are with support, but you might just try a reinstall. 

  • Mike_Moniz's avatar
    Mike_Moniz
    Icon for Professor rankProfessor
    30 days ago

    Every 24 hours the collector will restart and get a new encryption key to communicate with the portal. If you restore a backup from before this key change, the collector will not be able to talk with the portal anymore. The hashed credentials is stored in agent.conf so you may need to copy the current key from portal settings > collector > collector settings for that collector > agent.conf tab and copy it into the agent.conf file on the server (or I guess you can copy the whole agent.conf file over). But if you're working with support they should be able to help you with that.

     

    • Kelemvor's avatar
      Kelemvor
      Icon for Professor rankProfessor
      29 days ago

      This is exactly what happened.  I had to get it from the portal and put it in the agent.conf and then things started working.  I thought it had something to do with that, but didn't know how to fix it.

      Thanks.

  • Kelemvor's avatar
    Kelemvor
    Icon for Professor rankProfessor
    30 days ago

    Is there no way to edit a post once it's been posted?  I don't see an edit button anywhere.

    Anyway, a tad more info.  This is in AWS so we couldn't change the subnet of the machine directly.  We had to take a backup of the machine and then restore it in the area we needed it to live.  So, technically it's a different server, but it's really the same server.  Maybe there's something that's linked directly to the server so I need to rest something or reinstall or....

    Any help would be great.  Thanks.