Error on subcontainer ia addr insert

snmpd[3916]: error on subcontainer ‘ia_addr’ insert (-1)

This message is flooding my syslog on each snmp query.

To avoid it you have to change the log level of the services. In debian squeeze edit /etc/default/snmpd and change these lines:

4 thoughts to “snmpd[3916]: error on subcontainer ‘ia_addr’ insert (-1)”

snmpd gives “error on subcontainer” warnings

This document (7005030) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 11
Situation
After starting the snmpd service “service snmpd start” the following messages appear in /var/log/net-snmpd.log

error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)

The error occurs every 30 seconds and fills the log.
Resolution
The message ‘error on subcontainer’ is logged with log level DEBUG. The log level for snmp is set in /etc/sysconfig/net-snmp by SNMPD_LOGLEVEL. By default it is set to ‘d’ (debug) to ensure backward compatibility with an older init script.

If you want to stop these messages, you can change the log level in /etc/sysconfig/net-snmp. The available log levels are documented in snmpcmd(1).

In /etc/sysconfig/net-snmp you can set the log level down wards to ‘i’ (LOG_INFO):

SNMPD_LOGLEVEL=”d”
to
SNMPD_LOGLEVEL=”i”

and restart snmpd.
Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Document ID:7005030
Creation Date:15-DEC-09
Modified Date:27-APR-12
SUSESUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Источник

The Snmpd.log Repeatedly Records «error on subcontainer ‘ia_addr’ insert (-1)» Message (Doc ID 1549401.1)

Last updated on MAY 13, 2021

Applies to:

Symptoms

Approximately every 30 seconds a message is logged to the /var/log/snmpd.log file:

error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)
error on subcontainer ‘ia_addr’ insert (-1)

Despite this message the Net-SNMP service, snmpd, operates correctly and responds to SNMP queries.

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

Problem starting net-snmp-5.7_3

cybercoke

Hy guys, I installed net-snmp-5.7_3 on several FreeBSD 8.1-RELEASE machines without any problem, but, when I try to start it with default config /usr/local/share/snmp/snmpd.conf (copy by snmpd.conf.sample) it gave me the following error:

There are no other snmpd.conf anywhere on the paths that it looking for. If I start it from [cmd=]/usr/local/etc/rc.d/snmpd start[/cmd] it gave me the following error:

SirDice

Administrator

cybercoke

Hy SirDice, here is my snmpd.conf:

SirDice

Administrator

cybercoke

SirDice

Administrator

cybercoke

It does the same error:

SirDice

Administrator

Isn’t it already running? It looks like it’s trying to add stuff that’s already there.

ps -aux | grep snmpd

cybercoke

Isn’t it already running? It looks like it’s trying to add stuff that’s already there.

ps -aux | grep snmpd

There is nothing running at all.

cybercoke

Hi guys, I still can’t get net-snmp to work on several machines. Please help me.

SirDice

Administrator

Ah.. I couldn’t figure it out myself. So I just installed it and started playing with it.

Remove your /usr/local/share/snmp/snmpd.conf and run the following command:
# snmpconf -g basic_setup

Answer the questions and it’ll generate a proper snmpd.conf. Copy that file to /usr/local/share/snmp/. It should start properly now.

cybercoke

Ah.. I couldn’t figure it out myself. So I just installed it and started playing with it.

Источник

Что не пускает к агенту SNMP?

ОС Debian (lenny). Установлен SMTPD, настроен. Команда к примеру #snmpwalk -c public localhost -v1 отрабатывает без проблем. Стоит localhost заменить реальным IP адресом компьютера, например snmpwalk -c public 192.168.1.55 -v1, получаем Timeout: No Response from 192.168.1.55. С других машин локалки разумеется доступа тоже нет.

Кусок файла конфигурации: com2sec local localhost public com2sec localnet 192.168.0.0/24 public

Вроде ж прописано — пущать в/из локалки. Что то где то надо ещё?

в /etc/default/snmp-что-то там там по умолчанию он слушает на 127.0.0.1
Соответственно, когда вы указываете localhost — он обращается на 127.0.0.1 Это же можно было узнать посмотрев нетстатом =)

Не так всё просто

Чуть позже выяснил, что агент по умолчанию сел на UDP6. Прописал в файл snmpd.conf строку:

В результате имеем:

Dec 11 14:32:41 begemot snmpd[2325]: error on subcontainer ‘ia_addr’ insert (-1) Dec 11 14:32:41 begemot snmpd[2325]: Error opening specified endpoint «udp:161» Dec 11 14:32:41 begemot snmpd[2325]: Server Exiting with code 1

Пробовал сажать на другие порты. Сел на 162, но работал нестабильно и в конце концов тоже перестал его подключать.

begemot, вы читали, что я написал в предыдущем посте?
файлик точно /etc/default/snmpd

Но пардон!

А кто ему не даёт то сесть на 161 порт НЕ по умолчанию, если я прописал в конфиге /etc/snmpd.conf строку

И почему он при этом садится на 162. Нетстат как раз показывает, что оба порта одинаково свободны.

Спасибо, основные проблемы решены.

Осталась одна, касающаяся ловли трапов. Как избавиться от сообщения:

snmptrapd[2205]: Warning: no access control information configured.

Источник

Monitoring Linux problem — SNMP port not reachable

I’ve been following instructions to monitor my Linux server (Dell server — opensuse) and installed net-snmp.

According to http://www.debianhelp.co.uk/snmp.htm I changed the snmpd.conf file and I think I’ve done everything correctly, but when I test with «snmpwalk localhost -c public -v1», I get the following error «timeout: no response from localhost»

