Mine has gotten worse! The following appears in the ossec.log: 2008/09/29 09:43:02 ossec-remoted(1403): Incorrectly formated message from '192.168.0.200'. 2008/09/29 09:52:42 ossec-remoted(1403): Incorrectly formated message from '192.168.0.150'. 2008/09/29 09:56:47 ossec-remoted(1403): Incorrectly formated message from '192.168.0.200'.
Hoping an upgrade of the agent to v1.6 will resolve this and the original issue as described below. Thanks, Eric -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of binc Sent: Friday, September 26, 2008 9:48 AM To: ossec-list Subject: [ossec-list] Re: Agent Error in ossec-remoted Hi, same problem here after upgrading the "ossec server" to version 1.6. I've the problem with agent v1.4 or v1.6 ! On the console it seem all work fine... and I receive notification from the client... regards nick On Sep 23, 4:17 pm, [EMAIL PROTECTED] wrote: > Not sure what caused this issue. I have two agents running v1.4 and > both were operational and stable. > > On the 19th of Sept, one sensor started the following error: > 2008/09/23 08:43:51 ossec-remoted:Invalidmessagefrom > '192.168.0.150' (strchr \n) > > The ossec-wui is showing the agent last keep alive as current. No > recent events were provided though. > > Any thoughts? > > Was going to upgrade the agents this week to v1.6, might be a good day > to try it.
