Uploaded image for project: 'Red Hat Service Interconnect (Skupper)'
  1. Red Hat Service Interconnect (Skupper)
  2. SKUPPER-2829

Excessive logging and problem when resource is created before site

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      If you create a listener resource before creating a site in a namespace, the listener might not work as expected and you might see excessive router logging like:

      ```
      2025-09-25 00:41:43.870905 +0000 FLOW_LOG (info) LOG [89855:273642] BEGIN END parent=89855:0 logSeverity=3 logText=LOG_TCP_ADAPTOR: Listener backend: proactor listener error on backend:8082: proton:io (Cannot assign requested address - listen on backend:8082) sourceFile=/remote-source/skupper-router/app/src/adaptors/adaptor_listener.c sourceLine=172

      2025-09-25 00:52:15.490647 +0000 TCP_ADAPTOR (error) Listener backend: proactor listener error on backend:8082: proton:io (Cannot assign requested address - listen on backend:8082)

      ```

      To workaround this issue, delete and recreate any listener resources.

      To avoid this issue, always create a site and wait for the site status `ready` before creating other resources.
      Show
      If you create a listener resource before creating a site in a namespace, the listener might not work as expected and you might see excessive router logging like: ``` 2025-09-25 00:41:43.870905 +0000 FLOW_LOG (info) LOG [89855:273642] BEGIN END parent=89855:0 logSeverity=3 logText=LOG_TCP_ADAPTOR: Listener backend: proactor listener error on backend:8082: proton:io (Cannot assign requested address - listen on backend:8082) sourceFile=/remote-source/skupper-router/app/src/adaptors/adaptor_listener.c sourceLine=172 2025-09-25 00:52:15.490647 +0000 TCP_ADAPTOR (error) Listener backend: proactor listener error on backend:8082: proton:io (Cannot assign requested address - listen on backend:8082) ``` To workaround this issue, delete and recreate any listener resources. To avoid this issue, always create a site and wait for the site status `ready` before creating other resources.
    • Known Issue

            fgiorget@redhat.com Fernando Giorgetti
            pwright@redhat.com Paul Wright
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: