Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused #792

Closed
houshangaziziaccelleran opened this issue Oct 4, 2024 · 6 comments

Comments

@houshangaziziaccelleran
Copy link

Hi
Can someone help with the following issue please?

ad@bm-super11-intel:/usr/local/lib/uhd/examples$ sudo uhd_usrp_probe 
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_23.11; UHD_4.7.0.HEAD-0-ga5ed1872
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=10.10.0.100,type=n3xx,product=n310,serial=32000F1,name=ni-n3xx-32000F1,fpga=HG,claimed=False,addr=10.10.2.100
[INFO] [MPM.PeriphManager] init() called with device args `fpga=HG,mgmt_addr=10.10.0.100,name=ni-n3xx-32000F1,product=n310,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.
ad@bm-super11-intel:/usr/local/lib/uhd/examples$ 

I have an n310. # IP ADDR: ETH for management (10.10.0.100) and two fiber for DPDK use (10.10.1.100 and 10.10.2.100).


ad@bm-super11-intel:/usr/local/lib/uhd/examples$ sudo uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_23.11; UHD_4.7.0.HEAD-0-ga5ed1872
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
    serial: 32000F1
    addr: 10.10.2.100
    claimed: False
    fpga: HG
    mgmt_addr: 10.10.0.100
    mgmt_addr: 10.10.1.100
    mgmt_addr: 10.10.2.100
    name: ni-n3xx-32000F1
    product: n310
    type: n3xx


ad@bm-super11-intel:/usr/local/lib/uhd/examples$ 

This is my UHD version:

ad@bm-super11-intel:/usr/local/lib/uhd/examples$ uhd_config_info --version
UHD 4.7.0.HEAD-0-ga5ed1872
ad@bm-super11-intel:/usr/local/lib/uhd/examples$ 

And here are my FPGA and MPM versions:

ad@bm-super11-intel:/usr/local/lib/uhd/examples$ uhd_usrp_probe --args "addr=10.10.0.100"
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_23.11; UHD_4.7.0.HEAD-0-ga5ed1872
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=10.10.0.100,type=n3xx,product=n310,serial=32000F1,name=ni-n3xx-32000F1,fpga=HG,claimed=False,addr=10.10.0.100
[INFO] [MPM.PeriphManager] init() called with device args `fpga=HG,mgmt_addr=10.10.0.100,name=ni-n3xx-32000F1,product=n310,clock_source=internal,time_source=internal'.
  _____________________________________________________
 /
|       Device: N300-Series Device
|     _____________________________________________________
|    /
|   |       Mboard: ni-n3xx-32000F1
|   |   dboard_0_pid: 336
|   |   dboard_0_serial: 31F6BD1
|   |   dboard_1_pid: 336
|   |   dboard_1_serial: 31F6BD5
|   |   eeprom_version: 3
|   |   fs_version: 20240628134248
|   |   mender_artifact: v4.7.0.0_n3xx
|   |   mpm_sw_version: 4.7.0.0-ga5ed1872
|   |   pid: 16962
|   |   product: n310
|   |   rev: 10
|   |   rpc_connection: remote
|   |   serial: 32000F1
|   |   type: n3xx
|   |   MPM Version: 5.3
|   |   FPGA Version: 8.2
|   |   FPGA git hash: c37b318.clean
|   |   RFNoC capable: Yes

@mbr0wn
Copy link
Contributor

mbr0wn commented Oct 7, 2024

You need to double-check your DPDK settings. If you can do this without DPDK (just for sanity check, you might not reach the appropriate rates), then you can also do it with DPDK if your settings file is correct. See also the manual.

@mbr0wn mbr0wn closed this as completed Oct 7, 2024
@houshangaziziaccelleran
Copy link
Author

Thanks for the reply @mbr0wn!
Is the instruction in this manual valid for my case as well?
My case: I want to use DPDK on my n310 with two SFP dedicated for DPDK.

@houshangaziziaccelleran
Copy link
Author

houshangaziziaccelleran commented Oct 7, 2024

