New Install Not Starting
If there are no logs, it likely means that your config is invalid.
You should better check why it is getting corrupted. It is not normal and has nothing to do with traccar server.
I have the same problem with an update from server 5.8 to 5.10. I have already done some updates without problems but with this one it does not work, the server does not start afterwards and gets stuck at the config which was still running 2 minutes before and did not cause any problems the years before. What could be the reason?
● traccar.service - traccar
Loaded: loaded (/etc/systemd/system/traccar.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2023-12-20 09:57:09 CET; 2s ago
Process: 1030 ExecStart=/opt/traccar/jre/bin/java -jar tracker-server.jar conf/traccar.xml (code=exited, status=203/EXEC)
Main PID: 1030 (code=exited, status=203/EXEC)I tried it several times because Traccar runs in a VM and I was able to revert to a working snapshot, but there was always the same problem.
What does traccar server log state?
The server log "/opt/traccar/logs" remains empty and no new logfile is created when I try to start the server.
A server log from server 5.8 looks like this.
2023-12-20 10:22:33 INFO: Operating system name: Linux version: 4.19.0-25-amd64 architecture: amd64
2023-12-20 10:22:33 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Eclipse Adoptium version: 17.0.6+10
2023-12-20 10:22:33 INFO: Memory limit heap: 988mb non-heap: 0mb
2023-12-20 10:22:33 INFO: Character encoding: UTF-8 charset: UTF-8
2023-12-20 10:22:33 INFO: Version: 5.8
2023-12-20 10:22:33 INFO: Starting server...
2023-12-20 10:22:33 INFO: HikariPool-1 - Starting...
2023-12-20 10:22:34 INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2023-12-20 10:22:34 INFO: HikariPool-1 - Start completed.
2023-12-20 10:22:35 INFO: Set default schema name to PUBLIC
2023-12-20 10:22:35 INFO: Clearing database change log checksums
2023-12-20 10:22:35 INFO: Successfully acquired change log lock
2023-12-20 10:22:35 INFO: Successfully released change log lock
2023-12-20 10:22:35 INFO: Successfully acquired change log lock
2023-12-20 10:22:37 INFO: Reading from PUBLIC.DATABASECHANGELOG
2023-12-20 10:22:38 INFO: Reading from PUBLIC.DATABASECHANGELOG
2023-12-20 10:22:38 INFO: Reading from PUBLIC.DATABASECHANGELOG
2023-12-20 10:22:38 INFO: UPDATE SUMMARY
2023-12-20 10:22:38 INFO: Run: 0
2023-12-20 10:22:38 INFO: Previously run: 43
2023-12-20 10:22:38 INFO: Filtered out: 0
2023-12-20 10:22:38 INFO: -------------------------------
2023-12-20 10:22:38 INFO: Total change sets: 43
2023-12-20 10:22:38 INFO: Update summary generated
2023-12-20 10:22:38 INFO: Successfully released change log lock
2023-12-20 10:22:38 INFO: Successfully released change log lock
2023-12-20 10:22:38 INFO: Command execution complete
2023-12-20 10:22:40 INFO: jetty-10.0.15; built: 2023-04-11T17:25:14.480Z; git: 68017dbd00236bb7e187330d7585a059610f661d; jvm 17.0.6+10
2023-12-20 10:22:40 INFO: Started o.t.w.@3611153f{/,null,AVAILABLE}
2023-12-20 10:22:40 INFO: Session workerName=node0
2023-12-20 10:22:41 WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2023-12-20 10:22:42 INFO: Started o.e.j.s.ServletContextHandler@404dc999{/,null,AVAILABLE}
2023-12-20 10:22:42 INFO: Started ServerConnector@69a373fd{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2023-12-20 10:22:42 INFO: Started Server@6f0c45f4{STARTING}[10.0.15,sto=0] @11582ms
2023-12-20 10:22:42 INFO: Health check enabled with period 480000I have now tried to install the server version 5.9 as an intermediate step and then 5.10. But already after the update to version 5.9 the server does not start anymore and no new logs are created. With 5.8 the server ran and still runs.
My config is also not very complex.
<entry key='database.driver'>org.h2.Driver</entry>
<entry key='database.url'>jdbc:h2:./data/database</entry>
<entry key='database.user'>saxxxx</entry>
<entry key='database.password'></entry>
<entry key='mail.smtp.host'>mxxxx.xxxxxxx.net</entry>
<entry key='mail.smtp.port'>465</entry>
<entry key='mail.smtp.ssl.enable'>true</entry>
<entry key='mail.smtp.from'>traccar@xxxxxxx</entry>
<entry key='mail.smtp.auth'>true</entry>
<entry key='mail.smtp.username'>traccar@xxxxxxxx</entry>
<entry key='mail.smtp.password'></entry>Run it manually and see the output. I'm pretty sure it's a configuration issue.
I use traccar all the time and I love it so much. The only thing that gets me is that I constantly have to reinstall it (debian 12 server) cause it get corrupted and stops working. Well, today was one of those days and after reinstalling it will not start. Its a fresh install of debian 12 with traccar installed and the xml configured to my working MySQL database. But I keep getting this error every time I try to start it:
There are no logs and no response from the webpage (no response). I checked MySQL and it worked fine