You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/usr/bin/ipfixprobe -i 'dpdk;p=0;q=1;e=ipfixprobe-eal --lcores (0-7)@(0,2,4,6,8,10,12,14,16,18,20,22) -a 0000:3b:00.0'
/usr/bin/ipfixprobe -i 'dpdk;p=0;q=1;e=ipfixprobe-eal --lcores (0-7)@(1,3,5,7,9,11,13,15,17,19,21,23) -a 0000:d8:00.0'
The second process gives this output:
EAL: Detected CPU lcores: 24
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Cannot create lock on '/var/run/dpdk/rte/config'. Is another primary process running?
EAL: FATAL: Cannot init config
EAL: Cannot init config
EAL: Error - exiting with code: 1
Cause: Cannot initialize RTE_EAL: Success
This problem should be noted in the documentation.
Possible solution
I've enhanced my local ipfixprobed script to include --file-prefix=$$ when setting up DPDK parameters. If there are no other uses for the --file-prefix, maybe the process itself could do it so that the user does not need to concern with this issue? Of course, it needs to be documented in any case.
Setup
OS: Ubuntu 22.04 LTS
Compilation as deb package using make deb with modified dh_auto_configure in debian/rules
One cannot run two processes as follows:
The second process gives this output:
This problem should be noted in the documentation.
Possible solution
I've enhanced my local
ipfixprobed
script to include--file-prefix=$$
when setting up DPDK parameters. If there are no other uses for the--file-prefix
, maybe the process itself could do it so that the user does not need to concern with this issue? Of course, it needs to be documented in any case.Setup
OS:
Ubuntu 22.04 LTS
Compilation as deb package using make deb with modified
dh_auto_configure
indebian/rules
Full configure params:
The text was updated successfully, but these errors were encountered: