I am getting there to finish everything with
openremote, velbus and beaglebone black server in my house. (well, for now, i
think)
But near the finish line, I am getting in some
trouble. And I cannot find the solution. Can you please help me?
About a week ago there was a fuse broken. It had
nothing to do with my smart home system. But the power of the velbus and the
server was down.
That should not be a problem, because the power of
both devices have been of many times.
The
problem: Afterwards I found out that I cannot access the
controller of the openremote anymore.
I cannot access the controller OR app. I cannot access
the controller to update. The rules for openremote do not work.
What I tested:
The logs in openremote do not show anything since
the fuse broke. Nothing good or bad is logged. Not in boot.log ,
drools,log and not in velbus.log.
If I connect via the velbus software on a separate
PC via the server to the velbus, that works. It is fully functional, no
problems.
So, I think velserv program is running perfectly.
The velbus system (seperate of openremote) works perfect.
I did not change anything to openremote around
that time or afterwards.
I can connect to the server via ssh
On my server the programs Velserv and openremote
are started via the same file on startup. If I list the current processes
on the server, it shows that that same file is working.
I tried to reboot via ssh with reboot , and tried to restart with
power on and off. I tried to wait
long (up to 3 days ) and short. That all did not work
I tried to just start openremote on the server.
That did now work
I am not sure what to do, nor what information I can
give to help.
It seems that the controller is running but somehow it does not communicate with the outside world. To diagnose it further you can go to the /opt/OpenRemote-Controller/bin directory, stop the service ./openremote.sh stop and run it from the command line ./openremote.sh run. This way it will dump all output to the terminal and perhaps you can spot what is blocking it?
Thank you. The resulting output can be summarized as this:
Jan 08, 2019 5:29:13 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/OpenRemote-Controller/webapps/controller/WEB-INF/lib/native
Jan 08, 2019 5:29:14 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8688
Jan 08, 2019 5:29:14 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3986 ms
Jan 08, 2019 5:29:14 PM org.apache.tomcat.util.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 1 column 1: Premature end of file.
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Premature end of file.
It says something about missing folder or file called native. There is indeed none on that destination. But in old backups I cannot find such a folder or file either.
) and short. That all did not work