I get such error message. Is there a compatibility issue (UHD- DPDK)?

ad@bm-super11-intel:/usr/local/lib/uhd/examples$ sudo ./benchmark_rate --rx_rate 125e6 --rx_subdev "A:0 B:0" --rx_channels 0,1 --tx_rate 125e6 --tx_subdev "A:0 B:0" --tx_channels 0,1 --args "addr=10.10.1.100,second_addr=10.10.2.100,mgmt_addr=10.10.0.100,master_clock_rate=125e6,use_dpdk=1"

[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_23.11; UHD_4.7.0.0-0-unknown
EAL: Detected CPU lcores: 64
EAL: Detected NUMA nodes: 1
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
TELEMETRY: No legacy callbacks, legacy socket not created
[ERROR] [DPDK] No available DPDK devices (ports) found!
EAL: FATAL: already called initialization.
EAL: already called initialization.
[ERROR] [DPDK] Error with EAL initialization
[ERROR] [X300] X300 Network discovery error RuntimeError: Error with EAL initialization
[ERROR] [UHD] Device discovery error: RuntimeError: No available DPDK devices (ports) found!
[00:00:00.000197] Creating the usrp device with: addr=10.10.1.100,second_addr=10.10.2.100,mgmt_addr=10.10.0.100,master_clock_rate=125e6,use_dpdk=1...
EAL: FATAL: already called initialization.
EAL: already called initialization.
[ERROR] [DPDK] Error with EAL initialization
[ERROR] [UHD] Device discovery error: RuntimeError: Error with EAL initialization
EAL: FATAL: already called initialization.
EAL: already called initialization.
[ERROR] [DPDK] Error with EAL initialization
[ERROR] [X300] X300 Network discovery error RuntimeError: Error with EAL initialization
Error: LookupError: KeyError: No devices found for ----->
Device Address:
    addr: 10.10.1.100
    second_addr: 10.10.2.100
    mgmt_addr: 10.10.0.100
    master_clock_rate: 125e6
    use_dpdk: 1

@mbr0wn
Copy link
Contributor

mbr0wn commented Oct 9, 2024

If you're using current master, you're good, but the latest release does have issues with DPDK 23.11.

@houshangaziziaccelleran
Copy link
Author

houshangaziziaccelleran commented Oct 9, 2024

@mbr0wn Many thanks for the reply! Here is what I get:

ad@bm-super11-intel:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_21.11; UHD_4.7.0.HEAD-0-ga5ed1872
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
    serial: 32000F1
    addr: 10.10.2.100
    claimed: False
    fpga: XG
    mgmt_addr: 10.10.0.100
    mgmt_addr: 10.10.1.100
    mgmt_addr: 10.10.2.100
    name: ni-n3xx-32000F1
    product: n310
    type: n3xx


ad@bm-super11-intel:~$ sudo uhd_usrp_probe 
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; DPDK_21.11; UHD_4.7.0.HEAD-0-ga5ed1872
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=10.10.0.100,type=n3xx,product=n310,serial=32000F1,name=ni-n3xx-32000F1,fpga=XG,claimed=False,addr=10.10.2.100
[INFO] [MPM.PeriphManager] init() called with device args `fpga=XG,mgmt_addr=10.10.0.100,name=ni-n3xx-32000F1,product=n310,clock_source=internal,time_source=internal'.
[ERROR] [RFNOC::MGMT] EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] IO Error during GSM initialization. EnvironmentError: IOError: recv error on socket: Connection refused
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: EnvironmentError: IOError: recv error on socket: Connection refused
Error: RuntimeError: Failure to create rfnoc_graph.
ad@bm-super11-intel:~$ 

@mbr0wn
Copy link
Contributor

mbr0wn commented Oct 9, 2024

@houshangaziziaccelleran like I said, this is not a support forum. This is for bug reports only. In your case, turn off DPDK, make sure communication works with the device, then from there craft a working DPDK configuration. Take further questions to the mailing list.

@EttusResearch EttusResearch locked and limited conversation to collaborators Oct 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants