[ossec-list] Re: Waiting for server reply (not started)

["Daniel Cid" <daniel.cid@xxxxxxxxx>]

Hi Tim,

I didn't understand very well what you meant by: "Did that - I even
uninstalled/reinstalled
the agent on the server side". You don't need to install an agent on
the server side,
since it does everything an agent would do.

What does your server logs says? Any error? Try running the manage_agents tool
again and making sure the authentication keys match.

Hope it helps.

--
Daniel B. Cid
dcid ( at ) ossec.net

On 4/19/07, Tim <boyert@xxxxxxxxx> wrote:
> On Apr 19, 1:58 pm, Jeremy Melanson <jmelan...@xxxxxxxxxxx> wrote:
> > You probably need to reload the OSSEC Server. After you add the host
> > keys, OSSEC needs to reread them. I don't recall which daemon (I suppose
> > I should look that up one of these days ;-). I usually just issue
> > 'ossec-control stop' and 'ossec-control start'.
> >
>
> Did that - I even uninstalled/reinstalled the agent on the server
> side.  No luck.  But just to be safe, I just bounced it again.  Server
> shows it stopped/started:
>
> 2007/04/19 14:33:30 ossec-execd(1314): Shutdown received. Deleting
> responses.
> 2007/04/19 14:33:30 ossec-execd(1225): SIGNAL Received. Exit
> Cleaning...
> 2007/04/19 14:33:30 ossec-execd: Started (pid: 29121).
>
> but agent still can't see it:
>
> 2007/04/19 14:39:38 ossec-agentd(4101): Waiting for server reply (not
> started).
> 2007/04/19 14:47:24 ossec-agentd(4101): Waiting for server reply (not
> started).
>
> -- tim --