Net SNMP not sending ifup trap

2021-07-27 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

We are using Netsnmp version: 5.7.2-37.el7 in one of our product, and looking 
for your assistance on below enquiry.

We have environment, where net snmp not sending clear trap when interface is 
come up.

Issue is seen even if we are doing simple operations like below:
ifup eth2
ifup eth2

Clear Trap is noticed intermittently,  but 99% of the time, it's not sending 
clear trap when interface comes up.

Please let us know if there is any known issue on this in 5.7.2-37.el7  and any 
possible workaround for the same.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

snmpwalk fails post upgrade to CentOS 8

2020-08-18 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

We are facing the following issue on Centos 8  while trying to perform 
snmpwalk using the following command

$ snmpwalk -On -e 0x0102030405060708 -v 3 -u myuser -a SHA -A mypassword -x AES 
-l authNoPriv -M +BROADHOP-MIB:PRODUCT-FILE-MIB vm01 
.1.3.6.1.4.1.26878.200.3.2.70
   .1.3.6.1.4.1.26878.200.3.2.70 = No Such Object available on this agent at 
this OID

Below is the rpm used for Centos 8
[root@vm01 ~]# rpm -qa | grep net-snmp
net-snmp-5.8-12.el8_1.1.x86_64
net-snmp-libs-5.8-12.el8_1.1.x86_64
net-snmp-utils-5.8-12.el8_1.1.x86_64
net-snmp-agent-libs-5.8-12.el8_1.1.x86_64

However on our Centos 6 and 7 enviornment, the same command is working fine and 
following is the output
$ snmpwalk -On -e 0x0102030405060708 -v 3 -u myuser -a SHA -A mypassword -x AES 
-l authNoPriv -M +BROADHOP-MIB:PRODUCT-FILE-MIB vm01 
.1.3.6.1.4.1.26878.200.3.2.70
.1.3.6.1.4.1.26878.200.3.2.70.1.4 = INTEGER: 12
.1.3.6.1.4.1.26878.200.3.2.70.1.4.0 = INTEGER: 12
.1.3.6.1.4.1.26878.200.3.2.70.1.5 = INTEGER: 5
.1.3.6.1.4.1.26878.200.3.2.70.1.5.0 = INTEGER: 5
.1.3.6.1.4.1.26878.200.3.2.70.1.6 = INTEGER: 1
.1.3.6.1.4.1.26878.200.3.2.70.1.6.0 = INTEGER: 1
.1.3.6.1.4.1.26878.200.3.2.70.1.7 = INTEGER: 8061096
.1.3.6.1.4.1.26878.200.3.2.70.1.7.0 = INTEGER: 8061096
.1.3.6.1.4.1.26878.200.3.2.70.1.8 = INTEGER: 1775736
.1.3.6.1.4.1.26878.200.3.2.70.1.8.0 = INTEGER: 1775736
.1.3.6.1.4.1.26878.200.3.2.70.1.9 = INTEGER: 4194300
.1.3.6.1.4.1.26878.200.3.2.70.1.9.0 = INTEGER: 4194300
.1.3.6.1.4.1.26878.200.3.2.70.1.10 = INTEGER: 4194300
.1.3.6.1.4.1.26878.200.3.2.70.1.10.0 = INTEGER: 4194300

Below is the rpm used for Centos 6
[root@ vm01 ~]# rpm -qa | grep net-snmp
net-snmp-libs-5.5-57.el6_8.1.x86_64
net-snmp-5.5-57.el6_8.1.x86_64
net-snmp-utils-5.5-57.el6_8.1.x86_64


Below is the snmpd.conf file used for Centos 8. We are using private mibs and 
trying to fetch the respective details

rouser myuser
rouser myuser_trap
com2sec local localhost   myuser
com2sec6 local localhost   myuser
group MyRWGroup usmlocal
group MyRWGroup usmmyuser
view allincluded  .1   80
access MyRWGroup ""  any   noauthexact  allallnone
syslocation Unknown (edit /etc/snmp/snmpd.conf)
syscontact Root  (configure /etc/snmp/snmp.local.conf)
master agentx
agentAddress udp:161,udp6:161


agentSecName myuser_trap

trapsess -v 3 -u myuser_trap -a SHA -m 
0x7aed7094e8d5eaf303a4dff14406367ba52b3757 -x AES -m 
0x7aed7094e8d5eaf303a4dff14406367b -l authPriv vip02


##
#
# Local Stats
#
ignoreDisk /proc
ignoreDisk /proc/sys/fs/binfmt_misc
ignoreDisk /var/lib/nfs/rpc_pipefs
ignoreDisk /dev/shm
ignoreDisk /dev/pts
disk / 10%


swap 102400

load 9 9 9

#linkUpDownNotifications yes

notificationEvent  linkUpTraplinkUp   ifIndex ifAdminStatus ifOperStatus
notificationEvent  linkDownTrap  linkDown ifIndex ifAdminStatus ifOperStatus



monitor  -u myuser_trap -r 60 -e linkUpTrap -o ifDescr  "Generate linkUp" 
ifOperStatus != 2
monitor  -u myuser_trap -r 60 -e linkDownTrap -o ifDescr "Generate linkDown" 
ifOperStatus == 2

# Note: alert!=0, clear==0 and messages must be unique or snmpd errors.
monitor -u myuser_trap -r 60 -o dskPath -o dskErrorMsg "DiskFullAlert" 
dskErrorFlag != 0
monitor -u myuser_trap -r 60 -o dskPath -o dskErrorMsg "DiskFullClear" 
dskErrorFlag == 0
monitor -u myuser_trap -r 60 -o memErrorName -o memSwapErrorMsg "LowSwapAlert" 
memSwapError != 0
monitor -u myuser_trap -r 60 -o memErrorName -o memSwapErrorMsg "LowSwapClear" 
memSwapError == 0
monitor -u myuser_trap -r 60 -o laNames -o laErrMessage  "HighLoadAlert" 
laErrorFlag != 0
monitor -u myuser_trap -r 60 -o laNames -o laErrMessage  "HighLoadClear" 
laErrorFlag == 0


##
#
# System Stats
#

# User, System and Idle CPU (VM-SNMP-MIB ss)
proxy -e 0x0102030405060708 -v 3 -u myuser -a SHA -m 
0x71d8d544a7447e377fa5fc355d8f08f81f1a901c -x AES -m 
0x71d8d544a7447e377fa5fc355d8f08f8 -l authPriv localhost 
.1.3.6.1.4.1.26878.200.3.2.70.1.1.0  .1.3.6.1.4.1.2021.11.9.0
proxy -e 0x0102030405060708 -v 3 -u myuser -a SHA -m 
0x71d8d544a7447e377fa5fc355d8f08f81f1a901c -x AES -m 
0x71d8d544a7447e377fa5fc355d8f08f8 -l authPriv localhost 
.1.3.6.1.4.1.26878.200.3.2.70.1.2.0  .1.3.6.1.4.1.2021.11.10.0
proxy -e 0x0102030405060708 -v 3 -u myuser -a SHA -m 
0x71d8d544a7447e377fa5fc355d8f08f81f1a901c -x AES -m 
0x71d8d544a7447e377fa5fc355d8f08f8 -l authPriv localhost 
.1.3.6.1.4.1.26878.200.3.2.70.1.3.0  .1.3.6.1.4.1.2021.11.11.0
proxy -e 0x0102030405060708 -v 3 -u myuser -a SHA -m 
0x71d8d544a7447e377fa5fc355d8f08f81f1a901c -x AES -m 
0x71d8d544a7447e377fa5fc355d8f08f8 -l authPriv localhost 
.1.3.6.1.4.1.26878.200.3.2.70.1.1  .1.3.6.1.4.1.2021.11.9.0
proxy -e 0x0102030405060708 -v 3 -u myuser -a SHA -m 
0x71d8d544a7447e377fa5fc355d8f08f81f1a901c -x AES -m 
0x71d8d544a7447e377fa5fc355d8f08f8 -l authPriv localhost 
.1.3.6.1.4.1.26878.200.3.2.70.1.2  .1.3.6.1.4.1.2021.11.10.0
proxy -e 0x0102030405060708 -v 3 -u myus

