If both agent and server are properly configured and running ossec, if they cannot connect to each other, you have a network issue. In order to list the agents monitored by the ossec server, see http://ossec-docs.readthedocs.org/en/latest/programs/list_agents.html
On Wed, Nov 4, 2015 at 8:58 AM, Reinaldo Fernandes < [email protected]> wrote: > Shouldn't I receive a connected successfully instead of this warnig? > > I found this and it's says that the agent is having issues to connect to > the server: > > *The following log messages may appear in the ossec.log file on an agent > when it is having issues connecting to a manager:* > > 2011/11/13 18:05:13 ossec-agent: WARN: Process locked. Waiting for > permission...2011/11/13 18:05:24 ossec-agent(4101): WARN: Waiting for server > reply (not started). Tried: '10.10.134.241'.2011/11/13 18:05:26 ossec-agent: > INFO: Trying to connect to server (10.10.134.241:1514).2011/11/13 18:05:26 > ossec-agent: INFO: Using IPv4 for: 10.10.134.241 .2011/11/13 18:05:47 > ossec-agent(4101): WARN: Waiting for server reply (not started). Tried: > '10.10.134.241'. > > > -- > > --- > 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.
