error - Connection reset by peer - IOException (...)

I use Unraid and I am running Traccar Docker Version 4.11 and I am using MariaDB Version 10.4.16 in another docker for the database.

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is #####
Server version: 10.4.16-MariaDB-1:10.4.16+maria~bionic-log mariadb.org binary distribution

At this point, I only have two iPhones connected to the server via the Traccar Client app for testing purposes. I just connected the second client today and I am now receiving error - Connection reset by peer - IOException (...) in the logs every time my device connects. Yesterday, when only my client was connected, I did not have this problem. Also, the server has not been up for very long. I connected my first client about a week ago and I just created the database 2 days ago.

Actually, as I type this, I received a new error in the logs that I have not seen before. WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@26b1c55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value. The full logs are at the end of this post.

Here are the log files from the server:

2020-11-12 09:02:43  INFO: [46904558] connected
2020-11-12 09:02:43  INFO: [46904558: osmand < 198.233.237.1] HEX: 504f5354202f3f69643d363830353735352674696d657374616d703d31363035323030353632266c61743d34372e363130323532266c6f6e3d2d3132322e3332393534322673706565643d302662656172696e673d3026616c7469747564653d39312e35393539323731353230353534382661636375726163793d32392e333436343130353338383131333426626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:02:43  INFO: [46904558: osmand > 198.233.237.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:02:43  INFO: [46904558] id: 6805755, time: 2020-11-12 09:02:42, lat: 47.61025, lon: -122.32954, course: 0.0, accuracy: 29.3
2020-11-12 09:02:43  WARN: [46904558] error - Connection reset by peer - IOException (...)
2020-11-12 09:02:43  INFO: [46904558] disconnected
2020-11-12 09:06:59  INFO: [0877220a] connected
2020-11-12 09:06:59  INFO: [0877220a: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323030383139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33352e37383336353730373339373436312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:06:59  INFO: [0877220a] id: 277587, time: 2020-11-12 09:06:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:07:29  INFO: [0877220a] disconnected
2020-11-12 09:07:43  INFO: [5c28e276] connected
2020-11-12 09:07:43  WARN: [5c28e276] error - Connection reset by peer - IOException (...)
2020-11-12 09:07:43  INFO: [5c28e276] disconnected
2020-11-12 09:11:59  INFO: [8d553a07] connected
2020-11-12 09:11:59  INFO: [8d553a07: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031313139266c61743d34372e353430373737266c6f6e3d2d3132322e3237313033392673706565643d302662656172696e673d3026616c7469747564653d33362e35383232343130353833343936312661636375726163793d313026626174743d383320485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:11:59  INFO: [8d553a07] id: 277587, time: 2020-11-12 09:11:59, lat: 47.54078, lon: -122.27104, course: 0.0, accuracy: 10.0
2020-11-12 09:12:29  INFO: [8d553a07] disconnected
2020-11-12 09:12:44  INFO: [ba5083df] connected
2020-11-12 09:12:44  WARN: [ba5083df] error - Connection reset by peer - IOException (...)
2020-11-12 09:12:44  INFO: [ba5083df] disconnected
2020-11-12 09:17:00  INFO: [bb2ec03b] connected
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031343230266c61743d34372e353430373932266c6f6e3d2d3132322e3237313039332673706565643d302662656172696e673d3026616c7469747564653d34312e34353432353033333536393333362661636375726163793d313026626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:17:00  INFO: [bb2ec03b] id: 277587, time: 2020-11-12 09:17:00, lat: 47.54079, lon: -122.27109, course: 0.0, accuracy: 10.0
2020-11-12 09:17:30  INFO: [bb2ec03b] disconnected
2020-11-12 09:17:45  INFO: [579705fe] connected
2020-11-12 09:17:45  WARN: [579705fe] error - Connection reset by peer - IOException (...)
2020-11-12 09:17:45  INFO: [579705fe] disconnected
2020-11-12 09:22:00  INFO: [fb6fa746] connected
2020-11-12 09:22:00  INFO: [fb6fa746: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323031373230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e33363935303237323333343438332661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:22:00  INFO: [fb6fa746] id: 277587, time: 2020-11-12 09:22:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:22:30  INFO: [fb6fa746] disconnected
2020-11-12 09:22:46  INFO: [2a96a2d7] connected
2020-11-12 09:22:46  WARN: [2a96a2d7] error - Connection reset by peer - IOException (...)
2020-11-12 09:22:46  INFO: [2a96a2d7] disconnected
2020-11-12 09:27:00  INFO: [252cc16d] connected
2020-11-12 09:27:00  INFO: [252cc16d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032303230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e343134323833383635323936342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:27:00  INFO: [252cc16d] id: 277587, time: 2020-11-12 09:27:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:27:31  INFO: [252cc16d] disconnected
2020-11-12 09:27:47  INFO: [77616c94] connected
2020-11-12 09:27:47  WARN: [77616c94] error - Connection reset by peer - IOException (...)
2020-11-12 09:27:47  INFO: [77616c94] disconnected
2020-11-12 09:32:00  INFO: [349203be] connected
2020-11-12 09:32:00  INFO: [349203be: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032333230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e34383838353036313639393534342661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:32:00  INFO: [349203be: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:32:00  INFO: [349203be] id: 277587, time: 2020-11-12 09:32:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:32:30  INFO: [349203be] disconnected
2020-11-12 09:32:48  INFO: [945b7bcb] connected
2020-11-12 09:32:48  WARN: [945b7bcb] error - Connection reset by peer - IOException (...)
2020-11-12 09:32:48  INFO: [945b7bcb] disconnected
2020-11-12 09:37:00  INFO: [0f6d0076] connected
2020-11-12 09:37:00  INFO: [0f6d0076: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032363230266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e35303135313436323539343333372661636375726163793d3526626174743d383220485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:37:00  INFO: [0f6d0076] id: 277587, time: 2020-11-12 09:37:00, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:37:30  INFO: [0f6d0076] disconnected
2020-11-12 09:37:48  INFO: [03ae082d] connected
2020-11-12 09:37:48  WARN: [03ae082d] error - Connection reset by peer - IOException (...)
2020-11-12 09:37:48  INFO: [03ae082d] disconnected
2020-11-12 09:42:01  INFO: [f07c47e1] connected
2020-11-12 09:42:01  INFO: [f07c47e1: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323032393231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33392e32333831313839343738373030312661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:42:01  INFO: [f07c47e1] id: 277587, time: 2020-11-12 09:42:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:42:31  INFO: [f07c47e1] disconnected
2020-11-12 09:42:49  INFO: [a9261418] connected
2020-11-12 09:42:49  WARN: [a9261418] error - Connection reset by peer - IOException (...)
2020-11-12 09:42:49  INFO: [a9261418] disconnected
2020-11-12 09:47:01  INFO: [a48df3f3] connected
2020-11-12 09:47:01  INFO: [a48df3f3: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033323231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e37303239303231363130393731332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:47:01  INFO: [a48df3f3] id: 277587, time: 2020-11-12 09:47:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:47:31  INFO: [a48df3f3] disconnected
2020-11-12 09:47:49  INFO: [a8b59851] connected
2020-11-12 09:47:49  WARN: [a8b59851] error - Connection reset by peer - IOException (...)
2020-11-12 09:47:49  INFO: [a8b59851] disconnected
2020-11-12 09:52:01  INFO: [fd5b3f97] connected
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033353231266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e35373134343230353839373635342661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:52:01  INFO: [fd5b3f97] id: 277587, time: 2020-11-12 09:52:01, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:52:31  INFO: [fd5b3f97] disconnected
2020-11-12 09:52:50  INFO: [9d03f21d] connected
2020-11-12 09:52:50  WARN: [9d03f21d] error - Connection reset by peer - IOException (...)
2020-11-12 09:52:50  INFO: [9d03f21d] disconnected
2020-11-12 09:57:02  INFO: [bd5ad5de] connected
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323033383232266c61743d34372e353430383734266c6f6e3d2d3132322e3237313034372673706565643d302662656172696e673d3236352e3432393638373526616c7469747564653d33382e34343634343337353736363730332661636375726163793d3526626174743d383120485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 09:57:02  INFO: [bd5ad5de] id: 277587, time: 2020-11-12 09:57:02, lat: 47.54087, lon: -122.27105, course: 265.4, accuracy: 5.0
2020-11-12 09:57:32  INFO: [bd5ad5de] disconnected
2020-11-12 09:57:50  INFO: [c5241048] connected
2020-11-12 09:57:50  WARN: [c5241048] error - Connection reset by peer - IOException (...)
2020-11-12 09:57:50  INFO: [c5241048] disconnected
2020-11-12 10:02:02  INFO: [8b9ba6db] connected
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034313232266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33382e39373638393431303739313930322661636375726163793d313026626174743d383020485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:02:02  INFO: [8b9ba6db] id: 277587, time: 2020-11-12 10:02:02, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:02:32  INFO: [8b9ba6db] disconnected
2020-11-12 10:02:51  INFO: [de2c431a] connected
2020-11-12 10:02:51  WARN: [de2c431a] error - Connection reset by peer - IOException (...)
2020-11-12 10:02:51  INFO: [de2c431a] disconnected
2020-11-12 10:07:03  INFO: [5d57336d] connected
2020-11-12 10:07:03  INFO: [5d57336d: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034343233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d33392e37343235363531353731323337342661636375726163793d313026626174743d373920485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:07:03  INFO: [5d57336d] id: 277587, time: 2020-11-12 10:07:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:07:33  INFO: [5d57336d] disconnected
2020-11-12 10:07:52  INFO: [006d6435] connected
2020-11-12 10:07:52  WARN: [006d6435] error - Connection reset by peer - IOException (...)
2020-11-12 10:07:52  INFO: [006d6435] disconnected
2020-11-12 10:12:03  INFO: [1ff03709] connected
2020-11-12 10:12:03  INFO: [1ff03709: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323034373233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e32323130393634353438313832322661636375726163793d313026626174743d373720485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:12:03  INFO: [1ff03709] id: 277587, time: 2020-11-12 10:12:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:12:33  INFO: [1ff03709] disconnected
2020-11-12 10:12:52  INFO: [d52b1288] connected
2020-11-12 10:12:52  WARN: [d52b1288] error - Connection reset by peer - IOException (...)
2020-11-12 10:12:52  INFO: [d52b1288] disconnected
2020-11-12 10:17:03  INFO: [c270a8d9] connected
2020-11-12 10:17:03  INFO: [c270a8d9: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035303233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e36313334343631393034343338322661636375726163793d313026626174743d373620485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9] id: 277587, time: 2020-11-12 10:17:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:17:33  INFO: [c270a8d9] disconnected
2020-11-12 10:17:52  INFO: [9bd54c2e] connected
2020-11-12 10:17:52  WARN: [9bd54c2e] error - Connection reset by peer - IOException (...)
2020-11-12 10:17:52  INFO: [9bd54c2e] disconnected

And the second error:

2020-11-12 10:22:04  INFO: [9587f2b7] connected
2020-11-12 10:22:04  INFO: [9587f2b7: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035333234266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e393439333732333535393932322661636375726163793d313026626174743d373520485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@26b1c55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@1a05e3fd (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b8f1c9f (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@174cfe55 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@4d1fd15d (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@78b0c908 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  WARN: HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b285965 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2020-11-12 10:22:04  INFO: [9587f2b7: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:22:04  INFO: [9587f2b7] id: 277587, time: 2020-11-12 10:22:04, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:22:34  INFO: [9587f2b7] disconnected

Any help with this is much appreciated. I am in the process of building a Raspberry Pi Client for Traccar, but I need these errors resolved before I can move forward.

Thank you!

This means that device force-closed the connection:

error - Connection reset by peer - IOException (...)

This probably means that database internal connection timeout is shorter than pooling library connection timeout:

HikariPool-1 - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@b285965 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.

I don't think it's a big issue because it should just reconnect. Let me know if it doesn't happen.

Thank you for the quick response, Anton.

If the device is force-closing the connection, this would not be related to the Traccar server then, correct? Do you know why the device would force-close the connection? In relation to this, what does the 8-digit hexadecimal number after log-type represent? I noticed that this number changes when I receive the connection reset error as seen here:

2020-11-12 10:17:03  INFO: [c270a8d9: osmand < 192.168.89.1] HEX: 504f5354202f3f69643d3237373538372674696d657374616d703d31363035323035303233266c61743d34372e353430373639266c6f6e3d2d3132322e3237303938322673706565643d302662656172696e673d3233322e37333433373526616c7469747564653d34302e36313334343631393034343338322661636375726163793d313026626174743d373620485454502f312e310d0a486f73743a206469636b73746f7765722e6475636b646e732e6f72673a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313139372044617277696e2f32302e302e300d0a4163636570742d4c616e67756167653a20656e2d75730d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9: osmand > 192.168.89.1] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2020-11-12 10:17:03  INFO: [c270a8d9] id: 277587, time: 2020-11-12 10:17:03, lat: 47.54077, lon: -122.27098, course: 232.7, accuracy: 10.0
2020-11-12 10:17:33  INFO: [c270a8d9] disconnected
2020-11-12 10:17:52  INFO: [9bd54c2e] connected
2020-11-12 10:17:52  WARN: [9bd54c2e] error - Connection reset by peer - IOException (...)
2020-11-12 10:17:52  INFO: [9bd54c2e] disconnected

I'll do some research on the timeouts to figure out how to modify them for the database. Are there recommended settings for this, i.e., what setting is the server expecting?

I don't think it's a big issue because it should just reconnect. Let me know if it doesn't happen.

The device did eventually reconnect, but it took over an hour. It seems odd to me that everything was working great until I added a second device.

If the device is force-closing the connection, this would not be related to the Traccar server then, correct? Do you know why the device would force-close the connection?

Why is this related to the server? You should probably contact your device vendor support to check. It could be related to the server if we don't send response that your device is expecting, but it could also be a purely device issue, which is more common.

The device did eventually reconnect, but it took over an hour. It seems odd to me that everything was working great until I added a second device.

I think you are mixing things up. The second issue is related to the database connection. It has nothing to do with device.

Why is this related to the server? You should probably contact your device vendor support to check. It could be related to the server if we don't send response that your device is expecting, but it could also be a purely device issue, which is more common.

Read my response again, I said that it would NOT be related to the server. If it is a device issue, then it would be an issue with the Traccar Client iOS app.

I think you are mixing things up. The second issue is related to the database connection. It has nothing to do with device.

I don't believe I am mixing things up. I fully understand that the "Connection reset by peer" error has to do with the device and that the "HikariPool" error has to do with the database. I think how my response was formatted might have caused some confusion.

My first paragraph and code block was in reference to your first response explaining what the connection error meant.
My second paragraph was in reference to your response about the database internal connection.
My quote of you and my last paragraph was in reference to your response about the errors not being a big issue.

My apologies for the confusion, but my original questions still stand:

1. Do you know why the device would force-close the connection?
2. What does the 8-digit hexadecimal number after log-type represent?
3. Are there recommended settings for this (database internal connection timeout & pooling library connection timeout), i.e., what setting is the server expecting?

At this point, the second device hasn't been connected for 2 hours. I disabled the Traccar Client on my phone and the other device connected once and I'm now back to this:

2020-11-12 14:33:29  INFO: [5f9fee74] connected
2020-11-12 14:33:29  WARN: [5f9fee74] error - Connection reset by peer - IOException (...)
2020-11-12 14:33:29  INFO: [5f9fee74] disconnected
2020-11-12 14:38:30  INFO: [9ff447c1] connected
2020-11-12 14:38:30  WARN: [9ff447c1] error - Connection reset by peer - IOException (...)
2020-11-12 14:38:30  INFO: [9ff447c1] disconnected
2020-11-12 14:43:31  INFO: [d928f265] connected
2020-11-12 14:43:31  WARN: [d928f265] error - Connection reset by peer - IOException (...)
2020-11-12 14:43:31  INFO: [d928f265] disconnected

It happens every 5 minutes which is what is set in the Traccar Client app. Since mine is disabled and not attempting to connect, I think I can safely narrow it down to the second device. Are there logs for the Traccar Client app stored on the phone that I could look at?

Do you know why the device would force-close the connection?

What makes you think it's your device? I don't see any indication of that. It seems like just a random network connection. We don't even know which port it was on.

What does the 8-digit hexadecimal number after log-type represent?

Connection id.

Are there recommended settings for this (database internal connection timeout & pooling library connection timeout), i.e., what setting is the server expecting?

For most of our servers we use MySQL, not MariaDB, and I've never seen errors like this.

What makes you think it's your device? I don't see any indication of that. It seems like just a random network connection. We don't even know which port it was on.

Fair point. I was making assumptions because this didn't start until I added the second client. Also, when the second client successfully connects, the error does not appear. Is there a way to see what port incoming connections are using? I only have port 5055 forwarded in my router.

For most of our servers we use MySQL, not MariaDB, and I've never seen errors like this.

I thought I had seen other instances of people successfully using MariaDB. I use MariaDB for other dockers on my server and I was hoping to be able to use it since the two are usually interchangeable. This being said, I think I might have found part of my problem in regard to the database error. I followed the instructions here and this uses a MySQL driver and MySQL is also in the database URL. I'm really wanting to avoid installing MySQL just for Traccar, do you think downloading the MariaDB Java driver will fix this, or is this not needed? I found this topic on the forum and you said that it shouldn't be needed, granted, this was 3 years ago.

Traccar is definitely compatible with MariaDB. I know a lot of people are using.

Can we step back a little and figure out what problems you are trying to solve. Is something not working or you just trying to fix some random errors you see in the log?

Traccar is definitely compatible with MariaDB. I know a lot of people are using.

Awesome! This gives me some inspiration.

Can we step back a little and figure out what problems you are trying to solve. Is something not working or you just trying to fix some random errors you see in the log?

Absolutely, I am currently trying to get two iPhones, using the Traccar Client app, to connect with the server. When I had only one phone connected, it was working great. Today, I added a second iPhone and it goes offline after it connects once or twice, and stays offline for long periods (2 hours or more). I looked in the logs and discovered the errors that I posted here.

OK, and have you already followed both server and client troubleshooting guides?

OK, and have you already followed both server and client troubleshooting guides?

I have followed the server troubleshooting guide and I know the server works with the iPhone app, as it's working with one, but not two. I have not followed the client troubleshooting guide yet as I do not have access to the phone during the day. It's my girlfriend's phone and she is at work during the day.
I asked her to send me a screenshot, and from the app, it shows "Location update" every 5 minutes as it should. The location accuracy has been set as high all day, and I would think this would be causing problems as she works in a lab inside of a concrete building, but since there are no errors, the client thinks it is sending the data correctly. I asked her to change from high to medium and see what happens. I'll also check the recommendations in point 6 when she gets home.

As for the database issue, should I start a separate thread for this?

Quick follow up on the client troubleshooting guide. In point 6, it says "Make sure that in iOS settings background execution is allowed and Traccar Client has permission to always access location services." I just looked through my phone, and under Settings>General>Background App Refresh, Traccar is not listed as an option to enable or disable. I am running iOS 14.1.

Looks like that shouldn't be an issue:

Disabling the Background App Refresh setting for the current app, or for all apps, does not prevent the delivery of location events in the background.

Hi Anton Tananaev, I am getting the same problem.

(2020-11-12 14:43:31 WARN: [d928f265] error - Connection reset by peer - IOException (...) 2020-11-12 14:43:31 INFO: [d928f265] disconnected)

But I only get the error when ACC is on.
Devices frequently switch between online and offline.
If devices acc is off every thing is fine.

I have tried different devices (Teltonica and Wetrack2)
problem still there.

What could be the issue, please help.

You should contact your device vendor(s) and ask about it.