Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-9331

BestMatchPinger fails to initialize when IPv6 is not available

    XMLWordPrintable

Details

    • Story
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • 19.0.0, 19.0.1, 19.1.0
    • 20.0.0, 20.0.1
    • Architecture
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon - May 10th, Horizon - May 17th

    Description

      Excerpt from chat:

      twiki
      10:51 AM
      irc <markw78> Not able to start v19... getting this error
      10:51 AM
      irc <markw78> Caused by: java.net.SocketException: System error creating ICMPv6 socket (97, Address family not supported by protocol)
      10:52 AM
      irc <markw78> I have tried setting opennms.properties with these set to auto, and now this... but still get this error on startup
      10:52 AM
      irc <markw78> org.opennms.netmgt.icmp.requireV4=true
      10:52 AM
      irc <markw78> org.opennms.netmgt.icmp.requireV6=false
      	
      rangerrick
      11:28 AM
      markw78: so you don't have IPv6 at all? I think I still have some bugs in the pinger autoconfiguration
      11:29 AM
      if you want to force v4-only you should uncomment org.opennms.netmgt.icmp.pingerClass=org.opennms.netmgt.icmp.jni.JniPinger in opennms.properties
      11:29 AM
      or if you do have V6 and it's just weirding out, try uncommenting and explicitly setting it to the Jni6 one
      	
      twiki
      11:45 AM
      irc <markw78> no ipv6 at all on this box
      	
      twiki
      11:56 AM
      irc <markw78> Success!  Thank you!
      

      Attachments

        Activity

          People

            ranger Benjamin Reed
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: