This page last changed on Feb 26, 2015 by yannph.
I've recently upgraded to Controller 2.1.1 and I'm facing a new behavior.
When starting the Controller or when reloading it (sync with the designer), the Controller is taking up to 5 minutes to be ready.
My panels (on iOS, Android or WebConsole) are waiting in a kind of "loading" loop. It's like they are starting the loading process more than 10 times before after the panel loaded.
Having a look at the dev.log, I've found this exception reoccuring more than 10 times:
2015-02-21 17:22:02,241 ERROR [HTTP-Thread-13]: CommandException occurs
org.openremote.controller.config.ControllerXMLChangedException: The content of controller.xml had changed.
The panels, design haven't change. only the Controller.
Any luck with this?
I'm experiencing what looks to be the same issue. Dev log has the same error, and panels on iOS devices are stuck in loading loops.
Posted by frand at Mar 25, 2015 20:00
Unfortunatly not, no solution, no support, don't know where to start from ...
Hopefully, I'm not the only one with this issue
Wait and see, may be the community or the support will react
Posted by yannph at Mar 26, 2015 18:45
I fixed the situation on my end, but I can't account the solution to a single step. It's even stranger because the installation was running fine for about a month before breaking itself, and normal re-installing did not help.
Here are things that I went through (the installation is running on a raspi2):
- Installed jre8 security package to fix an identity fetching error
- Noted knx connectivity issues in dev log, these may be related to rebooting the system too quickly in succession
- Removed virtual sensors that were giving error messages due to hardware that's no longer connected
- Fixed some buttons in the UI panels that were connected to status sensors that weren't giving proper output
As said, none of the issues above were showstoppers before, but after cleaning up the setup for a couple of hours it just so happened that after one of the tweak&reboot cycles the boot log showed a successful startup and things are back to normal again.
So all I can say is I hope you find something fishy in your boot.log or dev.log that can be fixed with similar steps. Let me know if you need some more details.
Posted by frand at Mar 27, 2015 05:46
The above exception is not the cause of the problem, but rather a "side effect".
It's an exception that occurs when a panel makes a request to the controller while its configuration is being updated (in this case, it's a request for a sensor value).
If your configuration update takes a really long time (like 5 or 10 min), then it's normal that the console would regularly poll for e.g. sensor values and that you're seeing the exception multiple times.
Are there any other logs in the controller that show something usual / changed from before ?
Posted by ebariaux at Mar 30, 2015 11:32