Server Issue - No data from devices

Mile Stone Techa year ago

The port and server are shown open but we are unable to receive data daily when load increases. We did optimization and everything suggested. Can you please let us know initial solution to resolve below error

2022-12-28 03:09:15  WARN: Position forwarding failed: 4200 pending - Status code 2xx expected - RuntimeException (WebDataHandler:261 < *:186 < ...)
2022-12-28 03:09:15  WARN: Position forwarding failed: 4199 pending - Status code 2xx expected - RuntimeException (WebDataHandler:261 < *:186 < ...)
2022-12-28 03:09:15  WARN: Position forwarding failed: 4198 pending - Status code 2xx expected - RuntimeException (WebDataHandler:261 < *:186 < ...)
2022-12-28 03:09:15  WARN: Position forwarding failed: 4197 pending - Status code 2xx expected - RuntimeException (WebDataHandler:261 < *:186 < ...)
2022-12-28 03:09:44  WARN: Event save error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < NotificationManager:68 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Update device status error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:323 < DeviceManager:313 < ...)
2022-12-28 03:09:44  WARN: Update device status error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:323 < DeviceManager:313 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Failed to update device - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:344 < DeviceManager:341 < ...)
2022-12-28 03:09:44  WARN: Update device status error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:323 < DeviceManager:313 < ...)
2022-12-28 03:09:44  INFO: [56ed9adc] id: 869247045209803, time: 2022-12-28 02:34:30, lat: 34.13878, lon: 77.56411, speed: 1.1, course: 148.0
2022-12-28 03:09:44  WARN: Update device status error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:323 < DeviceManager:313 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Update device status error - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:323 < DeviceManager:313 < ...)
2022-12-28 03:09:44  WARN: Failed to update device - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:130 < DataManager:344 < DeviceManager:341 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  INFO: [683c50cd] id: 865205031578221, time: 2022-12-28 02:31:15, lat: 19.61406, lon: 84.82948, speed: 23.3, course: 255.0
2022-12-28 03:09:44  INFO: [683c50cd: h02 < 42.109.140.134] HEX: 353033313537383232312c56312c3032333132352c412c313933362e38313638362c4e2c30383434392e37303639392c452c32322e37382c3234302c3238313232322c4646464646464646230d0a2a48512c3836353230353033313537383232312c56312c3032333133352c412c313933362e37383533362c4e2c30383434392e36343831342c452c32322e39342c3234312c3238313232322c464646464646
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  WARN: Failed to store position - HikariPool-1 - Connection is not available, request timed out after 30000ms. - SQLTransientConnectionException (... < QueryBuilder:58 < *:135 < DataManager:437 < DefaultDataHandler:40 < ...)
2022-12-28 03:09:44  INFO: [683c50cd: h02 > 42.109.140.134] HEX: 2a48512c3836353230353033313537383232312c56342c56312c323032323132323830333039343423
Anton Tananaeva year ago

You have a database connection problem.

Mile Stone Techa year ago

Thanks Anton
Is it something related to server.timeOut parameter. I kept this in traccar.xml to 300 value. Hope both are not linked.

Anton Tananaeva year ago

Not related.

Mile Stone Techa year ago

I tried to do MySQL Optimization by keeping below. Will do testing with this configuration and update you.

[mysqld]
innodb_buffer_pool_size = 22G
innodb_log_file_size = 512M
innodb_flush_method = O_DIRECT
innodb_flush_log_at_trx_commit = 0

My server is having 32GB Ram

Mile Stone Techa year ago

Its still getting same error. Please help us.
When only 10 devices are sending data- its working fine. When 500 devices send data, within 30 mins we are not receiving any error.

We are using forward URL for positions . If we forward for 500 devices and destination server is busy, will it give this kind of error, Please help us on this.