Opennms 28.0.1 fails after start related to telemetryd problem
Description
Opennms 28.0.1 fails after start related to telemetryd problem
Environment
Ubuntu 20.04 also RedHat 8 on vmware virtualization vsphere ESXI 7.
Acceptance / Success Criteria
None
Attachments
29
Lucidchart Diagrams
Activity
Show:
Jeff Gehlbach August 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 Gehlbach June 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 Gehlbach May 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 Yancey September 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?
Waleed Saud September 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 .
Opennms 28.0.1 fails after start related to telemetryd problem