From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1760] Failed to send message on primary process exit
Date: Tue, 22 Jul 2025 15:20:06 +0000 [thread overview]
Message-ID: <bug-1760-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1760
Bug ID: 1760
Summary: Failed to send message on primary process exit
Product: DPDK
Version: 25.07
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
When a secondary process detects primary process has exited and calls
eal_cleanup a warning message is generated.
Primary: testpmd
# dpdk-testpmd -l 0-3 --vdev=net_tap0 -- -i
testpmd> start
...
testpmd> quit
Secondary: dumpcap
# dpdk-dumpcap
File: /tmp/dpdk-dumpcap_0_net_tap0_20250722081556.pcapng
Capturing on 'net_tap0'
Packets captured: 34 Primary process is no longer active, exiting...
EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to No such file or
directory
EAL: Fail to send request /var/run/dpdk/rte/mp_socket:mp_pdump
PDUMP: pdump_prepare_client_request(): client request for pdump enable/disable
failed
EAL: failed to send to (/var/run/dpdk/rte/mp_socket) due to No such file or
directory
EAL: Cannot send message to primary
Dumpcap is doing the right thing and detecing, the problem is internal to EAL.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3286 bytes --]
next reply other threads:[~2025-07-22 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 15:20 bugzilla [this message]
[not found] <bug-1760-3@http.bugs.dpdk.org/>
2026-02-17 22:03 ` [DPDK/core Bug 1760] Failed to send message on primary process exit 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-1760-3@https.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.