Can someone help with this problem?

Created on Jun 7, 2010 3:51:28 PM by mastr2 (1) ● 1

Last change on Jan 4, 2023 11:45:48 AM by Brandy Greger [Paessler Support]

Best Answer

This article applies as of PRTG 22

Checklist: Setting up SNMP on Linux

Note: This article applies to Debian-based systems. For other Linux distributions like RedHat, CentOS, and Suse, you must slightly adapt the following steps. See SNMP installation and configuration for more details.

Every so often, monitoring devices via SNMP causes issues. We collect the most common problems with SNMP in the article SNMP and PRTG: Basic Troubleshooting. On Linux systems, some additional points have to be considered. This article sums up the basic steps to set up SNMP on Debian-based systems for monitoring with PRTG. However, specific problems often require deeper analysis. If you followed the checklist below and monitoring still does not work, do not hesitate to contact our support.

Good resources for information about SNMP on Linux systems are the articles on Sijoe Web’s: SNMP Server (snmpd) and Client (snmp) Installation and Configuration in Debian and on ubuntuusers Wiki: SNMP (German). Refer to these pages if you need more details on this topic.

1. Set up SNMP

First, you need an SNMP server on your Linux machine. Install the packet snmpd to query network components, and the packet snmp to request values (for example walk or get). Use the following commands: sudo apt-get install snmpd sudo apt-get install snmp After you installed these packets, you must follow the configuration steps below.

Basic configuration: SNMP v1 and v2

The configuration file snmpd.conf is located in the /etc/snmp directory. Make a backup of the original file before you edit it.

You have to set up the SNMP server in order to allow read access from other machines. Open the configuration file with an editor. # sec.name source community com2sec paranoid default public Change the entry paranoid to readonly or readwrite. You can define sources as you want (for example 127.0.0.1 to only allow access from the local machine), and you can modify the community string as well. Save the changes to the configuration and restart the SNMP daemon: sudo service snmpd restart

Basic configuration: SNMP v3

If you want to use SNMP v3, you need the packet openssl in addition. Stop the SNMP daemon and create an SNMP v3 user: sudo service snmpd stop

sudo net-snmp-config —create-snmpv3-user -ro -X DES -A MD5 -a «SNMP_PWD» -x «SNMP_PWD» username

After that, force encryption in the file /usr/share/snmp/snmpd.conf by adding AuthPriv: rouser username AuthPriv

Furthermore, delete the file /etc/snmp/snmpd.conf, and create a new one with the following content:

group groupv3 usm username view all included .iso 80

Note: Ubuntu 18.04 implements stronger security mechanisms, so you have to provide a wider path in /etc/snmp/snmpd.conf: view systemonly included .1.3.6.1

# context sec.model sec.level match read write notif access groupv3 «» any auth exact all all all syslocation Unknown syscontact Root

Then start the daemon again: sudo service snmpd start

2. Set up access

By default, only requests on localhost are allowed. In order to allow access for other IPs on the monitored computer, modify the start options in the file /etc/default/snmpd. There you will find the following line: SNMPDOPTS=’-Lsd -Lf /dev/null -u snmp -g snmp -I -smux -p /var/run/snmpd.pid 127.0.0.1′ You have two options now:

• In order to allow requests for all network interfaces, delete 127.0.0.1 from the line.
• To allow requests only for specific devices, add the corresponding IP addresses after 127.0.0.1, separated by spaces. Then restart snmpd. You can also allow access only for specific computers by modifying /etc/snmp/snmpd.conf accordingly. Just specify the sources there with the IP addresses that should get access.

# com2sec paranoid default public # com2sec readonly default public com2sec readonly xxx.xxx.xxx.xxx/32 public com2sec readonly yyy.yyy.yyy.yyy/32 public

Note: If you have a firewall, you need to open the UDP port 161 to get access from other computers. For example, use the following commands to open access:

iptables -A OUTPUT -p udp -m udp —sport 161 -j ACCEPT iptables -A ufw-user-input -p udp -m udp —dport 161 -j ACCEPT

3. Test the configuration with an SNMP walk

You can test your configuration with an SNMP walk. A walk shows you lists of return values requested from a specific device. Use the following command to show a list of available data on your Linux machine: snmpwalk –v1 –c public localhost With the following command, a list of memory values on a specific device (indicated with ) is returned: snmpwalk v1 –c –private memory

Note: Do not only use 127.0.0.1 for testing, but also external IP addresses.

4. Test the configuration with the SNMP Tester

Use the SNMP Tester to run test queries against your Linux device. This tool enables you to debug SNMP activities in order to find problems in your SNMP configuration. For more information, the download, and the manual, please refer to Paessler SNMP Tester.

5. Create sensors in PRTG

PRTG already provides several SNMP sensors for Linux monitoring out of the box. You can natively monitor for example free disk space, load average, memory usage, and I/O on physical disks via SNMP.

You can also use the SNMP Library sensor to adjust monitoring to your needs. PRTG already includes a basic Linux OID library (ucd-snmp-mib).

1. Create a device for the Linux machine you want to monitor (enter this computer’s IP address or DNS name)
2. On this device, create an SNMP Library sensor or one of the natively available ones.
   1. For the SNMP Library sensor: From the appearing list, select the basic linux library (ucd-snmp-mib).oidlib file.
   2. In the next step, you will see a list of library OIDs that indicate the available sensors. Select the sensors you want to monitor by marking the corresponding checkboxes.
3. Click Continue.

PRTG will start to monitor your Linux device immediately.

Last change on Jan 4, 2023 11:46:06 AM by Brandy Greger [Paessler Support]

Источник

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com