[dpdk-dev] [Bug 731] [dpdk-19.11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py prompt connection refused

[dpdk-dev] [Bug 731] [dpdk-19.11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py prompt connection refused

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=731

            Bug ID: 731
           Summary: [dpdk-19.11.9] telemetry: python3
                    /root/dpdk/usertools/dpdk-telemetry-client.py prompt
                    connection refused
           Product: DPDK
           Version: 19.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: yux.jiang@intel.com
  Target Milestone: ---

[Environment]
DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
19.11.9-rc2: bb144e7a1c5e7709c74b3096179f6296e77923da
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Ubuntu 18.04.4
Compiler: gcc (GCC) 8.4.1
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz.
NIC hardware: 82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb
NIC firmware:  0x61bf0001
 driver：ixgbe-5.6.1


[Test Setup]
Steps to reproduce
List the steps to reproduce the issue.

1.bind nic to vfio-pci
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:81:00.0 0000:81:00.1
2.start pf testpmd
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1,2 -n 4 -w 0000:81:00.0 -w
0000:81:00.1 --file-prefix=dpdk_11234_20210610195821 --telemetry – -i 
3.start
4.modify dpdk-telemetry-client.py
#sed -i
's/self.socket.send_fd.connect("\/var\/run\/dpdk\/.*\/telemetry")/self.socket.send_fd.connect("\/var\/run\/dpdk\/dpdk_11234_20210610195821\/telemetry")/g'
/root/dpdk/usertools/dpdk-telemetry-client.py
#sed -i
's/self.socket.send_fd.connect("\/var\/run\/dpdk\/.*\/telemetry")/self.socket.send_fd.connect("\/var\/run\/dpdk\/dpdk_11234_20210610195821\/telemetry")/g'
/root/dpdk/dpdk_telemetry_client.py
5.python3 /root/dpdk/usertools/dpdk-telemetry-client.py


[Show the output from the previous commands.]

Warning - No filepath passed, using default (/var/run/dpdk/default_client).
Traceback (most recent call last):
File "/root/dpdk/usertools/dpdk-telemetry-client.py", line 134, in <module>
client.register()
File "/root/dpdk/usertools/dpdk-telemetry-client.py", line 67, in register
self.socket.send_fd.connect("/var/run/dpdk/dpdk_12064_20210610203206/telemetry")
ConnectionRefusedError: [Errno 111] Connection refused
Error - Client could not be destroyed
Error - Sockets could not be closed


[Expected Result]
test normal. 


[Regression]
Is this issue a regression: (Y/N) Y     
Version the regression was introduced: Specify git id if known.

commit 555da24882e1ca836f9532304f5f58034e57ff5e (HEAD)
Author: Luc Pelletier <lucp.at.work@gmail.com>
Date: Fri May 21 11:49:06 2021 -0400

eal: fix race in control thread creation

[ upstream commit 34cc55cce6b180a6c3ee3fcf70a0fd56927f240d ]

The creation of control threads uses a pthread barrier for
synchronization. This patch fixes a race condition where the pthread
barrier could get destroyed while one of the threads has not yet
returned from the pthread_barrier_wait function, which could result in
undefined behaviour.

Fixes: 3a0d465d4c53 ("eal: fix use-after-free on control thread creation")

-- 
You are receiving this mail because:
You are the assignee for the bug.

[dpdk-dev] [Bug 731] [dpdk-19.11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py prompt connection refused

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=731

jiang,yu (yux.jiang@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #7 from jiang,yu (yux.jiang@intel.com) ---
Verified on dpdk_lts 19.11.10-rc2
Tested passed for i40e/ice/ixgbe

-- 
You are receiving this mail because:
You are the assignee for the bug.