RE: Crash at Net-snmp due to corrupted double-linked list

2019-11-18 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you please shed some light on this.

Our Dev engineer had analyzed the cores files using the unstripped snmpd binary.
>From the core analysis, we can see both the crashes happened due to memory 
>corruption in snmp.

Attached the core backtrace logs for reference. Could you please help in this 
regard.

CORE1:

/net-snmp/5.7.3-r5.0/net-snmp-5.7.3/agent/mibgroup/ip-mib/data_access/systemstats_linux.c
/*
 * try to open /proc/net/dev_snmp6 directory. If we can't, that' ok -
 * maybe it is not supported by the current running kernel.
 */
if ((dev_snmp6_dir = opendir(DEV_SNMP6_DIRNAME)) == NULL) {<<< opendir 
uses malloc(0 to allocate memory and it is crashing
DEBUGMSGTL(("access:ifstats",
"Failed to load IPv6 IfStats Table (linux)\n"));
return 0;
}


CORE2:

/net-snmp/5.7.3-r5.0/net-snmp-5.7.3/snmplib/snmp_api.c

/*
* snmp_duplicate_objid: duplicates (mallocs) an objid based on the
* input objid
*/
oid*
snmp_duplicate_objid(const oid * objToCopy, size_t objToCopyLen)
{
oid*returnOid;
if (objToCopy != NULL && objToCopyLen != 0) {
returnOid = (oid *) malloc(objToCopyLen * sizeof(oid)); 
<<< Failing in malloc corruption
if (returnOid) {
memcpy(returnOid, objToCopy, objToCopyLen * sizeof(oid));
}
} else
returnOid = NULL;
return returnOid;
}

Thanks,
Kiran

From: Kiran Kumar Pamula
Sent: 12 November 2019 14:23
To: 
net-snmp-users@lists.sourceforge.net
Subject: Crash at Net-snmp due to corrupted double-linked list

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any known issue and if a patch is available 
for the same.

[New LWP 31070]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 31070
selftid = 31070
#1 0x7fc49e728418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffdf25156ea, sa_sigaction = 
0x7ffdf25156ea}, sa_mask = {__val = {6, 140482449860288, 2, 140728668870398, 2, 
140482449851372, 1, 140482449860284, 3, 140728668870372, 12, 140482449860288, 
2, 140728668871184, 15, 140728668872944}}, sa_flags = 93, sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2 0x7fc49e764e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fc49e8588a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3 0x7fc49e76a9be in malloc_printerr (ptr=, 
str=0x7fc49e855129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "009cf690"
cp = 
#4 malloc_printerr (action=3, str=0x7fc49e855129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5 0x7fc49e76abc3 in malloc_consolidate (av=av@entry=0x7fc49ea93660 
) at malloc.c:4078
fb = 
maxfb = 0x7fc49ea936b0 
p = 0x9cf690
nextp = 0x9cd1d0
unsorted_bin = 0x7fc49ea936b8 
first_unsorted = 
nextchunk = 0x9cf8d0
size = 576
nextsize = 128
prevsize = 
nextinuse = 
bck = 
fwd = 
#6 0x7fc49e76cb78 in _int_malloc (av=0x7fc49ea93660 , 
bytes=32816) at malloc.c:3374
nb = 32832
idx = 
bin = 
victim = 
size = 
victim_index = 
remainder = 
remainder_size = 
block = 
bit = 
map = 
fwd = 
bck = 
errstr = 0x0
__func__ = "_int_malloc"
#7 0x7fc49e76e1ac in __GI___libc_malloc (bytes=32816) at malloc.c:2874
ar_ptr = 0x7fc49ea93660 
victim = 0x6
__func__ = "__libc_malloc"
#8 0x7fc49e7a5caa in __alloc_dir (fd=14, close_fd=, 
flags=, statp=) at ../sysdeps/unix/opendir.c:199
default_allocation = 32768
small_allocation = 8192
allocation = 32768
dirp = 
#9 0x7fc4a0018666 in ?? () from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#10 0x7fc4a0018a00 in netsnmp_access_systemstats_container_arch_load () 
from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#11 0x7fc4a0015ec7 in netsnmp_access_systemstats_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#12 0x7fc49ffeeabe in ipIfStatsTable_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#13 0x7fc4a03d6100 i

RE: Crash at Net-snmp due to corrupted double-linked list

2019-11-12 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Net-snmp team,

Our Dev engineer had analyzed the cores files using the unstripped snmpd binary.
>From the core analysis, we can see both the crashes happened due to memory 
>corruption in snmp.

Attached the core backtrace logs for reference. Could you please help in this 
regard.

CORE1:

/net-snmp/5.7.3-r5.0/net-snmp-5.7.3/agent/mibgroup/ip-mib/data_access/systemstats_linux.c
/*
 * try to open /proc/net/dev_snmp6 directory. If we can't, that' ok -
 * maybe it is not supported by the current running kernel.
 */
