On Wed, Jun 26, 2013 at 10:48 AM, David Blanton <[email protected]> wrote: > I built an installer for the agent installs because in Production servers we > do not have compilers on them. The agents can start, stop, all PIDs run, > netstat -pan | grep 1514 shows that the server is listening, however I get > an ERROR that the the agent cannot connect to the server (it is transmitting > but server is rejecting). There is no firewall. The ossec.conf file is > updated to whitelist the agent IP and allowed-IPS. > > The Web UI shows that the agent is inactive because of this. Does anybody > have any experience with this? Are there files that cannot be 'made' using > an installer/ghostscript that I should be aware of? >
Binary installs weren't working? What errors are in the ossec.log on the manager (this seems like a very important part of the troubleshooting processes)? > -- > > --- > 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. > > -- --- 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.
