Unable to start traccar 4.13 on our server.
My guess is that you are trying to start a second instance of Traccar.
Anton I have stopped the traccar service with following command
sudo systemctl stop traccar.service
Then i have started the traccar service with following command
sudo systemctl start traccar.service
Have you checked that the process actually stopped? Check the process list.
Hi Anton i have solved the port error. Now No error is coming is my server is running fine please help
tracker-server.log file runs fine
2021-07-30 16:20:25 INFO: HikariPool-1 - Starting...
2021-07-30 16:20:25 WARN: Registered driver with driverClassName=com.mysql.jdbc.Driver was not found, trying direct instantiation.
2021-07-30 16:20:25 INFO: HikariPool-1 - Start completed.
2021-07-30 16:20:26 INFO: Clearing database change log checksums
2021-07-30 16:20:26 INFO: Successfully acquired change log lock
2021-07-30 16:20:26 INFO: Successfully released change log lock
2021-07-30 16:20:26 INFO: Successfully acquired change log lock
2021-07-30 16:20:26 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2021-07-30 16:20:26 INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2021-07-30 16:20:29 INFO: Reading from traccar.DATABASECHANGELOG
2021-07-30 16:20:29 INFO: Reading from traccar.DATABASECHANGELOG
2021-07-30 16:20:29 INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2021-07-30 16:20:29 INFO: Successfully released change log lock
2021-07-30 16:20:31 INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2021-07-30 16:20:32 INFO: Operating system name: Linux version: 3.10.0-1127.18.2.el7.x86_64 architecture: amd64
2021-07-30 16:20:32 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.8+10-LTS
2021-07-30 16:20:32 INFO: Memory limit heap: 2934mb non-heap: 0mwrapper.log.20210730 File has some problem
INFO|wrapper|Service traccar|21-07-30 16:18:58|waitpid 6479 9
INFO|wrapper|Service traccar|21-07-30 16:18:58|exit code posix process: 9 application: 0Please help.
Where did you get wrapper from? Traccar 4.13 doesn't use it.
It's only 8 conflicting ports out of almost 200, so there might actually be services running on them.
Hemant:
Stop traccar, make absolutely sure it's not running, then try lsof -nP -i tcp. Do you see any of the ports "disabled due to conflict" in the list? If so, edit traccar/conf/default.xml and comment out those ports (<!-- before and --> after), then restart traccar. As long as traccar starts after those other services you only get a warning and you have no problem, but if traccar would start before those other services, those other services will then fail to start.
Anton:
There are some very obvious port conflicts in traccar's client port range, the worst being 5060. I think it would make sense in some future major release to move the port range up to the high unregistered ports, e.g. 55xxx or so. Another possibility would be to fingerprint the protocols and let them all come in on the same port, which could then be registered with IANA. Fingerprinting them all is a lot of work, but there are people out there inventing a new protocol every day, and you tend to add half a dozen or so in every minor release, so at this rate traccar will soon hit 65535 protocols and run out of ports.
We added about 200 in 10 years, so we will run out of ports in about 3000 years, if my calculations are correct. I understand that it was probably not a good idea to pick low numbers for ports, but changing will cause more problems than it would solve.
Here are the details, Please help