hello I have approximately 20 days to update traccar to version 4.2, today I realize that the service was shut down twice and this is what I sent in my logs
root@FCB6BDA:/opt/traccar/logs# tail tracker.server.log
tail: cannot open 'tracker.server.log' for reading: No such file or directory
root@FCB6BDA:/opt/traccar/logs# tail tracker-server.log
2018-11-30 14:34:59 WARN: Too many open files - IOException (...)
2018-11-30 14:34:59 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2018-11-30 14:35:00 WARN: Too many open files - IOException (...)
2018-11-30 14:35:00 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2018-11-30 14:35:01 WARN: Too many open files - IOException (...)
2018-11-30 14:35:01 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2018-11-30 14:35:02 WARN: Too many open files - IOException (...)
2018-11-30 14:35:02 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
2018-11-30 14:35:03 WARN: Too many open files - IOException (...)
2018-11-30 14:35:03 WARN: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. - Too many open files - IOException (...)
root@FCB6BDA:/opt/traccar/logs# tail tracker-server.log
I'm not sure if the solution is the same that I find here: https://www.traccar.org/optimization/
could guide me
Why are you not sure? Have you tried the solution?
I have not tried the solution but I did not think the problem was there because I have a server with 1TB on disk and 16GB of memory and less than 30 devices configured in traccar I think there were very few to generate this problem
Even one device can potentially cause this issue. If you carefully read the documentation, you will understand that it has nothing to do with amount of disk space or memory you have.
ok very well, thank you very much implement the solution.
Hello Anton again, implement the solutions of ru documentation but I keep opting the same error and the service of traccar goes down I have to stop and start traccar.service so that some advice works again?
I was checking and apparently traccar is responding to all requests with a http 429 has happened to them?
Do you know how to correct this?
hello I have approximately 20 days to update traccar to version 4.2, today I realize that the service was shut down twice and this is what I sent in my logs
I'm not sure if the solution is the same that I find here: https://www.traccar.org/optimization/
could guide me