Service Unavailable // service just stopped

hey, my traccar service just stopped and i dont know why?

If I restarted the server manuelly its working fine and than in 2-4 days its stopped again.

last entries in the log file:

2020-04-03 00:33:24  INFO: [daf2caf9] id: 352672100069152, time: 2020-04-03 00:33:03, lat: 52.98454, lon: 9.17959, course: 0.0
2020-04-03 00:33:31  INFO: [e00158a7: gt06 < 80.187.114.38] HEX: 78781f1214040300211eca05af464300fc22a1001400010601072200b869000822fb0d0a
2020-04-03 00:33:31  INFO: [e00158a7: gt06 > 80.187.114.38] HEX: 7878051200082eec0d0a
2020-04-03 00:33:31  INFO: [e00158a7] id: 352672100069103, time: 2020-04-03 00:33:30, lat: 52.98493, lon: 9.17997, course: 0.0
2020-04-03 00:33:33  INFO: [54b7d527] timed out
2020-04-03 00:33:33  INFO: [54b7d527] disconnected
2020-04-03 00:33:35  INFO: [daf2caf9: gt06 < 80.187.98.213] HEX: 78781f12140403002121ca05af438f00fc2004001400010601072200b8690809e0020d0a
2020-04-03 00:33:35  INFO: [daf2caf9: gt06 > 80.187.98.213] HEX: 787805120809f1a50d0a
2020-04-03 00:33:35  INFO: [daf2caf9] id: 352672100069152, time: 2020-04-03 00:33:33, lat: 52.98454, lon: 9.17959, course: 0.0
2020-04-03 00:33:35  INFO: [4fa467b7: gt06 < 80.187.118.28] HEX: 78781f12140403002122cb05af440700fc1fad001400010601072200b8690a742f2b0d0a
2020-04-03 00:33:35  INFO: [4fa467b7: gt06 > 80.187.118.28] HEX: 787805120a746a770d0a
2020-04-03 00:33:35  INFO: [4fa467b7] id: 352672100068147, time: 2020-04-03 00:33:34, lat: 52.98461, lon: 9.17955, course: 0.0

Check system logs.

do you mean the server.log file under opt/traccar/logs ?

No, I'm talking about os logs.

that seems not good :

got traccar killed because of memory ussage?

Apr  3 00:29:20 vps-zap487977-1 kernel: [4194983.698032] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:29:48 vps-zap487977-1 kernel: [4195011.851841] EXT4-fs error: 3 callbacks suppressed
Apr  3 00:30:04 vps-zap487977-1 kernel: [4195027.364021] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:31:03 vps-zap487977-1 kernel: [4195086.763836] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:31:03 vps-zap487977-1 kernel: [4195086.810150] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:32:38 vps-zap487977-1 kernel: [4195181.617522] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:33:15 vps-zap487977-1 kernel: [4195218.273922] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:33:47 vps-zap487977-1 kernel: [4195250.716583] CPU: 26 PID: 6663 Comm: mysqld Tainted: P        W  O      5.3.18-1-pve #1
Apr  3 00:33:47 vps-zap487977-1 kernel: [4195250.716633]  ? __switch_to_asm+0x40/0x70
Apr  3 00:33:47 vps-zap487977-1 kernel: [4195250.716674] Memory cgroup stats for /lxc/1221443:
Apr  3 00:33:47 vps-zap487977-1 kernel: [4195250.716725] [  24396]     0 24396    23705     6535   212992        0             0 letsencrypt
Apr  3 00:33:47 vps-zap487977-1 systemd[1]: traccar.service: Main process exited, code=killed, status=9/KILL
Apr  3 00:33:47 vps-zap487977-1 systemd[1]: traccar.service: Failed with result 'signal'.
Apr  3 00:33:53 vps-zap487977-1 kernel: [4195256.825013] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:34:12 vps-zap487977-1 kernel: [4195276.055302] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:35:35 vps-zap487977-1 kernel: [4195359.116515] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:36:15 vps-zap487977-1 kernel: [4195399.225917] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:36:16 vps-zap487977-1 kernel: [4195399.311384] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:36:21 vps-zap487977-1 kernel: [4195404.602153] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:36:28 vps-zap487977-1 kernel: [4195412.210104] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:37:21 vps-zap487977-1 kernel: [4195464.522160] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:38:50 vps-zap487977-1 kernel: [4195554.033652] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:39:00 vps-zap487977-1 kernel: [4195563.255586] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:40:01 vps-zap487977-1 kernel: [4195624.503911] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:40:01 vps-zap487977-1 kernel: [4195624.518599] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:40:30 vps-zap487977-1 kernel: [4195653.710735] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:42:18 vps-zap487977-1 kernel: [4195762.075569] EXT4-fs error (device loop10): ext4_find_extent:913: inode #393377: comm systemd-journal: pblk 1611801 bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
Apr  3 00:42:44 vps-zap487977-1 kernel: [4195787.360584] EXT4-fs error: 4 callbacks suppressed

Most likely low memory.