if ((dev_snmp6_dir = opendir(DEV_SNMP6_DIRNAME)) == NULL) {<<< opendir 
uses malloc(0 to allocate memory and it is crashing
DEBUGMSGTL(("access:ifstats",
"Failed to load IPv6 IfStats Table (linux)\n"));
return 0;
}


CORE2:

/net-snmp/5.7.3-r5.0/net-snmp-5.7.3/snmplib/snmp_api.c

/*
* snmp_duplicate_objid: duplicates (mallocs) an objid based on the
* input objid
*/
oid*
snmp_duplicate_objid(const oid * objToCopy, size_t objToCopyLen)
{
oid*returnOid;
if (objToCopy != NULL && objToCopyLen != 0) {
returnOid = (oid *) malloc(objToCopyLen * sizeof(oid)); 
<<< Failing in malloc corruption
if (returnOid) {
memcpy(returnOid, objToCopy, objToCopyLen * sizeof(oid));
}
} else
returnOid = NULL;
return returnOid;
}

Thanks,
Kiran

From: Kiran Kumar Pamula
Sent: 12 November 2019 14:23
To: net-snmp-users@lists.sourceforge.net
Subject: Crash at Net-snmp due to corrupted double-linked list

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any known issue and if a patch is available 
for the same.

[New LWP 31070]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 31070
selftid = 31070
#1 0x7fc49e728418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffdf25156ea, sa_sigaction = 
0x7ffdf25156ea}, sa_mask = {__val = {6, 140482449860288, 2, 140728668870398, 2, 
140482449851372, 1, 140482449860284, 3, 140728668870372, 12, 140482449860288, 
2, 140728668871184, 15, 140728668872944}}, sa_flags = 93, sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2 0x7fc49e764e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fc49e8588a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3 0x7fc49e76a9be in malloc_printerr (ptr=, 
str=0x7fc49e855129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "009cf690"
cp = 
#4 malloc_printerr (action=3, str=0x7fc49e855129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5 0x7fc49e76abc3 in malloc_consolidate (av=av@entry=0x7fc49ea93660 
) at malloc.c:4078
fb = 
maxfb = 0x7fc49ea936b0 
p = 0x9cf690
nextp = 0x9cd1d0
unsorted_bin = 0x7fc49ea936b8 
first_unsorted = 
nextchunk = 0x9cf8d0
size = 576
nextsize = 128
prevsize = 
nextinuse = 
bck = 
fwd = 
#6 0x7fc49e76cb78 in _int_malloc (av=0x7fc49ea93660 , 
bytes=32816) at malloc.c:3374
nb = 32832
idx = 
bin = 
victim = 
size = 
victim_index = 
remainder = 
remainder_size = 
block = 
bit = 
map = 
fwd = 
bck = 
errstr = 0x0
__func__ = "_int_malloc"
#7 0x7fc49e76e1ac in __GI___libc_malloc (bytes=32816) at malloc.c:2874
ar_ptr = 0x7fc49ea93660 
victim = 0x6
__func__ = "__libc_malloc"
#8 0x7fc49e7a5caa in __alloc_dir (fd=14, close_fd=, 
flags=, statp=) at ../sysdeps/unix/opendir.c:199
default_allocation = 32768
small_allocation = 8192
allocation = 32768
dirp = 
#9 0x7fc4a0018666 in ?? () from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#10 0x7fc4a0018a00 in netsnmp_access_systemstats_container_arch_load () 
from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#11 0x7fc4a0015ec7 in netsnmp_access_systemstats_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#12 0x7fc49ffeeabe in ipIfStatsTable_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#13 0x7fc4a03d6100 in ?? () from /usr/lib64/libnetsnmpagent.so.30
No symbol table info available.
#14 0

Crash at Net-snmp due to corrupted double-linked list

2019-11-12 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any known issue and if a patch is available 
for the same.

[New LWP 31070]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0 0x7fc49e726f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 31070
selftid = 31070
#1 0x7fc49e728418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffdf25156ea, sa_sigaction = 
0x7ffdf25156ea}, sa_mask = {__val = {6, 140482449860288, 2, 140728668870398, 2, 
140482449851372, 1, 140482449860284, 3, 140728668870372, 12, 140482449860288, 
2, 140728668871184, 15, 140728668872944}}, sa_flags = 93, sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2 0x7fc49e764e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fc49e8588a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdf2516100, 
reg_save_area = 0x7ffdf2516010}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3 0x7fc49e76a9be in malloc_printerr (ptr=, 
str=0x7fc49e855129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "009cf690"
cp = 
#4 malloc_printerr (action=3, str=0x7fc49e855129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5 0x7fc49e76abc3 in malloc_consolidate (av=av@entry=0x7fc49ea93660 
) at malloc.c:4078
fb = 
maxfb = 0x7fc49ea936b0 
p = 0x9cf690
nextp = 0x9cd1d0
unsorted_bin = 0x7fc49ea936b8 
first_unsorted = 
nextchunk = 0x9cf8d0
size = 576
nextsize = 128
prevsize = 
nextinuse = 
bck = 
fwd = 
#6 0x7fc49e76cb78 in _int_malloc (av=0x7fc49ea93660 , 
bytes=32816) at malloc.c:3374
nb = 32832
idx = 
bin = 
victim = 
size = 
victim_index = 
remainder = 
remainder_size = 
block = 
bit = 
map = 
fwd = 
bck = 
errstr = 0x0
__func__ = "_int_malloc"
#7 0x7fc49e76e1ac in __GI___libc_malloc (bytes=32816) at malloc.c:2874
ar_ptr = 0x7fc49ea93660 
victim = 0x6
__func__ = "__libc_malloc"
#8 0x7fc49e7a5caa in __alloc_dir (fd=14, close_fd=, 
flags=, statp=) at ../sysdeps/unix/opendir.c:199
default_allocation = 32768
small_allocation = 8192
allocation = 32768
dirp = 
#9 0x7fc4a0018666 in ?? () from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#10 0x7fc4a0018a00 in netsnmp_access_systemstats_container_arch_load () 
from /usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#11 0x7fc4a0015ec7 in netsnmp_access_systemstats_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#12 0x7fc49ffeeabe in ipIfStatsTable_container_load () from 
/usr/lib64/libnetsnmpmibs.so.30
No symbol table info available.
#13 0x7fc4a03d6100 in ?? () from /usr/lib64/libnetsnmpagent.so.30
No symbol table info available.
#14 0x7fc49fcd0357 in run_alarms () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#15 0x00403d85 in ?? ()
No symbol table info available.
#16 0x7fc49e713865 in __libc_start_main (main=0x4028f0, argc=20, 
ubp_av=0x7ffdf2516b88, init=, fini=, 
rtld_fini=, stack_end=0x7ffdf2516b78) at libc-start.c:274
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -764479061368474344, 4212360, 
140728668875648, 0, 0, 765580028292920600, 787350082089547032}, mask_was_saved 
= 0}}, priv = {pad = {0x0, 0x0, 0x404950, 0x7ffdf2516b88}, data = {prev = 0x0, 
cleanup = 0x0, canceltype = 4213072}}}
not_first_call = 
#17 0x004046b1 in ?? ()
No symbol table info available.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Some general questions on netsnmp_logging_restart

2019-09-09 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you please help me with below questions in the below part of net-snmp 
code:

File: 
net-snmp/5.7.3-r5.0/net-snmp-5.7.3/agent/snmpd.c

1199  static int
1200  receive(void)
1201  {
..
..
1233  snmp_log(LOG_INFO, "Reconfiguring daemon\n");
1234  /*  Stop and restart logging.  This allows logfiles to be
1235  rotated etc.  */
1236  netsnmp_logging_restart();
1237  snmp_log(LOG_INFO, "NET-SNMP version %s restarted\n",
1238   netsnmp_get_version());
1239  update_config();
1240  send_easy_trap(SNMP_TRAP_ENTERPRISESPECIFIC, 3);
..
..
}

  1.  In line 1237, log points to "NET-SNMP version 5.7.3 restarted", but in 
actual, it is net-snmp logger that gets restarted here.

Hence the above message needs to be changed accordingly so that it doesn't 
annoy customers !!

Am I right ?



  1.  In line 1240, why a trap is being sent just for a snmp logging restart ?

Is this trap really need here as snmp process is not actually getting restarted 
?

Can this line be commented out ? And what is the impact if so.

Kindly let me know.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Some general questions on netsnmp_logging_restart

2019-09-05 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Sorry .. I wrongly copied code in my earlier email.

Please find plain text below.

1199  static int
1200  receive(void)
1201  {
..
..
1233  snmp_log(LOG_INFO, "Reconfiguring daemon\n");
1234  /*  Stop and restart logging.  This allows logfiles to be
1235  rotated etc.  */
1236  netsnmp_logging_restart();
1237  snmp_log(LOG_INFO, "NET-SNMP version %s restarted\n",
1238   netsnmp_get_version());
1239  update_config();
1240  send_easy_trap(SNMP_TRAP_ENTERPRISESPECIFIC, 3);
..
..
}

