DROPBOX IO needed for OpenHAB Designer sync. NOT SHOWING IN OPENHAB.LOG

I love the idea of being able to synchronise the Openhab folder with DROPBOX in order to use OpenHAB Designer on my server, but I’m finding great difficulty getting the DROPBOX IO addon integrated. I haven’t ever seen the “o.o.i.d.i.DropboxSynchronizer” entries described in https://github.com/openhab/openhab/wiki/Dropbox-IO in the openhab log file, even though I’ve put the DROPBOX add-on in the add-ons folder

And added the dropbox:initialize=true line into the config file


All help gratefully received.

Could the problem seems to be that port 8080 is already in use for some reason? I hesitate to suggest this because the OpenHAB functionality works OK. Here is first entry in openhab.log on issuing command “sudo sh openhab/start.sh”:

2016-02-29 20:18:29.835 [WARN ] [.u.component.AbstractLifeCycle] - FAILED SelectChannelConnector@0.0.0.0:8080: java.net.BindException: Address already in use
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_72]
at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_72]
at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_72]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[na:1.8.0_72]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[na:1.8.0_72]
at org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:182) ~[org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:311) ~[org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:260) ~[org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) [org.eclipse.jetty.util_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.server.Server.doStart(Server.java:273) [org.eclipse.jetty.server_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) [org.eclipse.jetty.util_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.osgi.boot.internal.serverfactory.ServerInstanceWrapper.start(ServerInstanceWrapper.java:166) [org.eclipse.jetty.osgi.boot_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.jetty.osgi.boot.internal.serverfactory.JettyServerServiceTracker.serviceChanged(JettyServerServiceTracker.java:112) [org.eclipse.jetty.osgi.boot_8.1.3.v20120522.jar:8.1.3.v20120522]
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]

...

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) [org.eclipse.osgi_3.8.2.v20130124-134944.jar:na]

That is indeed the what that error means. I’m sorry I have nothing else to offer in terms of trouble shooting.

I’m wondering if the 8080 port is a red herring, especially as I can log on
OK. I’ve tried using the dropbox addon version 1.7.0 that was published for
my version of OpenHAB (1.7.1), but still do not see the dropbox entries in
my openhab.log file :^(

It might not be openHAB’s 8080 port that it is complaining about. I could see cases where there would be a binding that opens its own ports. There is also port 8442 and 5555 which openHAB opens and those could be causing the error as well. If there is a conflict on any of those ports you will see a binding exception.

Thank you, that’s interesting. I’m not seeing any more problem with port 8080 now. I believe I had a second instance of openhab running and have resolved that now by killing the right process.

I would still very much like to get the DROPBOX IO sync working. It seems most strange that I get none of the expected entries in the log file that are promised in the guide to the binding (extract from https://github.com/openhab/openhab/wiki/Dropbox-IO below).

Could it be that there is something not listed in the steps described in the guide that the binding relies on for start up, and that is missing from my configuration? I think that could be why I don’t see the synchronizer entries:

Step 2 is issued by openHAB automatically on startup. You will find some log entries (also in the console) like this:

17:04:35.375 INFO o.o.i.d.i.DropboxSynchronizer[:202] - #########################################################################################
17:04:35.376 INFO o.o.i.d.i.DropboxSynchronizer[:203] - # Dropbox-Integration: U S E R I N T E R A C T I O N R E Q U I R E D !!
17:04:35.376 INFO o.o.i.d.i.DropboxSynchronizer[:204] - # 1. Open URL 'https://www.dropbox.com/1/oauth2/authorize?locale=en_US&client_id=gbrwwfzvrw6a9uv&response_type=code
17:04:35.376 INFO o.o.i.d.i.DropboxSynchronizer[:205] - # 2. Allow openHAB to access Dropbox
17:04:35.376 INFO o.o.i.d.i.DropboxSynchronizer[:206] - # 3. Paste the authorisation code here using the command 'finishAuthentication “”'
17:04:35.376 INFO o.o.i.d.i.DropboxSynchronizer[:207] - #########################################################################################

If you don’t see what the wiki pages tells you what you should see at startup the problem is almost certainly that the binding is not installed correctly. Verify that you have the right jar file for the binding in your addons folder. If you do, try downloading and installing it again in case it got corrupted the first time (unlikely but it has happened).

Thank you, Rich for your really speedy and helpful replies. That was indeed the problem. I had selected the wrong dropbox IO binding. Now it matches, the authentication code is available. Just waiting for the synchronisation to begin. Good stuff.

Interesting to see OpenHAB is seen as a Samsung device! It was worth making this DROPBOX connection because my labours have been rewarded with a lot more free space to develop the configuration some more and store those log files: