No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.core

Setup, Configuration and Use Runtime
1

For all bundles I get the following message after upgrading to the latest snapshot of today.

  • Platform information:
    • Hardware: Raspberry PI 3
    • OS: openhabian
    • Java Runtime Environment: openjdk version “1.8.0_152”
    • openHAB version: openHAB 2.2.0 Build #1099
  • Issue of the topic:
    • The issue is that I get a lot of INFO as seen in the log below.
  • If logs where generated please post these here using code fences:
2017-11-30 17:18:58.515 [INFO ] [org.knowm.yank.YankPoolManager      ] - Initialized pool 'yank-default'
2017-11-30 17:19:04.271 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.openhab.persistence.jdbc
2017-11-30 17:19:04.276 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.persistence.jdbc
2017-11-30 17:19:05.280 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.openhab.persistence.mapdb
2017-11-30 17:19:05.285 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.persistence.mapdb
2017-11-30 17:19:05.381 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.openhab.persistence.mqtt
2017-11-30 17:19:05.385 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.persistence.mqtt

And this goes on for all other bundles as well.

2017-11-30 17:19:06.044 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-11-30 17:19:06.086 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.openhab.ui.habpanel
2017-11-30 17:19:06.089 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.ui.habpanel
2017-11-30 17:19:06.497 [INFO ] [vice.internal.HttpServiceFactoryImpl] - Binding bundle: [org.openhab.core_2.2.0.201711260007 [190]] to http service
2017-11-30 17:19:06.539 [INFO ] [rg.ops4j.pax.web.utils.ClassPathUtil] - Ignoring bundle scan for /META-INF/services javax.servlet.ServletContainerInitializer.
2017-11-30 17:19:06.590 [INFO ] [ce.jetty.internal.HttpServiceContext] - registering context DefaultHttpContext [bundle=org.openhab.core_2.2.0.201711260007 [190], contextID=default], with context-name: 
2017-11-30 17:19:06.632 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=DefaultHttpContext [bundle=org.openhab.core_2.2.0.201711260007 [190], contextID=default]}
2017-11-30 17:19:08.653 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - Bundle Considered for SPI providers: org.openhab.core
2017-11-30 17:19:08.660 [INFO ] [g.apache.aries.spifly.dynamic.bundle] - No 'SPI-Provider' Manifest header. Skipping bundle: org.openhab.core

The last lines above are the last lines in the openhab.log and whatever I do in any of the UI’s nothing happens or gets added to the log.

And below some info from openhab-cli.

Version:        2.2.0-SNAPSHOT (#1099)
User:           openhab (Active Process 5364)
User Groups:    openhab tty dialout gpio

Directories:    Folder Name      | Path                           | User:Group
                -----------      | ----                           | ----------
                OPENHAB_HOME     | /usr/share/openhab2            | openhab:openhab
                OPENHAB_RUNTIME  | /usr/share/openhab2/runtime    | openhab:openhab
                OPENHAB_USERDATA | /var/lib/openhab2              | openhab:openhabian
                OPENHAB_CONF     | /etc/openhab2                  | openhab:openhabian
                OPENHAB_LOGDIR   | /var/log/openhab2              | openhab:openhabian

Dashboard URLs: http://192.168.1.13:8080
                https://192.168.1.13:8443

The result is that OpenHAB does not receive any data from my things and cannot send commands to my things.

Thanks in advance.

2

Hey Rob,
This is not an issue per say - this is just a log statement which ended up with wrong level. Aries SPI FLY is kind of classpath scanner which tries to link some items. You can safely mute it via:
log:set WARN org.apache.aries.spifly

@maggu2810 - As far I remember OH worked just fine without spi-fly so far, can you confirm?

3

I can not confirm that it works as intended. The system does not work at all.

4

Dear Rob,
Issue might come from other error which could not get logged. Do you have any messages with ERROR or WARN levels?

5

I found out that when I removed the following packages from my addons folder it now starts and works as intended.

-rw-rw-r-- 1 openhabian openhabian   66790 Sep  8 02:47 jackson-annotations-2.9.1.jar
-rw-rw-r-- 1 openhabian openhabian  320612 Sep  8 02:48 jackson-core-2.9.1.jar
-rw-rw-r-- 1 openhabian openhabian 1329588 Sep  8 03:10 jackson-databind-2.9.1.jar
-rw-rw-r-- 1 openhabian openhabian   33282 Jun  8 15:09 org.openhab.binding.unifi-2.1.0-SNAPSHOT.jar
-rw-rw-r-- 1 openhabian openhabian   98882 Nov 29 10:51 org.openhab.ui.iconset.climacons-2.2.0-SNAPSHOT.jar

So now my Unifi binding does not work but that’s the next thing I will try adding to the folder again.

6

So I have placed the latest Unifi binding and, without the jackson jars, it works!

7

Hi @splatch, sorry I don’t look normally into that forum.
I also don’t use openHAB myself, but AFAIK it never used SPI Fly.