deprecated sysctl warning when snmpd is running in LXC container

2013-12-12 Thread Alexander Bergmann 
Hi everyone,

we ran into a problem with snmpd inside a LXC container. The container 
does not offer the neigh/default directories for ipv4 and ipv6.
Therefore it cannot access the retrans_time_ms files inside 
the netsnmp_arch_interface_init() function and falls back to the 
deprecated retrans_time proc file.

/proc/sys/net/ipv6/neigh/default/retrans_time_ms

This causes snmpd during initialization to access the deprecated proc 
file retrans_time of the available interfaces:

/proc/sys/net/ipv6/neigh/interface/retrans_time

Then the following kernel message will show up:

 kernel: process `snmpd' is using deprecated sysctl (syscall) 
 net.ipv6.neigh.default.retrans_time; Use 
 net.ipv6.neigh.default.retrans_time_ms instead.

The question is now, is this a snmpd problem or is this a LXC issue.

One way to get this fixed would be to check for retrans_time_ms and
if not available for retrans_time inside _arch_interface_flags_v4_get(). 
In that case it wouldn't be necessary to access the default directory at
all. The same would go for the v6 function.

Any feedback would be appreciated.


Regards,
Alex

-- 
Alexander Bergmann abergm...@suse.com
Security Software Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)


signature.asc
Description: Digital signature
--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Re: Help! Convert OCTET string to READABLE string

2013-12-12 Thread Niels Baggesen 
On Thu, Dec 05, 2013 at 06:04:22PM +0800, namgmail wrote:
 Hi Niels,
 
 This is my full command:
 
 Sender:
  update=a1 a1 a2 a3 ...a400   #long string count from
 a1 to a400
   snmpset -v1 -c private 192.168.4.113 *.1.3.6.1.4.1.5*
 *s*  ${update}

I would like to see exactly what your update string looks like!

Also, please run snmpset with the -d option to dump the packets that are
sent and received, so we know if this is a snmpset or a snmpd problem.

/Niels

-- 
Niels Baggesen - @home - Århus - Denmark - n...@users.sourceforge.net
The purpose of computing is insight, not numbers   ---   R W Hamming

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders