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

Minion fails to start on Raspberry Pi

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 23.0.0, 24.0.0, 25.0.0
    • Fix Version/s: 25.1.0
    • Component/s: Minion
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Raspberry Pi 3 B+
    • Sprint:
      Horizon 2019 - October 16th, Horizon 2019 - October 23rd

      Description

      Not sure if this is the right place for this.

       

      I'm installing Minion on a Raspberry Pi and getting an error. I can install it, log on to Karaf the first time and configure the Minion. When I try launch the minion afterwards, Karaf fails to launch.

      Log in /var/log/minion/minion.log shows the following error:
      2018-11-13T12:50:32,089 | ERROR | ForkJoinPool.commonPool-worker-1 | KarafExtender | 104 - org.opennms.container.extender - 23.0.0 | Failed to install one or more features.
      org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=minion-provisiond-detectors; type=karaf.feature; version="[23.0.0,23.0.0]"; filter:="(&(osgi.identity=minion-provisiond-detectors)(type=karaf.feature)(version>=23.0.0)(version<=23.0.0))" [caused by: Unable to resolve minion-provisiond-detectors/23.0.0: missing requirement [minion-provisiond-detectors/23.0.0] osgi.identity; osgi.identity=opennms-icmp-best; type=karaf.feature [caused by: Unable to resolve opennms-icmp-best/23.0.0: missing requirement [opennms-icmp-best/23.0.0] osgi.identity; osgi.identity=opennms-icmp-jna; type=karaf.feature [caused by: Unable to resolve opennms-icmp-jna/23.0.0: missing requirement [opennms-icmp-jna/23.0.0] osgi.identity; osgi.identity=org.opennms.opennms-icmp-jna; type=osgi.bundle; version="[23.0.0,23.0.0]"; resolution:=mandatory [caused by: Unable to resolve org.opennms.opennms-icmp-jna/23.0.0: missing requirement [org.opennms.opennms-icmp-jna/23.0.0] osgi.wiring.package; filter:="(osgi.wiring.package=com.sun.jna)" [caused by: Unable to resolve com.sun.jna [11](R 11.0): missing requirement [com.sun.jna [11](R 11.0)] osgi.native; (|(&(osgi.native.osname~=win32)(osgi.native.processor~=x86))(&(osgi.native.osname~=win32)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=win)(osgi.native.processor~=x86))(&(osgi.native.osname~=win)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=wince)(osgi.native.processor~=arm))(&(osgi.native.osname~=sunos)(osgi.native.processor~=x86))(&(osgi.native.osname~=sunos)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=sunos)(osgi.native.processor~=sparc))(&(osgi.native.osname~=sunos)(osgi.native.processor~=sparcv9))(&(osgi.native.osname~=aix)(osgi.native.processor~=ppc))(&(osgi.native.osname~=aix)(osgi.native.processor~=ppc64))(&(osgi.native.osname~=linux)(osgi.native.processor~=ppc))(&(osgi.native.osname~=linux)(osgi.native.processor~=ppc64))(&(osgi.native.osname~=linux)(osgi.native.processor~=ppc64le))(&(osgi.native.osname~=linux)(osgi.native.processor~=x86))(&(osgi.native.osname~=linux)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=linux)(osgi.native.processor~=arm))(&(osgi.native.osname~=linux)(osgi.native.processor~=armel))(&(osgi.native.osname~=linux)(osgi.native.processor~=aarch64))(&(osgi.native.osname~=linux)(osgi.native.processor~=ia64))(&(osgi.native.osname~=linux)(osgi.native.processor~=sparcv9))(&(osgi.native.osname~=freebsd)(osgi.native.processor~=x86))(&(osgi.native.osname~=freebsd)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=openbsd)(osgi.native.processor~=x86))(&(osgi.native.osname~=openbsd)(osgi.native.processor~=x86-64))(&(osgi.native.osname~=macosx)(|(osgi.native.processor~=x86)(osgi.native.processor~=x86-64)(osgi.native.processor~=ppc))))]]]]]
          at org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42) ~[?:?]
       
      Not sure if this is important, but before that the log is saying that it cannot validate file integrity from the repositories folder
       

        Attachments

          Activity

            People

            • Assignee:
              mbrooks Matthew Brooks
              Reporter:
              jason-gatebook Jason Phillips
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: