The service dies with "LockException".
- It looks like you are using web port (8082) for the Traccar Client app. It's incorrect.
- Your log shows that the database got locked. You have to unlock it before proceeding. Search forum for more details.
- As I mentioned earlier in another conversation, "Traccar" uses a huge number of ports and processes and I never got an explanation why. As for your statement that "8082" is incorrect please see this row from "default.xml":
<entry key='web.port'>8082</entry>
- What database? Would unlocking resolve the issue? What causes the lock?
Most of the questions you are asking were already discussed and answered on the forum. Probably more than once. If you are looking for explanations and details - search.
I went through all the search results for "lockexception" and found nothing useful. What I did find whas you mentioning multiple times as if this topic had been discussed for many times. I think we both can draw a conclusion here that if something has to be had discussed for multiple times something is terribly wrong: either the software not admin-friendly or user manual not clear enough. I suggest for you to rebuild the software so that anybody can run it without messing around with database locks. These locks should be handled from inside the software itself. I couldn't imagine to release a software that has issues with database locks if the database isn't used from outside the software.
However, I tried this because in one of the search results was this suggestion:
kalmer@test:/opt/traccar$ java -cp lib/h2*.jar org.h2.tools.Shell -url “jdbc:h2:/opt/traccar/data/database” -user sa
Exception in thread "main" java.sql.SQLException: No suitable driver found for “jdbc:h2:/opt/traccar/data/database”
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:702)
at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:228)
at org.h2.tools.Shell.runTool(Shell.java:148)
at org.h2.tools.Shell.main(Shell.java:81)
As you see it lead me to another error message instead of solving anything.
I put "traccar" on hold until I get clear instructions. I don't want to afford growing "nginx" logs just because the smartphone client tries to connect it every five minutes and then, the service is just down. And "nginx" redied today.
Please see the bug report at https://github.com/traccar/traccar-web/issues/811. tananaev claims it not to have anything to do with the web app and suggested to ask here.