Error Installing Boot Features / Caused by: org.osgi.framework.BundleException: Exception in org.openhab.io.jetty.certificate.internal.CertificateGenerator.start() of bundle org.openhab.io.jetty.certificate.

[carpenike]

Error Installing Boot Features / Caused by: org.osgi.framework.BundleException: Exception in org.openhab.io.jetty.certificate.internal.CertificateGenerator.start() of bundle org.openhab.io.jetty.certificate.

[dvanherbergen]

When openHAB starts, it tries to generate a new certificate to be used for https. This generation is done through the bouncycastle library. I'm not sure why it is failing, maybe this is because you are using the openJDK in stead of Oracle JDK.

As a workaround, you can manually add a certificate to the keystore (userdata/etc/keystore) or replace the keystore with the one from here:
https://github.com/openhab/openhab-distro/tree/master/launch/home/etc. That one already contains a certificate.

[kaikreuzer]

Is the root cause not available in the log? That's a pity.
Besides OpenJDK, the reason could be some other pre-requisite. Maybe it requires libbcprov-java like in http://stackoverflow.com/a/4743435?

[carpenike]

Thanks. I'll install Oracle's JDK and retry.

1.8 should work fine though, right?

[kaikreuzer]

1.8 should work fine though, right?

Yes!

[carpenike]

Oracle's JDK works much better! Only error on first start that I get is now:

13:08:19.149 [ERROR] [.wemo.discovery.WemoDiscoveryService] - Could not send Wemo device discovery
java.net.BindException: Cannot assign requested address
        at java.net.PlainDatagramSocketImpl.bind0(Native Method)[:1.8.0_65]
        at java.net.AbstractPlainDatagramSocketImpl.bind(AbstractPlainDatagramSocketImpl.java:94)[:1.8.0_65]
        at java.net.DatagramSocket.bind(DatagramSocket.java:392)[:1.8.0_65]
        at org.eclipse.smarthome.binding.wemo.discovery.WemoDiscoveryService.sendWemoDiscoveryMessage(WemoDiscoveryService.java:152)[145:org.eclipse.smarthome.binding.wemo:0.8.0.201601082233]
        at org.eclipse.smarthome.binding.wemo.discovery.WemoDiscoveryService.discoverWemo(WemoDiscoveryService.java:120)[145:org.eclipse.smarthome.binding.wemo:0.8.0.201601082233]
        at org.eclipse.smarthome.binding.wemo.discovery.WemoDiscoveryService.access$0(WemoDiscoveryService.java:118)[145:org.eclipse.smarthome.binding.wemo:0.8.0.201601082233]
        at org.eclipse.smarthome.binding.wemo.discovery.WemoDiscoveryService$1.run(WemoDiscoveryService.java:79)[145:org.eclipse.smarthome.binding.wemo:0.8.0.201601082233]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_65]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_65]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
        at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]

[kaikreuzer]

Could you please report this at https://github.com/eclipse/smarthome/issues? (this is where the WeMo binding is maintained)