Error en server Traccar - Flespi, 403: stream failed to deliver messages

Josue 4 years ago

Good morning, I have a bug with the Flespi protocol.
Since yesterday it returns the following error:
403: stream failed to deliver messages (request sent but no response received) 08/11/2021 12:05:30

In some moments it receives the information correctly, but there is already a lot of failure and Traccar does not respond.

Anton Tananaev 4 years ago

Logs?

Josue 4 years ago

In the log it is receiving data, but very slow, and it was not like that. there are delays of many hours.

Logs from flespi

403: stream failed to deliver messages (request sent but no response received)
11/08/2021 12:29:13
{
error_code : -2
event_code : 403
origin_id : 17185
origin_type : 12
timestamp : 1628702953.816744
}

The devices say 0 minutes, but the date is yesterday.

Anton Tananaev 4 years ago

You are on Traccar forum, so when I'm asking logs, I mean Traccar, unless explicitly specified otherwise.

Andrés 3 years ago

Josue , how did you solve the problem? Was it a lack of memory, bad config parameters or something else?

Anton, I have facing the same problem. The log says disconnected.

remote socket address - ClosedChannelException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 DEBUG: HttpConnection@22fb7cce::SocketChannelEndPoint@61bedce4{l=null,r=null,CLOSED,fill=-,flush=-,to=8/30000}{io=0/0,kio=-1,kro=-1}->HttpConnection@22fb7cce[p=HttpParser{s=CLOSED,0 of -1},g=HttpGenerator@450deb4e{s=START}]=>HttpChannelOverHttp@31c83009{s=HttpChannelState@6020af21{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=IDLE,uri=null,age=0} parsed false HttpParser{s=CLOSED,0 of -1}
2022-08-19 22:30:52 DEBUG: Could not retrieve local socket address - ClosedChannelException (...)
2022-08-19 22:30:52 DEBUG: Could not retrieve remote socket address - ClosedChannelException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 DEBUG: releaseRequestBuffer HttpConnection@22fb7cce::SocketChannelEndPoint@61bedce4{l=null,r=null,CLOSED,fill=-,flush=-,to=9/30000}{io=0/0,kio=-1,kro=-1}->HttpConnection@22fb7cce[p=HttpParser{s=CLOSED,0 of -1},g=HttpGenerator@450deb4e{s=START}]=>HttpChannelOverHttp@31c83009{s=HttpChannelState@6020af21{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=IDLE,uri=null,age=0}
2022-08-19 22:30:52 DEBUG: Could not retrieve local socket address - ClosedChannelException (...)
2022-08-19 22:30:52 DEBUG: Could not retrieve remote socket address - ClosedChannelException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 DEBUG: shutdownOutput SocketChannelEndPoint@61bedce4{l=null,r=null,CLOSED,fill=-,flush=-,to=9/30000}{io=0/0,kio=-1,kro=-1}->HttpConnection@22fb7cce[p=HttpParser{s=CLOSED,0 of -1},g=HttpGenerator@450deb4e{s=START}]=>HttpChannelOverHttp@31c83009{s=HttpChannelState@6020af21{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=IDLE,uri=null,age=0}
2022-08-19 22:30:52 DEBUG: Could not retrieve local socket address - ClosedChannelException (...)
2022-08-19 22:30:52 DEBUG: Could not retrieve remote socket address - ClosedChannelException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 TRACE: IGNORED - CancelledKeyException (...)
2022-08-19 22:30:52 DEBUG: HttpConnection@22fb7cce::SocketChannelEndPoint@61bedce4{l=null,r=null,CLOSED,fill=-,flush=-,to=10/30000}{io=0/0,kio=-1,kro=-1}->HttpConnection@22fb7cce[p=HttpParser{s=CLOSED,0 of -1},g=HttpGenerator@450deb4e{s=START}]=>HttpChannelOverHttp@31c83009{s=HttpChannelState@6020af21{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0},r=1,c=false/false,a=IDLE,uri=null,age=0} onFillable exit HttpChannelState@6020af21{s=IDLE rs=BLOCKING os=OPEN is=IDLE awp=false se=false i=true al=0} null
2022-08-19 22:30:52 DEBUG: ReservedThread@83d9f07{RUNNING,thread=Thread[qtp594570680-28,5,main]} was=RUNNING next=RESERVED size=0+2 capacity=2
2022-08-19 22:30:52 DEBUG: ReservedThread@83d9f07{RESERVED,thread=Thread[qtp594570680-28,5,main]} waiting ReservedThreadExecutor@459f703f{reserved=2/2,pending=0}

Anton Tananaev 3 years ago

Andrés your logs are not helpful. Please provide the logs with the standard logging level.

Andrés 3 years ago

Anton Tanaev here is the log with standard logging level.

2022-08-22 15:07:55  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Unknown device - 868789021809727 (172.32.1.35)
2022-08-22 15:07:56  WARN: Unknown device - 868789021160311 (172.32.1.35)
2022-08-22 15:07:56  WARN: Unknown device - 860896050605708 (172.32.1.35)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:56  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Unknown device - 868789021427876 (172.32.1.35)
2022-08-22 15:07:57  WARN: Unknown device - 868789021865364 (172.32.1.35)
2022-08-22 15:07:57  WARN: Unknown device - 868789021183123 (172.32.1.35)
2022-08-22 15:07:57  WARN: Unknown device - 868789021807374 (172.32.1.35)
2022-08-22 15:07:57  WARN: Unknown device - 868789021180301 (172.32.1.35)
2022-08-22 15:07:57  WARN: Unknown device - 868789021428650 (172.32.1.35)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)
2022-08-22 15:07:57  WARN: Update device status error - ERROR: column "status" of relation "tc_devices" does not exist
  Position: 23 - PSQLException (... < QueryBuilder:472 < DatabaseStorage:108 < ConnectionManager:278 < ...)

Are you able to give technical support to our project by hours?

Anton Tananaev 3 years ago

Yes, if you're interested in paid support send us an email.

From the logs it looks like you didn't upgrade the server correctly.