@dan
Restarting the service isn't an option for us, as this runs in the
background on client boxes.
@Antonio,
Yes it does. (i wish it would have been that easy)
We started looking at the code
and found this
It seem the function
if (!s_ip) { merror("%s: WARN: Unable to get hostname for '%s'.",
__local_name, node[i]->content); merror(AG_INV_HOST, __local_name,
node[i]->content); os_strdup("invalid_ip", s_ip); }
On Friday, August 14, 2015 at 1:17:27 PM UTC-7, Antonio Querubin wrote:
>
> On Fri, 14 Aug 2015, Winn Johnston wrote:
>
> > You can also see via netstat the IP it is trying to use is definitely
> not
> > valid
> >
> > root# netstat -lntp udp | grep 1514
> > udp4 0 0 10.20.80.89.51990 255.255.255.255.1514
>
> Independent of ossec, does the server hostname actually resolve to an IP
> address?
>
>
> Antonio Querubin
> e-mail: [email protected] <javascript:>
> xmpp: [email protected] <javascript:>
>
--
---
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.
