This page last changed on Jul 25, 2014 by mbuitrago.

Why does my controller not start?, free version was working fine, now purchased Pro, installed... meaning all path are set, upon "openremote start"

Could not find a controller definition to load at path '..\webapps\controller\co
ntroller.xml' (for version 2.0)
INFO 2014-07-24 21:30:39,926 : Controller Definition File Watcher for Default De
ployer started.
Jul 24, 2014 9:30:40 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8688
Jul 24, 2014 9:30:40 PM org.restlet.engine.http.connector.HttpClientHelper start

INFO: Starting the default HTTP client
Jul 24, 2014 9:30:40 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1844 ms
Jul 24, 2014 9:30:41 PM org.restlet.engine.http.connector.HttpClientHelper stop
INFO: Stopping the default HTTP client

I do not see anything in the above log that indicates the controller has not started correctly. What make you think it failed to start ?

The above log indicates that a configuration has not yet been synced with the controller (with on-line sync) or uploaded.

Please note that by default the Pro controller uses port 8688 instead of 8080 for the free.
You should then access your controller home page with URL such as http://<controller ip>:8688/controller

Posted by ebariaux at Jul 25, 2014 12:45

Hi Eric, thank you for the response.
I could not get the controller up on the browser until I changed the environment variable JAVA_HOME to JAVA_JRE... ios this a known issue?

I was mislead by the log messages that read "starting the http client......stopping the http client..." this is normal I guess?

seems to be working fine now thank you, I will report if any other issues.

Max B

Posted by mbuitrago at Jul 25, 2014 14:16
Document generated by Confluence on Jun 05, 2016 09:38