Hey all,
One of my ossec-remoted processes is eating up a ton of RAM, to the point
that it eventually crashes. Is there anyway to see what's going on or why
it's doing that? I have around 1800 agents connected.
--
---
You received this message because you are subscribed to the Google
It's empy.
There are *no entries at maillog*.
However, if I send a mail with sendmail (*echo "Subject: sendmail test" |
sendmail -v xxx@xxx.x*xx), at /var/log/maillog:
- May 29 12:04:30 X postfix/pickup[8183]: 638F727EA4: uid=0 from=
May 29 12:04:30 X postfix/cleanup[8218]: 638F727EA4:
On Tue, May 29, 2018, 5:06 AM wrote:
> Hi,
>
> I am receiving the error:
>
>
>
> *2018/05/28 17:29:54 ossec-maild(1223): ERROR: Error Sending email to
> 127.0.0.1 (smtp server)2018/05/28 18:00:01 ossec-maild(1223): ERROR: Error
> Sending email to 127.0.0.1 (smtp server)2018/05/28 18:22:07
>
Hi,
I am receiving the error:
*2018/05/28 17:29:54 ossec-maild(1223): ERROR: Error Sending email to
127.0.0.1 (smtp server)2018/05/28 18:00:01 ossec-maild(1223): ERROR: Error
Sending email to 127.0.0.1 (smtp server)2018/05/28 18:22:07
ossec-maild(1223): ERROR: Error Sending email to
Hello again Mikel,
Those kinds of logs don't generate an alert on the alerts.json file.
They're pretty basic log messages and if they do generate an alert, it
would be a level 0 alert, so again, they won't appear on that file. More
severe or critical logs, such as admin login failure, etc,