In the above piece of code:


  1.  In line 1237, log points to "NET-SNMP version 5.7.3 restarted", but in 
actual, it is net-snmp logger that gets restarted here.

Hence the above message needs to be changed accordingly so that it doesn't 
annoy customers !!

Am I right ?



  1.  In line 1240, why a trap is being sent just for a snmp logging restart ?

Is this trap really need here as snmp process is not actually getting restarted 
?

Can this line be commented out ? And what is the impact if so.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 05 September 2019 17:04
To: net-snmp-users@lists.sourceforge.net
Cc: Naresh Pindukuru -X (narpindu - HCL TECHNOLOGIES LIMITED at Cisco) 
; Appandainathan Ayyannan -X (aayyanna - HCL TECHNOLOGIES 
LIMITED at Cisco) 
Subject: Some general questions on netsnmp_logging_restart

Hi Experts,

Could you please help me with below questions:

File: 
net-snmp/5.7.3-r5.0/net-snmp-5.7.3/agent/snmpd.c


1232 

  
reconfig
 = 0;

1233 

  
snmp_log(LOG_INFO,
 "Reconfiguring daemon\n");

1234 

/*  Stop and restart logging.  This allows logfiles to be

1235 

   rotated etc.  */

1236 


netsnmp_logging_restart();

1237 


snmp_log(LOG_INFO,
 "NET-SNMP version %s restarted\n",

1238 


netsnmp_get_version());

1239 

  
update_config();

1240 

  
send_easy_trap(SNMP_TRAP_ENTERPRISESPECIFIC,
 3);

In the above piece of code:


  1.  In line 1237, log points to "NET-SNMP version 5.7.3 restarted", but in 
actual, it is net-snmp logger that gets restarted here.

Hence the above message needs to be changed accordingly so that it doesn't 
annoy customers

Some general questions on netsnmp_logging_restart

2019-09-05 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you please help me with below questions:

File: 
net-snmp/5.7.3-r5.0/net-snmp-5.7.3/agent/snmpd.c


1232 

  
reconfig
 = 0;

1233 

  
snmp_log(LOG_INFO,
 "Reconfiguring daemon\n");

1234 

/*  Stop and restart logging.  This allows logfiles to be

1235 

   rotated etc.  */

1236 


netsnmp_logging_restart();

1237 


snmp_log(LOG_INFO,
 "NET-SNMP version %s restarted\n",

1238 


netsnmp_get_version());

1239 

  
update_config();

1240 

  
send_easy_trap(SNMP_TRAP_ENTERPRISESPECIFIC,
 3);

In the above piece of code:


  1.  In line 1237, log points to "NET-SNMP version 5.7.3 restarted", but in 
actual, it is net-snmp logger that gets restarted here.

Hence the above message needs to be changed accordingly so that it doesn't 
annoy customers !!

Am I right ?



  1.  In line 1240, why a trap is being sent just for a snmp logging restart ?

Is this trap really need here as snmp process is not actually getting restarted 
?

Can this line be commented out ? And what is the impact if so.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

2019-05-21 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Bart,

Thanks for your response.

Unfortunately Valgrind doesn't work on our product, due to memory limitations.

By generating backtraces with the help of unstripped binary, , we can see the 
crash happened due to calling snmp_free_pdu() twice
which then calls snmp_free_varbind () function and makes snmp pdu->variables 
pointer getting freed twice.

>From the logs, there are no logs for request for SNMP trap sent . The  crash 
>happened when snmpd service is started.

#4  malloc_printerr (action=3, str=0x7f22b2d43129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
#5  0x7f22b2c58c08 in malloc_consolidate (av=av@entry=0x7f22b2f81660 
) at malloc.c:4086
#6  0x7f22b2c59b18 in _int_free (av=0x7f22b2f81660 , 
p=0x18730a0, have_lock=0, trim=1) at malloc.c:3977
#7  0x7f22b4192cd8 in snmp_free_pdu () from /usr/lib64/libnetsnmp.so.30
#8  0x7f22b4192d24 in snmp_free_pdu () from /usr/lib64/libnetsnmp.so.30
#9  0x7f22b41938f5 in snmp_sess_close () from /usr/lib64/libnetsnmp.so.30
#10 0x7f22b4194c2f in snmp_sess_select_info2_flags () from 
/usr/lib64/libnetsnmp.so.30

We are thinking of a defensive fix below to assign the pdu->variables to NULL 
once after calling snmp_free_varbind(), which will avoid the crash if 
snmp_free_pdu() is called twice.

Index: net-snmp-5.7.3/snmplib/snmp_api.c
===
--- net-snmp-5.7.3.orig/snmplib/snmp_api.c
+++ net-snmp-5.7.3/snmplib/snmp_api.c
@@ -5138,6 +5138,7 @@ snmp_free_pdu(netsnmp_pdu *pdu)
 (*sptr->pdu_free) (pdu);
 }
 snmp_free_varbind(pdu->variables);
+pdu->variables = NULL;
 SNMP_FREE(pdu->enterprise);
 SNMP_FREE(pdu->community);
 SNMP_FREE(pdu->contextEngineID);

Please let us know if this sounds fine (or) if you think this will have any 
further implications.
We see the subsequent macro "SNMP_FREE" is also setting the variable to NULL, 
after freeing, which is missing in case of pdu->variables.

/** @def SNMP_FREE(s)
Frees a pointer only if it is !NULL and sets its value to NULL */
#define SNMP_FREE(s)do { if (s) { free((void *)s); s=NULL; } } while(0)

Thanks,
Kiran

From: Bart Van Assche 
Sent: 16 May 2019 16:27
To: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) 
; net-snmp-users@lists.sourceforge.net
Subject: Re: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Kiran,

I think Valgrind is the right tool to identify the root cause of this crash. 
What is not clear to me and what has not been mentioned in any of your e-mails 
is whether or not any custom MIB implementations (code from outside the 
Net-SNMP source code tree) had been loaded into the snmpd process. There are no 
known memory corruptions in the Net-SNMP code base so this memory corruption is 
probably caused by a custom MIB implementation.

Bart.

On 5/16/19 11:17 AM, Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED 
at Cisco) via Net-snmp-users wrote:
Could you kindly share your inputs on this.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 12 May 2019 12:43
To: 
'net-snmp-users@lists.sourceforge.net<mailto:net-snmp-users@lists.sourceforge.net>'
 
<mailto:net-snmp-users@lists.sourceforge.net>
Subject: RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Team,

Could you please comment on this, in case if this is any known issue.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 09 May 2019 11:48
To: 
'net-snmp-users@lists.sourceforge.net<mailto:net-snmp-users@lists.sourceforge.net>'
 
