O SNMP não funciona no servidor ubuntu 16.04 após a instalação. Eu fiz uma instalação limpa do servidor Ubuntu, depois que eu atualizei. Então, o sudo apt instala snmp snmpd e teve muitos problemas. você pode me ajudar?
cdt@srv-ubuntu:~$ sudo apt-get install snmp snmpd snmp-mibs-downloader -y
[sudo] senha para cdt:
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
snmp is already the newest version (5.7.3+dfsg-1ubuntu4).
snmpd is already the newest version (5.7.3+dfsg-1ubuntu4).
snmp-mibs-downloader is already the newest version (1.1).
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 1 não atualizados.
1 pacotes não totalmente instalados ou removidos.
Depois desta operação, 0 B adicionais de espaço em disco serão usados.
Configurando snmpd (5.7.3+dfsg-1ubuntu4) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match snmpd Default-Stop values (0 1 6)
Job for snmpd.service failed because the control process exited with error code. See "systemctl status snmpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript snmpd, action "start" failed.
● snmpd.service - LSB: SNMP agents
Loaded: loaded (/etc/init.d/snmpd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sex 2017-07-07 09:15:16 BRT; 8ms ago
Docs: man:systemd-sysv-generator(8)
Process: 30842 ExecStart=/etc/init.d/snmpd start (code=exited, status=1/FAILURE)
snmpd[30842]: * Starting SNMP services:
snmpd[30847]: /etc/snmp/snmpd.conf: line 145: Warning: Unknown token: defaultMonitors.
snmpd[30847]: /etc/snmp/snmpd.conf: line 147: Warning: Unknown token: linkUpDownNotifications.
snmpd[30847]: Turning on AgentX master support.
snmpd[30847]: Error opening specified endpoint "udp:127.0.0.1:161"
snmpd[30847]: Server Exiting with code 1
systemd[1]: snmpd.service: Control process exited, code=exited status=1
systemd[1]: Failed to start LSB: SNMP agents.
systemd[1]: snmpd.service: Unit entered failed state.
systemd[1]: snmpd.service: Failed with result 'exit-code'.
dpkg: erro ao processar o pacote snmpd (--configure):
sub-processo script post-installation instalado retornou estado de saída de erro 1
Erros foram encontrados durante o processamento de: snmpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
systemctl status snmpd.service
cdt@srv-ubuntu:~$ sudo systemctl status snmpd.service
● snmpd.service - LSB: SNMP agents
Loaded: loaded (/etc/init.d/snmpd; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sex 2017-07-07 09:15:16 BRT; 11min ago
Docs: man:systemd-sysv-generator(8)
Process: 30842 ExecStart=/etc/init.d/snmpd start (code=exited, status=1/FAILURE)
Jul 07 09:15:16 srv-ubuntu snmpd[30842]: * Starting SNMP services:
Jul 07 09:15:16 srv-ubuntu snmpd[30847]: /etc/snmp/snmpd.conf: line 145: Warning: Unknown token: defaultMonitors.
Jul 07 09:15:16 srv-ubuntu snmpd[30847]: /etc/snmp/snmpd.conf: line 147: Warning: Unknown token: linkUpDownNotifications.
Jul 07 09:15:16 srv-ubuntu snmpd[30847]: Turning on AgentX master support.
Jul 07 09:15:16 srv-ubuntu snmpd[30847]: Error opening specified endpoint "udp:127.0.0.1:161"
Jul 07 09:15:16 srv-ubuntu snmpd[30847]: Server Exiting with code 1
Jul 07 09:15:16 srv-ubuntu systemd[1]: snmpd.service: Control process exited, code=exited status=1
Jul 07 09:15:16 srv-ubuntu systemd[1]: Failed to start LSB: SNMP agents.
Jul 07 09:15:16 srv-ubuntu systemd[1]: snmpd.service: Unit entered failed state.
Jul 07 09:15:16 srv-ubuntu systemd[1]: snmpd.service: Failed with result 'exit-code'.
/etc/snmp/snmpd.conf (eu não mudei nada, apenas instale)
###############################################################################
#
# EXAMPLE.conf:
# An example configuration file for configuring the Net-SNMP agent ('snmpd')
# See the 'snmpd.conf(5)' man page for details
#
# Some entries are deliberately commented out, and will need to be explicitly activated
#
###############################################################################
#
# AGENT BEHAVIOUR
#
# Listen for connections from the local system only
agentAddress udp:127.0.0.1:161
# Listen for connections on all interfaces (both IPv4 *and* IPv6)
#agentAddress udp:161,udp6:[::1]:161
###############################################################################
#
# SNMPv3 AUTHENTICATION
#
# Note that these particular settings don't actually belong here.
# They should be copied to the file /var/lib/snmp/snmpd.conf
# and the passwords changed, before being uncommented in that file *only*.
# Then restart the agent
# createUser authOnlyUser MD5 "remember to change this password"
# createUser authPrivUser SHA "remember to change this one too" DES
# createUser internalUser MD5 "this is only ever used internally, but still change the password"
# If you also change the usernames (which might be sensible),
# then remember to update the other occurances in this example config file to match.
###############################################################################
#
# ACCESS CONTROL
1,1 Topo#
# system + hrSystem groups only
view systemonly included .1.3.6.1.2.1.1
view systemonly included .1.3.6.1.2.1.25.1
# Full access from the local host
#rocommunity public localhost
# Default access to basic system info
rocommunity public default -V systemonly
# rocommunity6 is for IPv6
rocommunity6 public default -V systemonly
# Full access from an example network
# Adjust this network address to match your local
# settings, change the community string,
# and check the 'agentAddress' setting above
#rocommunity secret 10.0.0.0/16
# Full read-only access for SNMPv3
rouser authOnlyUser
# Full write access for encrypted requests
# Remember to activate the 'createUser' lines above
#rwuser authPrivUser priv
# It's no longer typically necessary to use the full 'com2sec/group/access' configuration
# r[ow]user and r[ow]community, together with suitable views, should cover most requirements
###############################################################################
#
# SYSTEM INFORMATION
#
# Note that setting these values here, results in the corresponding MIB objects being 'read-only'
# See snmpd.conf(5) for more details
sysLocation Sitting on the Dock of the Bay
sysContact Me <[email protected]>
# Application + End-to-End layers
sysServices 72
#
# Process Monitoring
#
# At least one 'mountd' process
proc mountd
# No more than 4 'ntalkd' processes - 0 is OK
proc ntalkd 4
# At least one 'sendmail' process, but no more than 10
proc sendmail 10 1
# Walk the UCD-SNMP-MIB::prTable to see the resulting output
# Note that this table will be empty if there are no "proc" entries in the snmpd.conf file
#
# Disk Monitoring
#
# 10MBs required on root disk, 5% free on /var, 10% free on all other disks
disk / 10000
disk /var 5%
includeAllDisks 10%
# Walk the UCD-SNMP-MIB::dskTable to see the resulting output
# Note that this table will be empty if there are no "disk" entries in the snmpd.conf file
#
# System Load
#
# Unacceptable 1-, 5-, and 15-minute load averages
load 12 10 5
# Walk the UCD-SNMP-MIB::laTable to see the resulting output
# Note that this table *will* be populated, even without a "load" entry in the snmpd.conf file
#
# System Load
#
# Unacceptable 1-, 5-, and 15-minute load averages
load 12 10 5
# Walk the UCD-SNMP-MIB::laTable to see the resulting output
# Note that this table *will* be populated, even without a "load" entry in the snmpd.conf file
###############################################################################
#
# ACTIVE MONITORING
#
# send SNMPv1 traps
trapsink localhost public
# send SNMPv2c traps
#trap2sink localhost public
# send SNMPv2c INFORMs
#informsink localhost public
# Note that you typically only want *one* of these three lines
# Uncommenting two (or all three) will result in multiple copies of each notification.
#
# Event MIB - automatically generate alerts
#
# Remember to activate the 'createUser' lines above
iquerySecName internalUser
rouser internalUser
# generate traps on UCD error conditions
defaultMonitors yes
# generate traps on linkUp/Down
linkUpDownNotifications yes
###############################################################################
#
# EXTENDING THE AGENT
#
#
# Arbitrary extension commands
#
extend test1 /bin/echo Hello, world!
extend-sh test2 echo Hello, world! ; echo Hi there ; exit 35
#extend-sh test3 /bin/sh /tmp/shtest
# Note that this last entry requires the script '/tmp/shtest' to be created first,
# containing the same three shell commands, before the line is uncommented
# Walk the NET-SNMP-EXTEND-MIB tables (nsExtendConfigTable, nsExtendOutput1Table
# and nsExtendOutput2Table) to see the resulting output
# Note that the "extend" directive supercedes the previous "exec" and "sh" directives
# However, walking the UCD-SNMP-MIB::extTable should still returns the same output,
# as well as the fuller results in the above tables.
#
# "Pass-through" MIB extension command
#
#pass .1.3.6.1.4.1.8072.2.255 /bin/sh PREFIX/local/passtest
#pass .1.3.6.1.4.1.8072.2.255 /usr/bin/perl PREFIX/local/passtest.pl
# Note that this requires one of the two 'passtest' scripts to be installed first,
# before the appropriate line is uncommented.
# These scripts can be found in the 'local' directory of the source distribution,
# and are not installed automatically.
# Walk the NET-SNMP-PASS-MIB::netSnmpPassExamples subtree to see the resulting output
#
# AgentX Sub-agents
#
# Run as an AgentX master agent
master agentx
# Listen for network connections (from localhost)
# rather than the default named socket /var/agentx/master
#agentXSocket tcp:localhost:705
Ao fazer novos testes para tentar encontrar os problemas, deduzo que ocorre quando tenho partições em diferentes hds. Assim, eu fiz uma instalação que inclui todos os diretórios na mesma partição. Eu também instalei o SNMP e o SNMPD, que funcionaram bem. Além disso, fiz outra instalação com duas partições no mesmo HD e coloquei “/” em uma partição e “/ home” em outra. Então eu instalei o SNMP e o SNMPD e funcionou bem. No último caso, fiz uma instalação usando diferentes discos rígidos para diferentes partições, seguindo o exemplo acima, que é “/” em um hd e “/ home” em outro. Neste caso específico, os erros estão aparecendo, principalmente durante a instalação do SNMPD.
Obrigado em avançado