Re: [ossec-list] segmentation fault

2012-12-17 Thread dan (ddp)
On Mon, Dec 17, 2012 at 10:31 PM, Carrie Poole wrote: > The segfaults in /var/log/messages are: > Dec 17 15:45:24 abeossecpr kernel: ossec-remoted[6378]: segfault at > 02d1 rip 0042191b rsp 7fff87247e90 error 4 > Dec 17 15:48:56 abeossecpr kernel: ossec-remoted[6627]: segfa

RE: [ossec-list] segmentation fault

2012-12-17 Thread Carrie Poole
This is the only line that matches the segfault error in the logs: testconfig() { # We first loop to check the config. for i in ${SDAEMONS}; do ${DIR}/bin/${i} -t ${DEBUG_CLI}; if [ $? != 0 ]; then echo "${i}: Configuration error. Exiting" unlock;

RE: [ossec-list] segmentation fault

2012-12-17 Thread Carrie Poole
The segfaults in /var/log/messages are: Dec 17 15:45:24 abeossecpr kernel: ossec-remoted[6378]: segfault at 02d1 rip 0042191b rsp 7fff87247e90 error 4 Dec 17 15:48:56 abeossecpr kernel: ossec-remoted[6627]: segfault at 02d1 rip 0042191b rsp 7fff76959d

Re: [ossec-list] web_rules.xml , is triggering alert , but we are not geting email

2012-12-17 Thread dan (ddp)
On Mon, Dec 17, 2012 at 3:49 PM, Dhinakaran G wrote: > Hi all, > > In web_rules.xml rule is triggering alert that are stored in the log , but > not reaching our email notication , any idea. > > here the file: > > > > web-log > Access log messages grouped. > > >

Re: [ossec-list] segmentation fault

2012-12-17 Thread dan (ddp)
On Mon, Dec 17, 2012 at 7:17 PM, Carrie Poole wrote: > Line 138 in ossec.conf is the active response, which is disabled: > > > > > > yes > > > > host-deny > > local > > 6 > > 600 > >

RE: [ossec-list] segmentation fault

2012-12-17 Thread Carrie Poole
Line 138 in ossec.conf is the active response, which is disabled: yes host-deny local 6 600 yes firewall

Re: [ossec-list] segmentation fault

2012-12-17 Thread dan (ddp)
On Dec 17, 2012 4:37 PM, "Carrie Poole" wrote: > > I’m getting segmentation faults across all of my agents when restarting. Nothing is showing connected anymore. > > > > > > /var/ossec/bin/ossec-control: line 138: 24910 Segmentation fault ${DIR}/bin/${i} > > What's line 138 in ossec-control? Anyt

[ossec-list] Segmentation faults

2012-12-17 Thread carrie p
I’m getting segmentation faults across all of my agents when restarting. Nothing is showing connected anymore. /var/ossec/bin/ossec-control: line 138: 24910 Segmentation fault ${DIR}/bin/${i} Line 138 in ossec.conf is the active response, which is disabled:

[ossec-list] segmentation fault

2012-12-17 Thread Carrie Poole
I'm getting segmentation faults across all of my agents when restarting. Nothing is showing connected anymore. /var/ossec/bin/ossec-control: line 138: 24910 Segmentation fault ${DIR}/bin/${i} Line 138 in ossec.conf is the active response, which is disabled. I have checked the ossec.c

[ossec-list] web_rules.xml , is triggering alert , but we are not geting email

2012-12-17 Thread Dhinakaran G
Hi all, In web_rules.xml rule is triggering alert that are stored in the log , but not reaching our email notication , any idea. here the file: web-log Access log messages grouped. 31100 ^2|^3 is_simple_http_request Ignored URLs (simple quer

[ossec-list] Re: Rule Frequency problem

2012-12-17 Thread Kat
You should take a look at this patch: https://groups.google.com/forum/?fromgroups=#!search/accumulator/ossec-dev/NfQaFREyCHI/ycoRVq6YD_gJ On Thursday, December 13, 2012 8:21:51 AM UTC-8, Mike Hubbard wrote: > > Hello - > I am trying to construct a set of rules that cause a change in behavior if