mailto:net-snmp-users@lists.sourceforge.net>>
Cc: Saravanan Adhikesavan -X (sadhikes - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:sadhi...@cisco.com>>; Naresh Pindukuru -X (narpindu 
- HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>; Thivya Radjendirane -X 
(tradjend - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:tradj...@cisco.com>>; Apparao Podile -X (apodile - 
HCL TECHNOLOGIES LIMITED at Cisco) mailto:apod...@cisco.com>>
Subject: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any know issue and if a patch is available 
for the same.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 6103

RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

2019-05-16 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Thanks Bart for your response.

Let me check this internally.

BTW here is the command used by our customer that triggered the problem, but we 
didn't hit the same problem in our local repro efforts in spite of multiple 
attempts.

Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.

Thanks,
Kiran

From: Bart Van Assche 
Sent: 16 May 2019 16:27
To: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) 
; net-snmp-users@lists.sourceforge.net
Subject: Re: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Kiran,

I think Valgrind is the right tool to identify the root cause of this crash. 
What is not clear to me and what has not been mentioned in any of your e-mails 
is whether or not any custom MIB implementations (code from outside the 
Net-SNMP source code tree) had been loaded into the snmpd process. There are no 
known memory corruptions in the Net-SNMP code base so this memory corruption is 
probably caused by a custom MIB implementation.

Bart.

On 5/16/19 11:17 AM, Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED 
at Cisco) via Net-snmp-users wrote:
Could you kindly share your inputs on this.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 12 May 2019 12:43
To: 
'net-snmp-users@lists.sourceforge.net<mailto:net-snmp-users@lists.sourceforge.net>'
 
<mailto:net-snmp-users@lists.sourceforge.net>
Subject: RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Team,

Could you please comment on this, in case if this is any known issue.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 09 May 2019 11:48
To: 
'net-snmp-users@lists.sourceforge.net<mailto:net-snmp-users@lists.sourceforge.net>'
 
mailto:net-snmp-users@lists.sourceforge.net>>
Cc: Saravanan Adhikesavan -X (sadhikes - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:sadhi...@cisco.com>>; Naresh Pindukuru -X (narpindu 
- HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>; Thivya Radjendirane -X 
(tradjend - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:tradj...@cisco.com>>; Apparao Podile -X (apodile - 
HCL TECHNOLOGIES LIMITED at Cisco) mailto:apod...@cisco.com>>
Subject: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any know issue and if a patch is available 
for the same.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 6103
selftid = 6103
#1  0x7f22b2c16418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffd12ecebca, sa_sigaction 
= 0x7ffd12ecebca}, sa_mask = {__val = {6, 139787005871808, 2, 140724920970206, 
2, 139787005862892, 1, 139787005871804, 3, 140724920970180, 12, 
139787005871808, 2, 140724920970992, 11, 140724920972752}}, sa_flags = 93, 
sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2  0x7f22b2c52e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f22b2d468a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7f22b2c589be in malloc_printerr (ptr=, 
str=0x7f22b2d43129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "01806d00"
cp = 
#4  malloc_printerr (action=3, str=0x7f22b2d43129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5  0x7f22b2c58c08 in malloc_consolidate (av=av@entry=0x7f22b2f81660 
) at malloc.c:4086
fb = 
maxfb = 0x7f22b2f816b0 
p = 0x1806b30
nextp = 0x0
unsorted_bin = 0x7f22b2f816b8 
first_unsorted = 
nextchunk = 0x1806d00
size = 512
nextsize = 
prevsize = 
nextinuse = 
bck = 
fwd = 0x7f22b2f816d8 
#6  0x7f22b2c59b18 in _int_free (av=0x7f22b2f81660 , 
p=0x18730a0, have_lock=0, trim=1) at malloc.c:3977
size = 96160
fb = 
nextc

RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

2019-05-16 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Could you kindly share your inputs on this.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 12 May 2019 12:43
To: 'net-snmp-users@lists.sourceforge.net' 

Subject: RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Team,

Could you please comment on this, in case if this is any known issue.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 09 May 2019 11:48
To: 'net-snmp-users@lists.sourceforge.net' 
mailto:net-snmp-users@lists.sourceforge.net>>
Cc: Saravanan Adhikesavan -X (sadhikes - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:sadhi...@cisco.com>>; Naresh Pindukuru -X (narpindu 
- HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>; Thivya Radjendirane -X 
(tradjend - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:tradj...@cisco.com>>; Apparao Podile -X (apodile - 
HCL TECHNOLOGIES LIMITED at Cisco) mailto:apod...@cisco.com>>
Subject: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any know issue and if a patch is available 
for the same.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 6103
selftid = 6103
#1  0x7f22b2c16418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffd12ecebca, sa_sigaction 
= 0x7ffd12ecebca}, sa_mask = {__val = {6, 139787005871808, 2, 140724920970206, 
2, 139787005862892, 1, 139787005871804, 3, 140724920970180, 12, 
139787005871808, 2, 140724920970992, 11, 140724920972752}}, sa_flags = 93, 
sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2  0x7f22b2c52e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f22b2d468a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7f22b2c589be in malloc_printerr (ptr=, 
str=0x7f22b2d43129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "01806d00"
cp = 
#4  malloc_printerr (action=3, str=0x7f22b2d43129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5  0x7f22b2c58c08 in malloc_consolidate (av=av@entry=0x7f22b2f81660 
) at malloc.c:4086
fb = 
maxfb = 0x7f22b2f816b0 
p = 0x1806b30
nextp = 0x0
unsorted_bin = 0x7f22b2f816b8 
first_unsorted = 
nextchunk = 0x1806d00
size = 512
nextsize = 
prevsize = 
nextinuse = 
bck = 
fwd = 0x7f22b2f816d8 
#6  0x7f22b2c59b18 in _int_free (av=0x7f22b2f81660 , 
p=0x18730a0, have_lock=0, trim=1) at malloc.c:3977
size = 96160
fb = 
nextchunk = 0x18739a0
nextsize = 93856
nextinuse = 
prevsize = 
bck = 
fwd = 
errstr = 0x0
locked = 1
__func__ = "_int_free"
#7  0x7f22b4192cd8 in snmp_free_varbind () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#8  0x7f22b4192d24 in snmp_free_pdu () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#9  0x7f22b41938f5 in snmp_sess_close () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#10 0x7f22b4194c2f in snmp_sess_select_info2_flags () from 
/usr/lib64/libnetsnmp.so.30
No symbol table info available.
#11 0x00403c9a in ?? ()
No symbol table info available.
#12 0x7f22b2c01865 in __libc_start_main (main=0x4028f0, argc=20, 
ubp_av=0x7ffd12ecfb88, init=, fini=, 
rtld_fini=, stack_end=0x7ffd12ecfb78) at libc-start.c:274
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4240236755570019627, 
4212360, 140724920974208, 0, 0, -4241690438631797461, -4279196600293372629}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x404950, 0x7ffd12ecfb88}, data 
= {prev = 0x0, cleanup = 0x0, canceltype = 4213072}}}
not_first_call = 
#13 0x004046b1 in ?? ()
No symbol table info available.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to un

RE: Crash at snmp_free_varbind with Net-snmp 5.7.3

2019-05-12 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Team,

Could you please comment on this, in case if this is any known issue.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 09 May 2019 11:48
To: 'net-snmp-users@lists.sourceforge.net' 

