DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 731] [dpdk-19.11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py prompt connection refused
Date: Thu, 10 Jun 2021 11:28:04 +0000	[thread overview]
Message-ID: <bug-731-3@http.bugs.dpdk.org/> (raw)

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.

             reply	other threads:[~2021-06-10 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 11:28 bugzilla [this message]
2021-09-06  8:13 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-731-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).