Re: [netsnmp-coders] missing information in logmatch trap

2019-10-04 Thread Thommandra Gowtham
om> wrote: > >> Thank you Bill for your response. >> >> When you said that I have configured two separate features, can you >> explain? How else can we get a logmatch trap by just one directive? >> > > You currently can not. That is how I imagine the featu

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-29 Thread Bill Fenner
On Sat, Sep 28, 2019 at 10:14 AM Thommandra Gowtham wrote: > Thank you Bill for your response. > > When you said that I have configured two separate features, can you > explain? How else can we get a logmatch trap by just one directive? > You currently can not. That is how I imag

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-28 Thread Thommandra Gowtham
Thank you Bill for your response. When you said that I have configured two separate features, can you explain? How else can we get a logmatch trap by just one directive? For b), which part of the code has the actual string that is matched? I can probably use it to raise a trap if needed. I have

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-27 Thread Bill Fenner
Hi Gowtham, Please file your request at https://github.com/net-snmp/net-snmp/issues . The reason the info is not present in the trap is because you have configured two separate features: 1. count log file matches in the logMatch table - note that there is no place in this table for a list of

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-23 Thread Thommandra Gowtham
MatchFilename.1 = STRING: > /var/log/auth.log UCD-SNMP-MIB::logMatchCurrentCount.1 = INTEGER: 9 > UCD-SNMP-MIB::logMatchRegEx.1 = STRING: Failed password .* > > For the following config, > logmatch loginFailure /var/log/auth.log 30 Failed password for .* > and line in log fine as bel

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-06 Thread Thommandra Gowtham
teHotValue.0 = INTEGER: 9 UCD-SNMP-MIB::logMatchName.1 = STRING: loginFailure UCD-SNMP-MIB::logMatchFilename.1 = STRING: /var/log/auth.log UCD-SNMP-MIB::logMatchCurrentCount.1 = INTEGER: 9 UCD-SNMP-MIB::logMatchRegEx.1 = STRING: Failed password .* For the following config, logmatch loginFailur

Re: [netsnmp-coders] missing information in logmatch trap

2019-09-06 Thread Jeff Gehlbach
On 9/5/19 10:58 PM, Thommandra Gowtham wrote: > - How can we get more information in a logmatch trap other than the > pattern matched? Making your pattern match more text should do the trick. For example: logmatch loginFailure /var/log/auth.log 30 Failed password for .* BTW, this k

missing information in logmatch trap

2019-09-05 Thread Thommandra Gowtham
Hi I am using net-snmp 5.7.3 on Ubuntu and have a few questions regarding logmatch trap - How can we get more information in a logmatch trap other than the pattern matched? For example if we have below logmatch loginFailure /var/log/auth.log 30 Failed password monitor -r 10 -o logMatchName -o

Re: net-snmp dumps core when snmpd.conf contains an incorrect logmatch parameter regex

2014-04-16 Thread Mohan Gorai
lost? > > Thanks, > Bill > > > > On Tue, Mar 18, 2014 at 8:11 AM, Mohan Gorai <mailto:[email protected]>> wrote: > > Hi, > > On Solaris, whenever there is a wrong regex as logmatch parameter, > when the corresponding structures

Re: net-snmp dumps core when snmpd.conf contains an incorrect logmatch parameter regex

2014-04-09 Thread Bill Fenner
Hi Mohan, Thanks for the patch. Can you please upload it at http://www.net-snmp.org/patches/ so that it doesn't get lost? Thanks, Bill On Tue, Mar 18, 2014 at 8:11 AM, Mohan Gorai wrote: > Hi, > > On Solaris, whenever there is a wrong regex as logmatch parameter, when >

net-snmp dumps core when snmpd.conf contains an incorrect logmatch parameter regex

2014-04-08 Thread Mohan Gorai
Hi, On Solaris, whenever there is a wrong regex as logmatch parameter, when the corresponding structures are being de-allocated, snmpd coredumps. This is because we are freeing the structures using regfree(), even when the corresponding regcomp() returns with an error. The attached patch

Re: net-snmp dumps core when snmpd.conf contains an incorrect logmatch parameter regex

2014-04-08 Thread Mohan Gorai
The patch is against net-snmp 5.4.1 code. But, I can still see the issue on the latest code. If need be, I can provide the changes against the latest version. On March 18, 2014 05:41:46 PM IST, Mohan Gorai wrote: > Hi, > > On Solaris, whenever there is a wrong regex as logmatch

Re: logmatch

2006-07-10 Thread Dave Shield
Kevin Zhang wrote: > Anyone succeeded in using logmatch, I have tried different > configurations but failed. > As Wes said, repeating the same request several times in quick succession is not the best way to encourage a helpful response. We're all volunteers, supporting this

Re: logmatch

2006-07-07 Thread Wes Hardaker
> On Fri, 7 Jul 2006 11:46:49 -0700, "Kevin Zhang" <[EMAIL PROTECTED]> said: Kevin> again Sending notes once a day just really annoys people. Please don't do that. If someone can answer your question they will hopefully. -- Wes Hardaker Sparta, Inc. Using Tomcat but need to do more? Need

RE: logmatch

2006-07-07 Thread Kevin Zhang
again   From: Kevin Zhang Sent: Wednesday, July 05, 2006 12:22 PM To: '[email protected]' Subject: logmatch   Anyone succeeded in using logmatch, I have tried different configurations but failed.   Kevin SZ Using Tomcat but need to do

RE: logmatch

2006-07-06 Thread Kevin Zhang
Again, anyone can help me with logmatch?   Kevin SZ   From: Kevin Zhang Sent: Wednesday, July 05, 2006 12:22 PM To: '[email protected]' Subject: logmatch   Anyone succeeded in using logmatch, I have tried different configurations but failed.

logmatch

2006-07-05 Thread Kevin Zhang
Anyone succeeded in using logmatch, I have tried different configurations but failed.   Kevin SZ Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere

[BUG] LogMatch

2005-07-01 Thread Emmanuel Doguet
I have found a bug on net-snmp 5.2.1. On my debian, it's work very fine. But on a special Linux (Pitux distribution (glib-1.2.6-3 glibc-2.3.2-4.80.8tbs )), it's failed. It's return always the same value, sometime 0. I think it's a problem with value return of fseek. ** Modification I have

logmatch, it's great!

2005-06-17 Thread Emmanuel Doguet
I use logmatch, it's a great tools! But the "timer/frequency data" is use for what ? Since counter is reset when we call this OID ? smime.p7s Description: S/MIME Cryptographic Signature