Cc: Saravanan Adhikesavan -X (sadhikes - HCL TECHNOLOGIES LIMITED at Cisco) 
; Naresh Pindukuru -X (narpindu - HCL TECHNOLOGIES LIMITED 
at Cisco) ; Thivya Radjendirane -X (tradjend - HCL 
TECHNOLOGIES LIMITED at Cisco) ; Apparao Podile -X (apodile 
- HCL TECHNOLOGIES LIMITED at Cisco) 
Subject: Crash at snmp_free_varbind with Net-snmp 5.7.3

Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any know issue and if a patch is available 
for the same.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 6103
selftid = 6103
#1  0x7f22b2c16418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffd12ecebca, sa_sigaction 
= 0x7ffd12ecebca}, sa_mask = {__val = {6, 139787005871808, 2, 140724920970206, 
2, 139787005862892, 1, 139787005871804, 3, 140724920970180, 12, 
139787005871808, 2, 140724920970992, 11, 140724920972752}}, sa_flags = 93, 
sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2  0x7f22b2c52e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f22b2d468a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7f22b2c589be in malloc_printerr (ptr=, 
str=0x7f22b2d43129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "01806d00"
cp = 
#4  malloc_printerr (action=3, str=0x7f22b2d43129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5  0x7f22b2c58c08 in malloc_consolidate (av=av@entry=0x7f22b2f81660 
) at malloc.c:4086
fb = 
maxfb = 0x7f22b2f816b0 
p = 0x1806b30
nextp = 0x0
unsorted_bin = 0x7f22b2f816b8 
first_unsorted = 
nextchunk = 0x1806d00
size = 512
nextsize = 
prevsize = 
nextinuse = 
bck = 
fwd = 0x7f22b2f816d8 
#6  0x7f22b2c59b18 in _int_free (av=0x7f22b2f81660 , 
p=0x18730a0, have_lock=0, trim=1) at malloc.c:3977
size = 96160
fb = 
nextchunk = 0x18739a0
nextsize = 93856
nextinuse = 
prevsize = 
bck = 
fwd = 
errstr = 0x0
locked = 1
__func__ = "_int_free"
#7  0x7f22b4192cd8 in snmp_free_varbind () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#8  0x7f22b4192d24 in snmp_free_pdu () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#9  0x7f22b41938f5 in snmp_sess_close () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#10 0x7f22b4194c2f in snmp_sess_select_info2_flags () from 
/usr/lib64/libnetsnmp.so.30
No symbol table info available.
#11 0x00403c9a in ?? ()
No symbol table info available.
#12 0x7f22b2c01865 in __libc_start_main (main=0x4028f0, argc=20, 
ubp_av=0x7ffd12ecfb88, init=, fini=, 
rtld_fini=, stack_end=0x7ffd12ecfb78) at libc-start.c:274
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4240236755570019627, 
4212360, 140724920974208, 0, 0, -4241690438631797461, -4279196600293372629}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x404950, 0x7ffd12ecfb88}, data 
= {prev = 0x0, cleanup = 0x0, canceltype = 4213072}}}
not_first_call = 
#13 0x004046b1 in ?? ()
No symbol table info available.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Crash at snmp_free_varbind with Net-snmp 5.7.3

2019-05-08 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Net-snmp team,

We are using Net-snmp 5.7.3 in our product and our customer has reported the 
below crash recently, although it was never hit in our internal tests.

Could you please confirm if this is any know issue and if a patch is available 
for the same.

Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/snmpd -f -Lsd -M+/sw/unicorn/snmp/mibs -Dtrap 
-Dusm -Dinit_mibs -I-sy'.
Program terminated with signal 6, Aborted.
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
#0  0x7f22b2c14f57 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:63
resultvar = 0
pid = 6103
selftid = 6103
#1  0x7f22b2c16418 in __GI_abort () at abort.c:90
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7ffd12ecebca, sa_sigaction 
= 0x7ffd12ecebca}, sa_mask = {__val = {6, 139787005871808, 2, 140724920970206, 
2, 139787005862892, 1, 139787005871804, 3, 140724920970180, 12, 
139787005871808, 2, 140724920970992, 11, 140724920972752}}, sa_flags = 93, 
sa_restorer = 0x7}
sigs = {__val = {32, 0 }}
#2  0x7f22b2c52e3b in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f22b2d468a0 "*** glibc detected *** %s: %s: 0x%s ***\n") at 
../sysdeps/unix/sysv/linux/libc_fatal.c:197
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 
0x7ffd12ecf5e0, reg_save_area = 0x7ffd12ecf4f0}}
fd = 2
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7f22b2c589be in malloc_printerr (ptr=, 
str=0x7f22b2d43129 "corrupted double-linked list", action=3, ar_ptr=) at malloc.c:4855
buf = "01806d00"
cp = 
#4  malloc_printerr (action=3, str=0x7f22b2d43129 "corrupted double-linked 
list", ptr=, ar_ptr=) at malloc.c:4836
No locals.
#5  0x7f22b2c58c08 in malloc_consolidate (av=av@entry=0x7f22b2f81660 
) at malloc.c:4086
fb = 
maxfb = 0x7f22b2f816b0 
p = 0x1806b30
nextp = 0x0
unsorted_bin = 0x7f22b2f816b8 
first_unsorted = 
nextchunk = 0x1806d00
size = 512
nextsize = 
prevsize = 
nextinuse = 
bck = 
fwd = 0x7f22b2f816d8 
#6  0x7f22b2c59b18 in _int_free (av=0x7f22b2f81660 , 
p=0x18730a0, have_lock=0, trim=1) at malloc.c:3977
size = 96160
fb = 
nextchunk = 0x18739a0
nextsize = 93856
nextinuse = 
prevsize = 
bck = 
fwd = 
errstr = 0x0
locked = 1
__func__ = "_int_free"
#7  0x7f22b4192cd8 in snmp_free_varbind () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#8  0x7f22b4192d24 in snmp_free_pdu () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#9  0x7f22b41938f5 in snmp_sess_close () from /usr/lib64/libnetsnmp.so.30
No symbol table info available.
#10 0x7f22b4194c2f in snmp_sess_select_info2_flags () from 
/usr/lib64/libnetsnmp.so.30
No symbol table info available.
#11 0x00403c9a in ?? ()
No symbol table info available.
#12 0x7f22b2c01865 in __libc_start_main (main=0x4028f0, argc=20, 
ubp_av=0x7ffd12ecfb88, init=, fini=, 
rtld_fini=, stack_end=0x7ffd12ecfb78) at libc-start.c:274
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4240236755570019627, 
4212360, 140724920974208, 0, 0, -4241690438631797461, -4279196600293372629}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x404950, 0x7ffd12ecfb88}, data 
= {prev = 0x0, cleanup = 0x0, canceltype = 4213072}}}
not_first_call = 
#13 0x004046b1 in ?? ()
No symbol table info available.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

2019-04-12 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Your inputs on this issue is much appreciated..

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 09 April 2019 23:45
To: 'net-snmp-users@lists.sourceforge.net' 

Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
; Naresh Pindukuru -X (narpindu - HCL TECHNOLOGIES LIMITED 
at Cisco) 
Subject: RE: Having mismatch indexes for some interfaces in the IP-MIB and 
IF-MIB

Hi Experts,

Please help me on this.

