On Thu, Apr 30, 2015 at 1:31 PM, Doug S. Lipp <[email protected]> wrote: > > Greetings, > > > > The company I work for has decided to upgrade the OSSEC client agent to 2.8 > from 2.7.1. I have been provided a pre-compiled executable to do this. I've > found that it appears to install correctly as in place upgrade, but the agent > no longer communicates with the centralized server. Only by removing and > reinstalling 2.7.1 with a valid key, will the agent communicate properly with > the server. Additionally I seem to have the same issue if I remove 2.7.1 and > install 2.8 fresh, then use the same key I was using successfully with 2.7.1. > Is there something I am doing wrong? Do we need to issue new keys once the > agent has been upgraded on the client? Does version 2.8 actually do an in > place upgrade? Thanks in advance for your help. > >
I'm not aware of any issues. Are there any helpful log messages in the ossec.log of the manager? > > > > Doug Lipp - Endpoint Systems & Support - Application Packager > > FirstMerit Corporation > > Email: [email protected] > > Direct: 330-996-6517 > > Mobile: 330-697-4081 > 295 FirstMerit Circle > > Akron, Ohio 44307 > > > > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "ossec-list" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups "ossec-list" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
