Hello
@benhank
Thanks for following up, the message; "A plugin had an unrecoverable error. Will restart this plugin.\n Plugin: <LogStash::Inputs::Tcp type=>\"snmptrap\..." From what I see it appears that there is a plugin associated with snmptrap that is failing. Let's make sure that the logstash service looks okay, and should look similar:
Code: Select all
● logstash.service - LSB: Logstash
Loaded: loaded (/etc/rc.d/init.d/logstash; generated)
Active: active (running) since Mon 2021-12-06 06:27:47 CST; 3 days ago
Docs: man:systemd-sysv-generator(8)
Tasks: 43 (limit: 101107)
Memory: 638.5M
CGroup: /system.slice/logstash.service
├─1005 runuser -s /bin/sh -c exec /usr/local/nagioslogserver/logstash/bin/logstash agent -f /usr/local/nagioslogserver/logstash/etc/conf.d -l /var/log/logstash/logstash.log -w 4 nagios
└─1030 /bin/java -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/usr/local/nagioslogserver/tmp -Xmx500m -Xss2048k -Djffi.boot.library.path=/usr/local/nagioslogserver/logstash/vendor/jruby/lib/jni -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -Djava.awt.headless=true -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/usr/local/nagioslogserver/tmp -XX:HeapDumpPath=/usr/local/nagioslogserver/logstash/heapdump.hprof -Xbootclasspath/a:/usr/local/nagioslogserver/logstash/vendor/jruby/lib/jruby.jar -classpath : -Djruby.home=/usr/local/nagioslogserver/logstash/vendor/jruby -Djruby.lib=/usr/local/nagioslogserver/logstash/vendor/jruby/lib -Djruby.script=jruby -Djruby.shell=/bin/sh org.jruby.Main --1.9 /usr/local/nagioslogserver/logstash/lib/bootstrap/environment.rb logstash/runner.rb agent -f /usr/local/nagioslogserver/logstash/etc/conf.d -l /var/log/logstash/logstash.log -w 4
The /usr/local/nagioslogserver/.... owner: nagios and associated with nagios group:
Code: Select all
ls -laR /usr/local/nagioslogserver/ | grep -Ei '^d' | less
Also, take a look to see if there is anything logged in the system logs, or we will need to try to figure out which 'plugin' the error message is referring to.
Please let us know how things look,
Perry