skywire icon indicating copy to clipboard operation
skywire copied to clipboard

`WARN [router]: Failed to handle transport frame: routing table: rule not found`

Open 0pcom opened this issue 9 months ago • 8 comments

When starting the proxy client, sometimes I get the following errors:

[2025-03-22T17:52:05.15067992-05:00] WARN [router]: Failed to handle transport frame: route descriptor does not exist

Followed by:

[2025-03-22T16:15:22.947131457-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:25.945961459-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:28.945928791-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:31.946949258-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:34.949327839-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:37.948531989-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:40.952424336-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:43.950129767-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:46.947040384-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:48.21901971-05:00] DEBUG (STDOUT) [proc:skysocks-client:2a401abeae0c4aec9d4388c4f5d61e3f]: Accepted skysocks client
[2025-03-22T16:15:48.220106076-05:00] DEBUG (STDOUT) [proc:skysocks-client:2a401abeae0c4aec9d4388c4f5d61e3f]: Opened session skysocks client
[2025-03-22T16:15:48.469209774-05:00] DEBUG (STDOUT) [proc:skysocks-client:2a401abeae0c4aec9d4388c4f5d61e3f]: Accepted skysocks client
[2025-03-22T16:15:48.470412758-05:00] DEBUG (STDOUT) [proc:skysocks-client:2a401abeae0c4aec9d4388c4f5d61e3f]: Opened session skysocks client
[2025-03-22T16:15:49.949678247-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:52.952359655-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:55.945559979-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:15:58.9524292-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:01.951540642-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:04.946005769-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:07.95188596-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:10.946104233-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:13.951811455-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found
[2025-03-22T16:16:17.298107443-05:00] WARN [router]: Failed to handle transport frame: routing table: rule not found

The proxy client is not functioning when this happens, no bandwidth, though it is not terminated either.

It's unclear why the error occurs or what to do to avoid it.

0pcom avatar Mar 22 '25 21:03 0pcom