Re: [ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

I managed to resolve this issue in the end by removing OSSEC on the client and re-installing and then re-adding the key. I've no idea what happened but I'm guessing something got messed up. Thanks again for your support! On Monday, 31 October 2016 09:38:26 UTC, Pedro S wrote: > > Hi, > > I am

Re: [ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

Hi, I am sorry Mitchell but I can't think about what is happening there, it seems related to the transfer like you said, next step you need will be inserting some debug control messages to figure out what is happening. - When generating the files: client-agent/notify.c

Re: [ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

I did some more testing and simplified the setup. On the agent: + I completed cleared the etc/shared directory of all files + I checked the permissions allowed ossec to write to that directory On the server: + I checked the permissions of the etc/shared directory to ensure the server

Re: [ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

Thanks for your response. The only content in the folder is the *rcl.txt files, the rootkit files, agent.conf and ar.conf. They are all readable by the ossec group. I have a similar set of files on the agent. I do have the "ossec-remoted: DEBUG Sending file 'merged.mg' to agent." log message i

Re: [ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

Hi Sean, OSSEC compress the whole /var/ossec/etc/shared directory, including the agent.conf and push everything (merged.mg) to the agents. Sometimes if you have something not entirely readable on that folder the push fails, what content do you have in shared folder? Everytime a file is sent to th

[ossec-list] Failed md5 for: /etc/shared/merged.mg -- deleting.

Hi all, I've just set up a simple Alienvault server -> FreeBSD 10.3 OSSEC agent. I'm using OSSEC v2.8 on both machines. I've created a blank agent.conf for testing and enabled debug logging and every time I restart the agent and it tries to receive the agent.conf I get this error message on th