[DPDK/core Bug 1760] Failed to send message on primary process exit

[DPDK/core Bug 1760] Failed to send message on primary process exit

[bugzilla]

[-- 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 --]

[DPDK/core Bug 1760] Failed to send message on primary process exit

[bugzilla]

http://bugs.dpdk.org/show_bug.cgi?id=1760

Thomas Monjalon (thomas@monjalon.net) changed:

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

--- Comment #1 from Thomas Monjalon (thomas@monjalon.net) ---
Resolved in http://git.dpdk.org/dpdk/commit/?id=cefd5edce2

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