# Revision history [back]

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. I'm new to the ODL environment... What have I missed?

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. I'm new to the ODL environment... What have I missed?

ah, after enough patience, it appears to ask for username and password!!

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. I'm new to the ODL environment... What have I missed?

ah, after enough patience, it appears to ask for username and password!!password, allow access, display the topology, etc. ....but then I hit F5 and I'm back to the 404 error

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. I'm new to the ODL environment... What have I missed?

ah, after enough patience, it appears to ask for username and password, allow access, display the topology, etc. ....but then I hit F5 and I'm back to the 404 error

Per advice below and documentation, I tried "localhost:8181/index.html", but no luck. This comes out of the log. Any advice?

2015-06-30 12:57:52,308 | ERROR | rint Extender: 3 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container for bundle org.opendaylight.dlux.loader.implementation due to unresolved dependencies [(objectClass=org.osgi.service.http.HttpService)] java.util.concurrent.TimeoutException at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.2] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.079] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.079] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_79]

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. I'm new to the ODL environment... What have I missed?

ah, after enough patience, it appears to ask for username and password, allow access, display the topology, etc. ....but then I hit F5 and I'm back to the 404 error

Per advice below and documentation, I tried "localhost:8181/index.html", but no luck. This comes out of the log. Any advice?

2015-06-30 12:57:52,308 | ERROR | rint Extender: 3 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container for bundle org.opendaylight.dlux.loader.implementation due to unresolved dependencies [(objectClass=org.osgi.service.http.HttpService)] java.util.concurrent.TimeoutException at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.2] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.079] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.079] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_79]

### dlux web UI works with Helium, but not Lithium

I've created two instances of ODL in distinct release directories. I can start Helium (2.3) and then "feature:install odl-restconf odl-l2switch-switch odl-mdsal-apidocs odl-adsal-core odl-dlux-core odl-mdsal-xsql" and then start the dlux web interface successfully with "localhost:8181/dlux/index.html". I can see topology and things appear to work. However, if I "system:shutdown" and try that to start the web console with Lithium, I simply get an http error: 404. I even rebooted and went directly to the lithium instance, but it appears the dlux features are installed when I run "feature:list | grep dlux", but running "http:list | grep dlux" gives nothing. dlux". I'm new to the ODL environment... What have I missed?

Per advice below and documentation, I tried "localhost:8181/index.html", "localhost:8181/index.html" with Lithium (due to the restructuring), but no luck. This comes out of the log. Am I missing an update of code on which Lithium depends? Any advice?

2015-06-30 12:57:52,308 | ERROR | rint Extender: 3 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container for bundle org.opendaylight.dlux.loader.implementation due to unresolved dependencies [(objectClass=org.osgi.service.http.HttpService)] java.util.concurrent.TimeoutException at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.2] at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.079] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.079] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_79]