zenoh icon indicating copy to clipboard operation
zenoh copied to clipboard

Sporadic "Route data with unknown scope"

Open torsteingrindvik opened this issue 1 year ago • 2 comments

Describe the bug

If I start my example it sometimes prints an error:

zenoh-issue

On the subscriber side I then see a missing payload.

To reproduce

  1. I start my subscriber app
  2. I run my publish example many times

Zenoh default config on both sides.

My app is fairly complex (and closed source) but I could try to make a minimal reproduction if I can get some context from maintainers what the error message means and what I should look for etc.

System info

System is rolling endeavour OS.

Using Zenoh 0.11.0-rc.

torsteingrindvik avatar Apr 25 '24 16:04 torsteingrindvik

Got the same issue here :

2025-01-04T19:15:33.741532Z DEBUG acc-0 ThreadId(12) zenoh_transport::unicast::manager: New transport opened between 1efe554b22a6282057c67585d62ce481 and c53304aeb843585055813476cb24faaf - whatami: client, sn resolution: U32, initial sn: 142670226, qos: false, multilink: false, lowlatency: false
2025-01-04T19:15:33.741568Z DEBUG acc-0 ThreadId(12) zenoh_transport::unicast::establishment::accept: New transport link accepted from c53304aeb843585055813476cb24faaf to 1efe554b22a6282057c67585d62ce481: TransportLinkUnicast { link: Link { src: udp/192.168.0.238:7447, dst: udp/192.168.0.247:57222, mtu: 65487, is_reliable: false, is_streamed: false }, config: TransportLinkUnicastConfig { direction: Inbound, batch: BatchConfig { mtu: 2048, is_streamed: false, is_compression: false }, priorities: None, reliability: None } }
2025-01-04T19:15:35.141734Z ERROR rx-49 ThreadId(63) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!
2025-01-04T19:16:39.487755Z ERROR  rx-1 ThreadId(15) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!
2025-01-04T19:17:34.780054Z ERROR  rx-1 ThreadId(15) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!
2025-01-04T19:17:56.904185Z ERROR rx-49 ThreadId(63) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!
2025-01-04T19:18:27.059286Z ERROR  rx-1 ThreadId(15) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!




2025-01-04T19:18:44.153979Z ERROR  rx-1 ThreadId(15) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!
2025-01-04T19:19:50.500817Z ERROR rx-49 ThreadId(63) zenoh::net::routing::dispatcher::pubsub: Face{65, c53304aeb843585055813476cb24faaf} Route data with unknown scope 13362!

My context

  • ESP32 using idf zenoh-pico to communicate to a lubuntu pc
  • one publisher on PC sending to ESP32 1/sec
  • one subscriber on PC for fata of ESP32
  • ESP32 publishing at interval of 10 msec

Noise ? UDP should be CRC correct.

vortex314 avatar Jan 04 '25 19:01 vortex314

Hello @vortex314 could you please confirm which Zenoh version are you using? Thanks!

sashacmc avatar May 13 '25 15:05 sashacmc