Atomicorp

Ah, OK si that sounds like youre just using the open source builds? If so, then you need to grab the latest source code and build from that the binary your using is quite old and it looks like youre using 3.0, whereas the source tree has patches for the upcoming 4.0 release. If youre using the comm...

mikeshinn wrote:Thats pretty old, I dont think we've put out a version of AEO using a version of OSSEC that old. Can you send me the version number for AEO with this command:

asl -v

It says no such command. Only Ossec is installed it seems.

yum list installed | grep ossec
ossec-hids.x86_64 1:3.3.0-7006.el7.art @atomic
ossec-hids-server.x86_64 1:3.3.0-7006.el7.art @atomic

mikeshinn wrote:Yes the latest version of AEO allows for setting effectively an unlimited limit, just make sure youre using the latest version of AEO.

I am. Where do I change this setting?

mikeshinn wrote:I know in the past this limit was required because not all syslog listeners could handle messages larger than that.

Is there a way to work around this? We have long messages being sent and we need them to be sent in full.

Hey all. We have some rather long messages, around 3000 characters in size. Unfortunately they are being truncated. As you can see in the image below, the end of the field is cut off. Is it possible to increase the message limit so that they would no longer be truncated? Perhaps using something othe...