Hi all, I am trying to run the oak-template app on my OAK-4-S-AF. I have previously done this and it has worked, but now when I run oakctl app run ., it just hangs forever on "Sending data to device …" [upl-image-preview uuid=15a7a51c-e280-4129-829a-652e75806102 url=https://discuss.luxonis.com/assets/files/2026-01-29/1769661107-382864-image.png alt={TEXT?}] I have rebooted both my PC and the camera, but still cannot get past this. I've deleted the apps from the OAK4S, but still nothing. Has anyone dealt with this issue before? And did you manage to fix it?

oakctl hangs on "Sending data to device" forever

unseeing6866

Hi all,

I am trying to run the oak-template app on my OAK-4-S-AF. I have previously done this and it has worked, but now when I run oakctl app run ., it just hangs forever on "Sending data to device …"

I have rebooted both my PC and the camera, but still cannot get past this. I've deleted the apps from the OAK4S, but still nothing.

Has anyone dealt with this issue before? And did you manage to fix it?

OskarSonc

Hey unseeing6866 - this usually means the host never completes the upload to the device. First confirm the basics: oakctl device list, then check oakctl --version and oakctl device info (agent version) to rule out a host/agent mismatch and perform an update on both oakctl and device OS if they arent't latest...

If that doesn't help and the device is reachable SSH in and check logs/state right after it stalls.

Thanks,
Oskar

unseeing6866

Thanks for helping!

$ oakctl version

0.16.5

$ oakctl list

+---+---------------+-------------------------+--------------+------------------------+---------------+-------+

| # | Serial Number | Device | Connection | OS | Agent Version | Setup |

+=============================================================================================================+

| 1 | xxxxx | Luxonis, Inc. OAK4-S R9 | 192.168.2.23 | Luxonis OS RVC4 1.23.1 | 0.17.0 | OK |

|---+---------------+-------------------------+--------------+------------------------+---------------+-------|

| 2 | xxxxx | Luxonis, Inc. OAK4-S R9 | 192.168.2.25 | Luxonis OS RVC4 1.23.1 | 0.17.0 | OK |

+---+---------------+-------------------------+--------------+------------------------+---------------+-------+

$ oakctl device info

Device Info:

OS: Luxonis OS RVC4 1.23.1

Agent Version: 0.17.0 (rvc4)

Architecture: linux/arm64

Serial Number: 2546118815

Model: Luxonis, Inc. OAK4-S R9

Setup: OK

Internet: Unchecked (use --check_internet to enable this check)

I have set up ssh for one of them. Which logs should I be checking?

unseeing6866

After poking around, I assume you meant to look at the oak-agent logs. Here they are:

~ # journalctl -fu oak-agent

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_daemon]: prepare to announce service 1284316329._oakagent._tcp.local. on eth0: 192.168.2.23

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_SRV 1284316329._oakagent._tcp.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_TXT 1284316329._oakagent._tcp.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_A 1284316329.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_daemon]: resend: announce service 1284316329._oakagent._tcp.local. on 192.168.2.23

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_daemon]: prepare to announce service 1284316329._oakagent._tcp.local. on eth0: fe80::46a9:2cff:fe30:50dd

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_SRV 1284316329._oakagent._tcp.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_TXT 1284316329._oakagent._tcp.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_info]: found active record TYPE_AAAA 1284316329.local.

Jan 30 00:17:14 kalama oak-agent[1652]: DEBUG [mdns_sd::service_daemon]: resend: announce service 1284316329._oakagent._tcp.local. on fe80::46a9:2cff:fe30:50dd

Jan 30 00:17:23 kalama oak-agent[1652]: INFO [oak-agent::modules::public_api_tcp]: TCP: Connection closed

Jan 30 00:17:23 kalama oak-agent[1652]: INFO [oak-agent::modules::public_api_tcp]: TCP: New connection established

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [rustls::server::hs]: decided upon suite TLS13_AES_256_GCM_SHA384

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-writer]: Started

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-reader]: Started

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: Connection closed

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-reader]: Finished

Jan 30 00:17:23 kalama oak-agent[1652]: INFO [oak-agent::modules::public_api_tcp]: Closed stream!

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: Connection closed

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [rustls::common_state]: Sending warning alert CloseNotify

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-writer]: Finished

Jan 30 00:17:23 kalama oak-agent[1652]: INFO [oak-agent::modules::public_api_tcp]: TCP: Connection closed

Jan 30 00:17:23 kalama oak-agent[1652]: INFO [oak-agent::modules::public_api_tcp]: TCP: New connection established

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [rustls::server::hs]: decided upon suite TLS13_AES_256_GCM_SHA384

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-reader]: Started

Jan 30 00:17:23 kalama oak-agent[1652]: DEBUG [lib-tcp-server-multi]: task[tcp-writer]: Started

Jan 30 00:17:23 kalama oak-agent[1652]: WARN [oak-agent::modules::core]: Device password verification failed

Jan 30 00:17:32 kalama oak-agent[1652]: DEBUG [oak-agent]: No file sync receiver found

Jan 30 00:17:33 kalama oak-agent[1652]: DEBUG [oak-agent::filesync]: Scanned files and directories

Jan 30 00:17:42 kalama oak-agent[1652]: DEBUG [lib-webrtc {elapsed: 227.607483ms, payload: b""}]: Signaling connection: pong received

Jan 30 00:18:12 kalama oak-agent[1652]: DEBUG [lib-webrtc {elapsed: 217.151044ms, payload: b""}]: Signaling connection: pong received

OskarSonc

Hey unseeing6866 - sorry for the late answer. It seems like devices are healthy and you have latest version of software installed. The problem I see is "Device password verification failed". Is it possible that you are connecting to the other camera, which has different password? Can you connect to the camera using oakctl connect?

# Connect explicitly (updates the cached token for that device)
oakctl connect 192.168.2.23 -p 'YourPassword' --with-password

# Then run the app on that device
oakctl app run -d 192.168.2.23 /app/path/to/source

unseeing6866

OskarSonc

Hi OskarSonc

I'm not sure what the problem was, but I ended up using another PC to run oakctl, and that worked. In the end I just uninstalled oakctl fully and reinstalled it, now the problem is solved!

OskarSonc

unseeing6866 Happy to hear that! Yes, sometimes updating the oactl causes some weird errors, and it's better to completely remove and reinstall it.

unseeing6866

OskarSonc

So I'm back because my trick of reinstalling oakctl has stopped working. To your previous comment, I can confirm that I am connected to the correct OAK 4 S (there is now only one on my network), and the password is definitely correct. I've tried rebooting everything including my pc, and I've tried explicitly specifying the ip address of the OAK device with: oakctl app run -d 192.168.2.30 ..

But it still just hangs forever on

ubuntu@xlr8 ~/Documents/my-app $ oakctl app run -d 192.168.2.30 .

Starting oakapp in dev mode from path: .

⠙ Sending data to device ...

⠙ [00:01:10] [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0 B/100 B (0s)

Is there any way to know what is failing underneath the hood? I can ssh into the device perfectly fine, and I can start and stop apps that are already on it with oakctl. I just can't seem to build on it.

EDIT: I ran adb kill-server and then reran oakctl app run ., and it seemed to work this time. No idea if that actually did anything or if it was luck.

EDIT2: It was just luck. Can't seem to connect once again, and I have no more tricks 😢

jakaskerl

Hi @unseeing6866
This is a known issue. I think it should be fixed by the new OS in a week or two.

cc @Ales for the confirmation.

Thanks,
Jaka