Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

All work

Select view

Select search mode

 
1 of 1

Opennms 28.0.1 fails after start related to telemetryd problem

Description

Opennms 28.0.1 fails after start related to telemetryd problem

 

2021-08-09 11:14:55,259 ERROR [Main] o.o.n.v.Starter: An error occurred while attempting to start the "OpenNMS:Name=Telemetryd" service (class org.opennms.netmgt.daemon.SimpleSpringContextJmxServiceDaemon). Shutting down and exiting. javax.management.RuntimeMBeanException: java.lang.IllegalArgumentException: Each parser must be of type UdpParser but was not. at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:829) ~[?:?] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:842) ~[?:?] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:811) ~[?:?] at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) ~[?:?] at org.opennms.netmgt.vmmgr.Invoker.invoke(Invoker.java:277) ~[org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.netmgt.vmmgr.Invoker.invokeMethods(Invoker.java:206) ~[org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.netmgt.vmmgr.Starter.start(Starter.java:157) [org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.netmgt.vmmgr.Starter.startDaemon(Starter.java:95) [org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.netmgt.vmmgr.Controller.start(Controller.java:173) [org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.netmgt.vmmgr.Controller.main(Controller.java:150) [org.opennms.core.daemon-28.0.1.jar:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at org.opennms.bootstrap.Bootstrap$4.run(Bootstrap.java:531) [opennms_bootstrap.jar:?] at java.lang.Thread.run(Thread.java:829) [?:?] Caused by: java.lang.IllegalArgumentException: Each parser must be of type UdpParser but was not. at org.opennms.netmgt.telemetry.listeners.factory.UdpListenerFactory.createBean(UdpListenerFactory.java:63) ~[org.opennms.features.telemetry.listeners-28.0.1.jar:?] at org.opennms.netmgt.telemetry.listeners.factory.UdpListenerFactory.createBean(UdpListenerFactory.java:42) ~[org.opennms.features.telemetry.listeners-28.0.1.jar:?] at org.opennms.netmgt.telemetry.protocols.registry.impl.TelemetryServiceRegistryImpl.getService(TelemetryServiceRegistryImpl.java:121) ~[org.opennms.features.telemetry.registry-28.0.1.jar:?] at org.opennms.netmgt.telemetry.protocols.registry.impl.TelemetryServiceRegistryImpl.getService(TelemetryServiceRegistryImpl.java:56) ~[org.opennms.features.telemetry.registry-28.0.1.jar:?] at org.opennms.netmgt.telemetry.protocols.registry.impl.TelemetryRegistryImpl.getListener(TelemetryRegistryImpl.java:85) ~[org.opennms.features.telemetry.registry-28.0.1.jar:?] at org.opennms.netmgt.telemetry.daemon.Telemetryd.start(Telemetryd.java:141) ~[org.opennms.features.telemetry.daemon-28.0.1.jar:?] at org.opennms.netmgt.daemon.AbstractSpringContextJmxServiceDaemon$2.run(AbstractSpringContextJmxServiceDaemon.java:128) ~[org.opennms.core.daemon-28.0.1.jar:?] at org.opennms.core.logging.Logging.withPrefix(Logging.java:71) ~[org.opennms.core.logging-28.0.1.jar:?] at org.opennms.netmgt.daemon.AbstractSpringContextJmxServiceDaemon.start(AbstractSpringContextJmxServiceDaemon.java:118) ~[org.opennms.core.daemon-28.0.1.jar:?] at jdk.internal.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) ~[?:?] at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:260) ~[?:?] at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) ~[?:?] at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) ~[?:?] at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) ~[?:?] at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) ~[?:?] at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) ~[?:?] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:809) ~[?:?] ... 13 more

 

Environment

Ubuntu 20.04 also RedHat 8 on vmware virtualization vsphere ESXI 7.

Acceptance / Success Criteria

None

Attachments

29
  • 01 Sep 2021, 08:58 AM
  • 31 Aug 2021, 10:55 AM
  • 09 Aug 2021, 11:35 AM
  • 09 Aug 2021, 11:34 AM
  • 09 Aug 2021, 11:34 AM
  • 09 Aug 2021, 11:34 AM
  • 09 Aug 2021, 11:34 AM
  • 09 Aug 2021, 11:33 AM
  • 09 Aug 2021, 11:33 AM
  • 09 Aug 2021, 11:33 AM
  • 09 Aug 2021, 11:33 AM
  • 09 Aug 2021, 11:33 AM

Lucidchart Diagrams

Details

Assignee

Reporter

Labels

HB Backlog Status

Components

Affects versions

Priority

PagerDuty

Created August 9, 2021 at 11:26 AM
Updated July 26, 2023 at 2:12 PM

Activity

Jeff GehlbachAugust 2, 2022 at 9:54 PM

checking in again to inquire whether you've seen this issue in a 29.0.x or 30.0.x environment.

If you need more time to try with a newer release, please let us know. If we don't hear anything by end of August, we will assume the problem is fixed in newer releases and will close this issue.

Jeff GehlbachJune 21, 2022 at 10:12 PM

please advise whether you're still seeing this problem in current releases. We shipped 30.0.0 this month.

Jeff GehlbachMay 5, 2022 at 3:02 PM

any updates to share? It would be interesting to know whether you've seen this problem in the 29.x release series.

Dino YanceySeptember 9, 2021 at 7:17 PM
Edited

That's extremely interesting, given there are some threadpools whose size is determined dynamically by the number of CPU cores available.

 

If you make the following change to your `telemetryd-configuration.xml` on a system with 64 vCPU (or more), does it start?

[root@meridian etc]# diff -Bbw /opt/opennms/share/etc-pristine/telemetryd-configuration.xml /opt/opennms/etc/telemetryd-configuration.xml 64c64 <     <queue name="Netflow-5"> --- >     <queue name="Netflow-5" threads="16"> 76c76 <     <queue name="Netflow-9"> --- >     <queue name="Netflow-9" threads="16" > 94c94 <     <queue name="IPFIX"> --- >     <queue name="IPFIX" threads="16"> 106c106 <     <queue name="SFlow"> --- >     <queue name="SFlow" threads="16"> 142c142 <     <queue name="NXOS"> --- >     <queue name="NXOS" threads="8"> 165c165 <     <queue name="BMP"> --- >     <queue name="BMP" threads="8"> 185c185 <     <queue name="Graphite"> --- >     <queue name="Graphite" threads="8">

 

Waleed SaudSeptember 9, 2021 at 4:18 PM

I think I found the issue the VM was with 64 vCPU when I lowered it to 32 vCPU  OpenNMS  worked and didn't fail .

 

I will confirm more next week.