Server periodically drops
Have you actually checked wrapper logs to see why it stops?
Grrrr didn't saw that.
Here is it but, it didn't give me more info.
INFO|48674/0|Service traccar|18-09-11 23:27:41|Missing wrapper ping within timeout of 30000
WARNING|48674/0|Service traccar|18-09-11 23:27:42|ping between java application and wrapper timed out. if this this is due to server overload consider increasing wrapper.ping.timeout
INFO|48674/0|Service traccar|18-09-11 23:27:44|wrapper manager received stop command
INFO|48674/0|Service traccar|18-09-11 23:27:45|[Thread-16] INFO org.eclipse.jetty.server.ServerConnector - Stopped ServerConnector@245253d8{HTTP/1.1}{0.0.0.0:8084}
INFO|48674/0|Service traccar|18-09-11 23:27:45|[Thread-16] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.t.w.@2519026b{/,null,UNAVAILABLE}
INFO|48674/0|Service traccar|18-09-11 23:27:45|[Thread-16] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@35bfa1bb{/api,null,UNAVAILABLE}Timeout usually means that you don't have enough resources.
Trust me I have enough.
As I wrote. 32GB RAM ave. usage 8GB (never go to more then 15GB)
8 Cores ave. usage 20%.
I read here topic where guy had same problem and got same answer, but i had 1 GB RAM(on RPi I think) so 8 Xeon Core with 32GB RAM and 300GB SSD + 4 TB HDD is enough.
Theoretically there can be some temp traffic(too much incoming mails -> antivir scanning or some like that) but this can be only for few seconds.
Have you configured JVM to have enough memory?
No, I thought that startDaemon.sh alocate enough if there is plenty of free RAM.
You clearly haven't a "must read" guide for hosting a production grade Traccar server:
OK, I setup 3GB for maxmemory, Thanks. Will see after few days.
So, today it drops again
INFO|118660/0|Service traccar|18-09-16 12:54:22|[HikariPool-1 housekeeper] WARN com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=15m45s515ms354µs260$
INFO|118660/0|Service traccar|18-09-16 12:54:22|Missing wrapper ping within timeout of 30000
INFO|118660/0|Service traccar|18-09-16 12:54:25|[HikariPool-1 housekeeper] WARN com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=3m16s352ms465µs13ns$
WARNING|118660/0|Service traccar|18-09-16 12:54:25|ping between java application and wrapper timed out. if this this is due to server overload consider increasing wrapper.ping.timeout
INFO|118660/0|Service traccar|18-09-16 12:54:27|wrapper manager received stop command
INFO|118660/0|Service traccar|18-09-16 12:54:28|[Thread-16] INFO org.eclipse.jetty.server.ServerConnector - Stopped ServerConnector@245253d8{HTTP/1.1}{0.0.0.0:8084}
INFO|118660/0|Service traccar|18-09-16 12:54:28|[Thread-16] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.t.w.@2519026b{/,null,UNAVAILABLE}
INFO|118660/0|Service traccar|18-09-16 12:54:29|[Thread-16] INFO org.eclipse.jetty.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@35bfa1bb{/api,null,UNAVAILABLE}
INFO|wrapper|Service traccar|18-09-16 12:54:30|waitpid 118660 0
INFO|wrapper|Service traccar|18-09-16 12:54:30|exit code posix process: 0 application(status/signal): 0/0File wrapper.conf:
wrapper.java.command=java
wrapper.java.app.jar=tracker-server.jar
wrapper.java.maxmemory=3072
wrapper.app.parameter.1=./conf/traccar.xml
wrapper.java.additional.1=-Dfile.encoding=UTF-8
wrapper.logfile=logs/wrapper.log.YYYYMMDD
wrapper.logfile.rollmode=DATE
wrapper.ntservice.name=traccar
wrapper.ntservice.displayname=Traccar
wrapper.ntservice.description=Traccar
wrapper.daemon.run_level_dir=${if (new File('/etc/rc0.d').exists()) return '/etc/rcX.d' else return '/etc/init.d/rcX.d'}The issue is still the same. Your service times out.
Yeah, I can read that too. I'm asking if is that normal? Memory is set to 3GB and I have connected only one device. We plan to connect around 20 devices and it have to be stable. So I can increase memory limit, but question is, will that help? Is there chance of some memory leak or some more options to get what is wrong? I can't look at server 24h/7d for catch random services shutdown, it's impossible to catch it.
If you have only one device, I doubt that it's a memory issue.
OK, this messing my time. For save people's time tell them on start you don't want help them. It save time for you and for them.
And for clear. I searched stackoverflow and this forum for couple of days before create this topic. Tried a lot of answer and nothing help. What I want to say is that I tried to fix that for my self cause I know what it is to help people on some SW forum(mainly OSS SW). So, sorry that I missed memory setup (Again didn't think it is in RAM, cause had only one device).
You never mentioned that you have only one device. I gave you suggestion about RAM because it's the most common cause of this kind of problem. I tried to help and there is no need to be rude if you don't appreciate my help. If what I suggested didn't help you, it doesn't mean that I didn't want to help. I'm certainly not interested in wasting anyone's time.
Hi,
I have problem with traccar server running on Debian. I set-up server month ago and it periodically shutdown after few days without error message.
32GB RAM
8 Cores
SSD
See log, there is only message with "Shutting down server..." and with INFO flag! I think it should be with WARN flag if there's a problem.
I think about some watchdog which will autostart server if it drops but first I want to know there's no problem like memory leaking etc.
Any suggestion?