>From the links below, I see the fix is available for quite some time,
but it has not been integrated into net-snmp latest open source codebase, due 
to some reasons.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 02 April 2019 18:19
To: 'net-snmp-users@lists.sourceforge.net' 
mailto:net-snmp-users@lists.sourceforge.net>>
Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:athu...@cisco.com>>; Naresh Pindukuru -X (narpindu - 
HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>
Subject: RE: Having mismatch indexes for some interfaces in the IP-MIB and 
IF-MIB

Hi Experts,

Could you kindly help on this request please.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 01 April 2019 19:02
To: 
net-snmp-users@lists.sourceforge.net
Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:athu...@cisco.com>>; Naresh Pindukuru -X (narpindu - 
HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>
Subject: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

Hi Experts,


Our Product is currently using Net-snmp 5.7.3, and we are hitting an issue with 
mismatch indexes for some interfaces in the IP-MIB and IF-MIB.

Our DE could find the same issue was already discussed earlier through below 
topics in open forums.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

And the solution for these available at:

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

But the fix hasn't been integrated into Net-snmp 5.7.3, so making our customers 
vulnerable to this issue.

Please let us know if our understanding is right (or) if this has been fixed in 
a different way in net-snmp code (or) is there a chance to include this fix in 
upcoming net-snmp version.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

2019-04-09 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Please help me on this.

>From the links below, I see the fix is available for quite some time,
but it has not been integrated into net-snmp latest open source codebase, due 
to some reasons.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 02 April 2019 18:19
To: 'net-snmp-users@lists.sourceforge.net' 

Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
; Naresh Pindukuru -X (narpindu - HCL TECHNOLOGIES LIMITED 
at Cisco) 
Subject: RE: Having mismatch indexes for some interfaces in the IP-MIB and 
IF-MIB

Hi Experts,

Could you kindly help on this request please.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 01 April 2019 19:02
To: 
net-snmp-users@lists.sourceforge.net
Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:athu...@cisco.com>>; Naresh Pindukuru -X (narpindu - 
HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:narpi...@cisco.com>>
Subject: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

Hi Experts,


Our Product is currently using Net-snmp 5.7.3, and we are hitting an issue with 
mismatch indexes for some interfaces in the IP-MIB and IF-MIB.

Our DE could find the same issue was already discussed earlier through below 
topics in open forums.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

And the solution for these available at:

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

But the fix hasn't been integrated into Net-snmp 5.7.3, so making our customers 
vulnerable to this issue.

Please let us know if our understanding is right (or) if this has been fixed in 
a different way in net-snmp code (or) is there a chance to include this fix in 
upcoming net-snmp version.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

2019-04-02 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you kindly help on this request please.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 01 April 2019 19:02
To: net-snmp-users@lists.sourceforge.net
Cc: Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
; Naresh Pindukuru -X (narpindu - HCL TECHNOLOGIES LIMITED 
at Cisco) 
Subject: Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

Hi Experts,


Our Product is currently using Net-snmp 5.7.3, and we are hitting an issue with 
mismatch indexes for some interfaces in the IP-MIB and IF-MIB.

Our DE could find the same issue was already discussed earlier through below 
topics in open forums.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

And the solution for these available at:

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

But the fix hasn't been integrated into Net-snmp 5.7.3, so making our customers 
vulnerable to this issue.

Please let us know if our understanding is right (or) if this has been fixed in 
a different way in net-snmp code (or) is there a chance to include this fix in 
upcoming net-snmp version.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Having mismatch indexes for some interfaces in the IP-MIB and IF-MIB

2019-04-01 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,


Our Product is currently using Net-snmp 5.7.3, and we are hitting an issue with 
mismatch indexes for some interfaces in the IP-MIB and IF-MIB.

Our DE could find the same issue was already discussed earlier through below 
topics in open forums.

https://bugzilla.redhat.com/show_bug.cgi?id=114413
https://bugzilla.redhat.com/show_bug.cgi?id=119106

And the solution for these available at:

https://bugzilla.redhat.com/attachment.cgi?id=98840&action=diff

But the fix hasn't been integrated into Net-snmp 5.7.3, so making our customers 
vulnerable to this issue.

Please let us know if our understanding is right (or) if this has been fixed in 
a different way in net-snmp code (or) is there a chance to include this fix in 
upcoming net-snmp version.

Thanks,
Kiran

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: snmpd[20456]: %WAAS-UNKNOWN-3-899999: truncating integer value > 32 bits

2019-03-25 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you kindly help on this.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 13 March 2019 23:23
To: 'net-snmp-users@lists.sourceforge.net' 

Subject: snmpd[20456]: %WAAS-UNKNOWN-3-89: truncating integer value > 32 
bits


Hi Experts,



Our customer reported below messages. Customer want to know the impact and how 
to stop them.



--

Mar 10 16:35:03 10.137.33.13 2019 Mar 10 07:35:10 snmpd[20456]: 
%WAAS-UNKNOWN-3-89: truncating integer value > 32 bits Mar 10 16:35:40 
10.137.33.13 2019 Mar 10 07:35:11 snmpd[20456]: %WAAS-UNKNOWN-3-89: 
truncating integer value > 32 bits Mar 10 16:40:06 10.137.33.13 2019 Mar 10 
07:40:12 snmpd[20456]: %WAAS-UNKNOWN-3-89: truncating integer value > 32 
bits Mar 10 16:50:10 10.137.33.13 2019 Mar 10 07:50:12 last message repeated 5 
times Mar 10 17:00:10 10.137.33.13 2019 Mar 10 08:00:12 last message repeated 4 
times

--



Customer informed  the message was seen after running our WAAS Product 1 year, 
19 weeks, 23 hours that has Net-snmp 5.7.3 installed on it.



We think it looks close to:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597024

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597024;msg=2



The above links mention about a patch to change:
snmplib/snmp_client.c 805c805
< snmp_log(LOG_ERR,"truncating integer value > 32
bits\n");
---
> snmp_log(LOG_DEBUG,"truncating integer value > 32 
> bits\n");
816c816



But I see this code is unchanged and remains the same in Net-snmp 5.8 also, 
without above patch.


Could you please advise how to address this issue for our customer.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

snmpd[20456]: %WAAS-UNKNOWN-3-899999: truncating integer value > 32 bits

2019-03-13 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,



Our customer reported below messages. Customer want to know the impact and how 
to stop them.



--

Mar 10 16:35:03 10.137.33.13 2019 Mar 10 07:35:10 snmpd[20456]: 
%WAAS-UNKNOWN-3-89: truncating integer value > 32 bits Mar 10 16:35:40 
10.137.33.13 2019 Mar 10 07:35:11 snmpd[20456]: %WAAS-UNKNOWN-3-89: 
truncating integer value > 32 bits Mar 10 16:40:06 10.137.33.13 2019 Mar 10 
07:40:12 snmpd[20456]: %WAAS-UNKNOWN-3-89: truncating integer value > 32 
bits Mar 10 16:50:10 10.137.33.13 2019 Mar 10 07:50:12 last message repeated 5 
times Mar 10 17:00:10 10.137.33.13 2019 Mar 10 08:00:12 last message repeated 4 
times

--



Customer informed  the message was seen after running our WAAS Product 1 year, 
19 weeks, 23 hours that has Net-snmp 5.7.3 installed on it.



We think it looks close to:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597024

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597024;msg=2



The above links mention about a patch to change:
snmplib/snmp_client.c 805c805
< snmp_log(LOG_ERR,"truncating integer value > 32
bits\n");
---
> snmp_log(LOG_DEBUG,"truncating integer value > 32 
> bits\n");
816c816



But I see this code is unchanged and remains the same in Net-snmp 5.8 also, 
without above patch.


Could you please advise how to address this issue for our customer.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: nsNotifyRestart traps generated in place of link up/down.

2019-02-11 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you kindly help with your inputs on this and how to recover from the 
problem.

Thanks,
Kiran

From: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco)
Sent: 08 February 2019 23:49
To: 'net-snmp-users@lists.sourceforge.net' 

Cc: Sreenivasa Reddy Pappuri -X (spappuri - HCL TECHNOLOGIES LIMITED at Cisco) 
; Apparao Podile -X (apodile - HCL TECHNOLOGIES LIMITED at 
Cisco) ; Mathuvappan Sokkalingam -X (msokkali - HCL AMERICA 
INC at Cisco) ; Naresh Pindukuru -X (narpindu - HCL 
TECHNOLOGIES LIMITED at Cisco) ; Saravanan Adhikesavan -X 
(sadhikes - HCL TECHNOLOGIES LIMITED at Cisco) ; Kondalraj 
Kosalram -X (kkosalra - HCL TECHNOLOGIES LIMITED at Cisco) 
Subject: nsNotifyRestart traps generated in place of link up/down.

Hi Experts,

In our product we are using Net-snmp 5.7.3 and today a customer is hitting a 
strange issue with
some undesired nsNotifyRestart traps being generated, in place of link up/down 
traps,
when performed shut/noshut operations on selected intetrface.

Here is the SNMP v1 config Used by Customer:

snmp-server host x.y.z.w snmpComm1ab
snmp-server enable traps snmp linkup
snmp-server enable traps snmp linkdown

Here is the Unwanted nsNotifyRestart trap getting generated when performed 
interface shut/noshut operations

2019-02-08 17:07:19 x.x.x.x(via UDP: [x.x.x.x]:x->[x.x.x.x]:x) TRAP, SNMP v1, 
community snmpComm1ab
NET-SNMP-MIB::netSnmpNotificationPrefix Enterprise Specific Trap 
(NET-SNMP-AGENT-MIB::nsNotifyRestart) Uptime: 0:00:05.44

Any thoughts when "nsNotifyRestart" traps are generated and why they are 
blocking the expected link up/down traps here ?
And how to proceed forward on this case with customer ?

Could you please advise.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

nsNotifyRestart traps generated in place of link up/down.

2019-02-08 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

In our product we are using Net-snmp 5.7.3 and today a customer is hitting a 
strange issue with
some undesired nsNotifyRestart traps being generated, in place of link up/down 
traps,
when performed shut/noshut operations on selected intetrface.

Here is the SNMP v1 config Used by Customer:

snmp-server host x.y.z.w snmpComm1ab
snmp-server enable traps snmp linkup
snmp-server enable traps snmp linkdown

Here is the Unwanted nsNotifyRestart trap getting generated when performed 
interface shut/noshut operations

2019-02-08 17:07:19 x.x.x.x(via UDP: [x.x.x.x]:x->[x.x.x.x]:x) TRAP, SNMP v1, 
community snmpComm1ab
NET-SNMP-MIB::netSnmpNotificationPrefix Enterprise Specific Trap 
(NET-SNMP-AGENT-MIB::nsNotifyRestart) Uptime: 0:00:05.44

Any thoughts when "nsNotifyRestart" traps are generated and why they are 
blocking the expected link up/down traps here ?
And how to proceed forward on this case with customer ?

Could you please advise.

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Reg AES128 Support with Netsnmp 5.7.3

2019-01-24 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Thanks Bill for the pointer

Regards,
Kiran

From: Bill Fenner 
Sent: 25 January 2019 01:30
To: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) 

Cc: net-snmp-users@lists.sourceforge.net; Anil Kumar Thumma -X (athumma - HCL 
TECHNOLOGIES LIMITED at Cisco) 
Subject: Re: Reg AES128 Support with Netsnmp 5.7.3

You can try 
http://net-snmp.sourceforge.net/wiki/index.php/TUT:SNMPv3_Options#Configuration 
but replace "DES" with "AES".

  Bill


On Thu, Jan 24, 2019 at 12:27 PM Kiran Kumar Pamula -X (kpamula - HCL 
TECHNOLOGIES LIMITED at Cisco) mailto:kpam...@cisco.com>> 
wrote:
Thanks a lot Bill for your kind response.

Could you please help us with the configuration change required on Agent side.

Thanks,
Kiran

From: Bill Fenner mailto:fen...@gmail.com>>
Sent: 23 January 2019 05:56
To: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:kpam...@cisco.com>>
Cc: 
net-snmp-users@lists.sourceforge.net<mailto:net-snmp-users@lists.sourceforge.net>;
 Anil Kumar Thumma -X (athumma - HCL TECHNOLOGIES LIMITED at Cisco) 
mailto:athu...@cisco.com>>
Subject: Re: Reg AES128 Support with Netsnmp 5.7.3


On Jan 22, 2019, at 12:26 AM, Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES 
LIMITED at Cisco) via Net-snmp-users 
mailto:net-snmp-users@lists.sourceforge.net>>
 wrote:
Hi Experts,

Could you please confirm if AES128 is fully supported with Net-snmp 5.7.3

Yes, it is. Did you configure the user to use AES on the agent side?

  Bill

___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

RE: Reg AES128 Support with Netsnmp 5.7.3

2019-01-24 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Thanks a lot Bill for your kind response.

Could you please help us with the configuration change required on Agent side.

Thanks,
Kiran

From: Bill Fenner 
Sent: 23 January 2019 05:56
To: Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) 

Cc: net-snmp-users@lists.sourceforge.net; Anil Kumar Thumma -X (athumma - HCL 
TECHNOLOGIES LIMITED at Cisco) 
Subject: Re: Reg AES128 Support with Netsnmp 5.7.3


On Jan 22, 2019, at 12:26 AM, Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES 
LIMITED at Cisco) via Net-snmp-users 
mailto:net-snmp-users@lists.sourceforge.net>>
 wrote:
Hi Experts,

Could you please confirm if AES128 is fully supported with Net-snmp 5.7.3

Yes, it is. Did you configure the user to use AES on the agent side?

  Bill


___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reg AES128 Support with Netsnmp 5.7.3

2019-01-21 Thread Kiran Kumar Pamula -X (kpamula - HCL TECHNOLOGIES LIMITED at Cisco) via Net-snmp-users 
Hi Experts,

Could you please confirm if AES128 is fully supported with Net-snmp 5.7.3

>From code references in Netsnmp 5.7.3, we see support exists,
but when executing snmpwalk it fails in AES, rather it succeeds with DES as 
below:

AES: (Doesn't Work)
hostname# snmpwalk -v 3 -u SolarWinds-Auth -l AuthPriv localhost -a SHA -A 
watchThis123 -x AES -X watchThis123 system
snmpwalk: Decryption error (Sub-id not found: (top) -> system)
hostnamel#

DES: (Works)
hostname# snmpwalk -v 3 -u SolarWinds-Auth -l AuthPriv localhost -a SHA -A 
watchThis123 -x DES -X watchThis123 system
SNMPv2-MIB::sysDescr.0 = STRING: XXX
SNMPv2-MIB::sysObjectID.0 = OID: CISCO-SMI::ciscoProducts.1351
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (4528) 0:00:45.28
SNMPv2-MIB::sysContact.0 = STRING: Null
SNMPv2-MIB::sysName.0 = STRING: aaa-dc2-7541.cisco.com
SNMPv2-MIB::sysLocation.0 = STRING: Null
SNMPv2-MIB::sysServices.0 = INTEGER: 72
hostname#

Thanks,
Kiran
___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users