On Nov 8, 2016 9:53 AM, "Derek Day" wrote:
>
> If i have a system that has an ossec agent running, and the system needs
to be rebuilt or replaced, using same name and addresses space etc, just a
pc refresh. do i need to generate a new ID and client.keys on the server
side or can i use the same id/
If i have a system that has an ossec agent running, and the system needs to
be rebuilt or replaced, using same name and addresses space etc, just a pc
refresh. do i need to generate a new ID and client.keys on the server side
or can i use the same id/client.keys that was previously created for t
On Tue, Nov 8, 2016 at 9:13 AM, Kumar G wrote:
> Don't know if this falls under same issue. We are getting same error messages
> on one of the ossec server A, no new agents addition via manage_agents or
> ossec_authd were changing the status from "Never connected" to Active after
> adding them.
Don't know if this falls under same issue. We are getting same error messages
on one of the ossec server A, no new agents addition via manage_agents or
ossec_authd were changing the status from "Never connected" to Active after
adding them. Both manual and ossec auth worked out, these were the f
On Nov 8, 2016 4:35 AM, "Whit Blauvelt" wrote:
>
> Hi,
>
> There have been multiple past discussions of email problems. Yet none seem
> to cover this exactly. Here's what's logging, repeatedly:
>
> 2016/11/04 18:33:53 getaddrinfo: Name or service not known
> 2016/11/04 18:33:53 ossec-maild(122
Hi,
There have been multiple past discussions of email problems. Yet none seem
to cover this exactly. Here's what's logging, repeatedly:
2016/11/04 18:33:53 getaddrinfo: Name or service not known
2016/11/04 18:33:53 ossec-maild(1223): ERROR: Error Sending email to
localhost (smtp server)
It
