Server periodically drops

I posted you log file. And yes I can read so I known it's same issue. For your certainty that I really setup 3GB RAM I posted config file. You answered "it still same issue".How this answer can help me, or push me forward to debug problem, everyone see that's still same issue? So I ask you if is more ways to debug porlem. And you answer that is not memory issue. That's second time you send something what everyone can see but without some point to next debug step. So that's why I got this filling. And this way messing my and your time. I want to solve it quickly cause I don't want to waste YOUR time, but you don't helping me with that.

If you are using Java higher than 8, try downgrading to 8.

I that doesn't help, I don't have any other ideas, so without actually checking your system I won't be able to help any further.

Thanks for suggestion. I have installed openjdk-8.

For more info, here is daemon startup:

++++++++++ YAJSW SET ENV ++++++++++
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-1~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
wrapper home : /opt/traccar
configuration: /opt/traccar/conf/wrapper.conf
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-1~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
---------- YAJSW SET ENV ----------
++++++++++ YAJSW SET ENV ++++++++++
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-1~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
wrapper home : /opt/traccar
configuration: /opt/traccar/conf/wrapper.conf
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-8u181-b13-1~deb9u1-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
---------- YAJSW SET ENV ----------
YAJSW: yajsw-stable-12.12
OS   : Linux/4.9.0-7-amd64/amd64
JVM  : Oracle Corporation/1.8.0_181//usr/lib/jvm/java-8-openjdk-amd64/jre/64
Zář 18, 2018 10:20:21 DOP. org.apache.commons.vfs2.VfsLog info
INFO: Using "/tmp/vfs_cache" as temporary files store.
Zář 18, 2018 10:20:21 DOP. org.rzo.yajsw.os.posix.PosixService init
INFO: /etc/init.d/traccar already exists
************* STARTING traccar ***********************

Zář 18, 2018 10:20:21 DOP. org.rzo.yajsw.os.posix.PosixService getPid
INFO: wrapper pid file: /run/wrapper.traccar.pid
Zář 18, 2018 10:20:26 DOP. org.rzo.yajsw.os.posix.PosixService start
INFO: Starting traccar ...
YAJSW: yajsw-stable-12.12
OS   : Linux/4.9.0-7-amd64/amd64
JVM  : Oracle Corporation/1.8.0_181//usr/lib/jvm/java-8-openjdk-amd64/jre/64
************* STARTING traccar ***********************

Service traccar started

Zář 18, 2018 10:20:26 DOP. org.rzo.yajsw.os.posix.PosixService getPid
INFO: wrapper pid file: /run/wrapper.traccar.pid
Zář 18, 2018 10:20:27 DOP. org.rzo.yajsw.os.posix.PosixService getPid
INFO: wrapper pid file: /run/wrapper.traccar.pid
Zář 18, 2018 10:20:27 DOP. org.rzo.yajsw.os.posix.PosixService getPid
INFO: wrapper pid file: /run/wrapper.traccar.pid
Service traccar started

I found this in syslog, same time as timeout throw in wrapper log

Sep 16 12:54:22 buffon kernel: [2697429.125079] sd 0:0:1:0: [sdb] tag#0 task abort on host 0, ffff95a091e0fb00
Sep 16 12:54:22 buffon kernel: [2697429.126195] sd 0:0:1:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Sep 16 12:54:22 buffon kernel: [2697429.126437] sd 0:0:1:0: [sdb] tag#0 CDB: Write(10) 2a 00 0f 52 9f c0 00 00 40 00
Sep 16 12:54:22 buffon kernel: [2697429.126926] blk_update_request: I/O error, dev sdb, sector 257073088

And I forgot. This debian runs in VMWare as guest system.

I/O error usually indicates disk error.

Yeah, I know, but it's virtual disk and I don't know if it cause traccar timeout. VMWare saying that physical(SSD) disk where virtual disk's file is placed is OK without problem. Do you think that increase timeout interval can help? Because dovecot, postfix, apache, seafile(cloud server like dropbox), keep running without any problems.

It doesn't usually help, but you can try if you want.

So I did, will see. But I just saw in htop that there're two traccar process and one have 8.9 GB virt. memory and second one have 11.4 GB virt. memory, is that normal?

root      45502  1.2  0.2 11984440 93320 pts/0  Sl   11:26   0:05 java -Dwrapper.pidfile=/run/wrapper.traccar.pid
root      45527  8.3  1.2 8989532 397784 ?      Ssl  11:26   0:36 java -classpath /opt/traccar/wrapperApp.jar:/opt/traccar/tracker-server.jar

Real memory usage seems pretty low, so I wouldn't worry about that.

Did some research and found wrapper.ping.timeout.action. Manual saying theres default action RESTART is it same in traccar? So I expect it will restart not only shutdown. There is possible to combine action so I can try to use DEFAULT value with DEBUG it should dump some info, or not? I'm not java developer so I don't know how this works.

Try running it manually without Wrapper and see if it works.

Hmmm, that sounds good. To the record I run it by this command under /opt/traccar/

sudo nohup java -Xmx3072m -jar ./tracker-server.jar ./conf/traccar.xml &

And I see in nohup.out big verbosity, maybe it can help for debug.

Hi, I can confirm that, using command posted in last message works. I have uptime around 5 months. Thanks for help