Traccar 4.2 crash after 5 hours of working.

lfiallos6 years ago

I updated to 4.2 from 3.16

now the server crash every 5 hours, i have to erase the logs files and restart the service to up the server again.

Server: Centos 7
DB: MariaDB 5.5.60

here is the log file information:

The last packet successfully received from the server was 106 milliseconds ago.  The last packet sent successfully to the server was 106 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-17 23:55:47  WARN: Failed to store position - Communications link failure

The last packet successfully received from the server was 106 milliseconds ago.  The last packet sent successfully to the server was 106 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-17 23:55:47  WARN: HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@4f4b6020 marked as broken because of SQLSTATE(08S01), ErrorCode(0) - Communications link failure

The last packet successfully received from the server was 70 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:339 < DeviceManager:249 < ...)
2018-11-18 00:00:15  WARN: HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@24891f47 marked as broken because of SQLSTATE(08S01), ErrorCode(0) - Communications link failure

The last packet successfully received from the server was 69 milliseconds ago.  The last packet sent successfully to the server was 0 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 00:00:15  WARN: Failed to store position - Communications link failure

2018-11-18 00:24:59  WARN: Too many open files - IOException (...)
2018-11-18 00:25: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-18 00:25:00  WARN: Too many open files - IOException (...)

any advise please ? i didn't have this problem on version 3.16

lfiallos6 years ago

I set the IPv4 to the mysql.jdbc instead the word "localhost" so i'm monitoring the logs and everything is operating normally.

I hope not to receive a server crash in a few hours :)

lfiallos6 years ago

The server crash again :(

Here is the exact moment in the log file:

2018-11-18 08:01:12  INFO: [abed23c3: 5001 < 181.189.153.85] HEX: 696d65693a3836343138303033353537363033372c747261636b65722c3138313131383038303131312c2c462c3134303130372e3030302c412c313533312e303734302c4e2c30383735382e393137312c572c302e30302c303b
2018-11-18 08:01:12  INFO: [abed23c3] id: 864180035576037, time: 2018-11-18 08:01:07, lat: 15.51790, lon: -87.98195, course: 0.0
2018-11-18 08:01:12  INFO: [34f42606: 5001 < 181.189.153.3] HEX: 696d65693a3836383638333032393333343533332c747261636b65722c3138313131383232303131322c2c462c3134303130372e3030302c412c313431302e333434302c4e2c30383731382e373335312c572c302e30302c303b
2018-11-18 08:01:12  WARN: HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@6965bbe7 marked as broken because of SQLSTATE(08S01), ErrorCode(0) - Communications link failure

The last packet successfully received from the server was 123 milliseconds ago.  The last packet sent successfully to the server was 122 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 08:01:12  WARN: Failed to store position - Communications link failure

The last packet successfully received from the server was 123 milliseconds ago.  The last packet sent successfully to the server was 122 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@14d398b4 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@5dcf04f4 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@3ecc0ebe (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@302c4b87 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@38b2630e (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@1dff3848 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@43187cb7 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@113a7720 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:12  WARN: HikariPool-1 - Failed to validate connection com.mysql.jdbc.JDBC4Connection@3abbcc1a (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
2018-11-18 08:01:13  INFO: [25ae00a1: 5001 < 181.189.153.30] HEX: 696d65693a3836343138303033353538313939352c747261636b65722c3138313131383038303131332c2c462c3134303130382e3030302c412c313432302e353439372c4e2c30383733352e363231302c572c302e30302c303b
2018-11-18 08:01:14  INFO: [34f42606] id: 868683029334533, time: 2018-11-18 08:01:07, lat: 14.17240, lon: -87.31225, course: 0.0
2018-11-18 08:01:14  INFO: [c73297b6: 5001 < 181.189.153.120] HEX: 696d65693a3836383638333032373237383337372c747261636b65722c3138313131383232303131322c2c462c3134303130382e3030302c412c313434302e333236312c4e2c30383631332e343231352c572c302e30302c303b
2018-11-18 08:01:14  WARN: HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@1c5e5356 marked as broken because of SQLSTATE(08S01), ErrorCode(0) - Communications link failure

The last packet successfully received from the server was 131 milliseconds ago.  The last packet sent successfully to the server was 131 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 08:01:14  WARN: Failed to store position - Communications link failure

The last packet successfully received from the server was 131 milliseconds ago.  The last packet sent successfully to the server was 131 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 08:01:14  WARN: HikariPool-1 - Connection com.mysql.jdbc.JDBC4Connection@184d347a marked as broken because of SQLSTATE(08S01), ErrorCode(0) - Communications link failure

The last packet successfully received from the server was 112 milliseconds ago.  The last packet sent successfully to the server was 111 milliseconds ago. - CommunicationsException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:30 < ...)
2018-11-18 08:01:14  WARN: Failed to store position - Communications link failure