No, there were no interesting entries in the server's ossec.log. I deleted the rids file, restarted the server, and got a connection. Thanks, Dan.
On Friday, March 8, 2013 9:33:52 AM UTC-5, dan (ddpbsd) wrote: > > On Fri, Mar 8, 2013 at 9:19 AM, biciunas <[email protected] <javascript:>> > wrote: > > I upgraded my OSSEC server from 2.6 to 2.7. My 2.6 agents have no > problems > > sending data to the OSSEC server. > > > > I started to upgrade the OSSEC agents. I stopped a 2.6 windows agent, > > uninstalled it, and installed a 2.7 agent. I extracted the existing key > from > > the server (./manage_agents) and used it in the newly installed agent. > > > > When I start the agent, I get a Trying to connect to server INFO > message. I > > bounced the server, the agent, still no connection. tethereal shows the > > request coning in from the agent box to the server, so I know the server > is > > receiving the request. Any ideas? Do I need to generate new keys for the > 2.7 > > agents? > > > > You shouldn't need to, and I don't think you should have had to re-add > the key. Are there any log messages in the ossec server's ossec.log > about this agent? Have you tried clearing the rids on the server for > this agent? > > > -- > > > > --- > > 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] <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- --- 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/groups/opt_out.
