[Bug] Thread DUT commissioning failure with Internal Error

[SupreethKoushik2209]

Describe the bug

I'm using nRF Thread dongle (RCP) connected to Raspberry Pi with Matter Test Harness and Silicon Labs EFR32MG Thread Starter Kit with Door Lock sample application as DUT on Thread. I see the internal Error whenever I try to execute a test case. DUT commissioning is unsuccessful with below errors:

Test Suite Error: Error occurred during setup of test suite.FirstChipToolSuite. sent 1011 (internal error) keepalive ping timeout; no close frame received or CHIP:TOO Pairing Failure: src/platform/Linux/bluez/BluezEndpoint.cpp: "611:" CHIP Error 0x000000AC: Internal error

Also, the Test Harness doesnt auto launch and will have to manually launch it everytime after boot up using ./certification-tool/scripts/start.sh command

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

MoT_Test_1_2024_06_28_07_07_31-7.json MoT_Test_1_2024_06_26_12_50_30.log

PICS file

Door lock Test Plan PICS.zip

Screenshots

Environment

Raspberry Pi 4 Ubuntu Server 22.04 LTS (64-bit) Thread Border Router RCP - nRF52840 Dongle (FW - rcp_thread_1_3_nrf52840dongle_nrf52840_v2.0.2) Reference Matter Node (DUT) on Thread - Silicon Labs EFR32MG Thread Starter Kit

Additional Information

Project Config: { "config": { "test_parameters": null, "network": { "wifi": { "ssid": "", "password": "" }, "thread": { "rcp_serial_path": "/dev/ttyACM0", "rcp_baudrate": 115200, "on_mesh_prefix": "fd11:35::/64", "network_interface": "wlan0", "dataset": { "channel": "25", "panid": "0x5b35", "extpanid": "5b35dead5b35beef", "networkkey": "00112233445566778899aabbccddeeff", "networkname": "5b35" }, "otbr_docker_image": null } }, "dut_config": { "discriminator": "3840", "setup_code": "20202021", "pairing_mode": "ble-thread", "chip_timeout": null, "chip_use_paa_certs": false, "trace_log": true } },

[hiltonlima]

Also, the Test Harness doesnt auto launch and will have to manually launch it everytime after boot up using ./certification-tool/scripts/start.sh command

Could you send the docker logs after you restart the raspberry? 1 - cd certification-tool 2 - docker compose logs backend

Also you can try to reinstall the TH. 1 - cd certification-tool 2 - ./scripts/stop.sh 3 - ./scripts/ubuntu/auto-install.sh v2.10.1-beta1+spring2024 4 - Check if no erros occurs and reboot the raspberry

[hiltonlima]

@cecille could you help to triage this issue? About the internal error response?

[SupreethKoushik2209]

@hiltonlima Pls find the Docker logs attached here docker compose logs backend.txt

[SupreethKoushik2209]

Also, the Test Harness doesnt auto launch and will have to manually launch it everytime after boot up using ./certification-tool/scripts/start.sh command

Could you send the docker logs after you restart the raspberry? 1 - cd certification-tool 2 - docker compose logs backend

Also you can try to reinstall the TH. 1 - cd certification-tool 2 - ./scripts/stop.sh 3 - ./scripts/ubuntu/auto-install.sh v2.10.1-beta1+spring2024 4 - Check if no erros occurs and reboot the raspberry

@hiltonlima I'm unable to run the Test harness with the above branch. Backend service is unable to start

matter@ubuntu:~/certification-tool$ ./scripts/start.sh [+] Running 6/6 ✔ Network chip-default Created 0.4s ✔ Network certification-tool_traefik-public Created 0.3s ✔ Container certification-tool-db-1 Started 1.9s ✔ Container certification-tool-proxy-1 Started 2.6s ✔ Container certification-tool-frontend-1 Started 1.7s ✔ Container certification-tool-backend-1 Started 2.8s Waiting for frontend to start................. done Waiting for backend to startservice "backend" is not running

matter@ubuntu:~/certification-tool$ git branch --show-current v2.10.1-beta1+spring2024

[SupreethKoushik2209]

@cecille could you help to triage this issue? About the internal error response?

@hiltonlima Any update on this error.

Further observation: I'm able to successfully run test only once. Next test run almost always fails with below internal error and Raspberry Pi get disconnected with WiFi AP. It works the next time only on power cycle of Raspberry Pi. My team has also reported similar behaviour with CHIP-tool running on Raspberry Pi.

"Test Suite Error: Error occurred during setup of test suite.FirstChipToolSuite. sent 1011 (internal error) keepalive ping timeout; no close frame received"

[hiltonlima]

Hi @SupreethKoushik2209 , unfortunately we don't have any news yet. As soon as we have any information we will let you know.

[hiltonlima]

@SupreethKoushik2209 sorry for this late response... This error still occurring on the latest branch? v2.11-beta3.1+fall2024