Vista: /data/.dinitctl socket missing at boot, no airside services started

[LeoniePhiline]

Here the situation on my DJI FPV Air Unit Light (Caddx Vista).

Note that I removed wtfos, rerooted and reinstalled it, and the issue persists even then.

Here a CLI exploration after boot:

root@pigeon_wm150_tiny:/ # dinitctl -u list
dinitctl: connecting to socket /data/.dinitctl: No such file or directory
1|root@pigeon_wm150_tiny:/ # ps | grep dinit
root      564   1     2724   880   SyS_epoll_ 00000000 S /opt/sbin/dinit
root@pigeon_wm150_tiny:/ # /opt/etc/init.d/rc.unslung restart                  
root@pigeon_wm150_tiny:/ # dinitctl -u list                                    
[[+]     ] boot
[{+}     ] msp-osd-airside (pid: 954)
root@pigeon_wm150_tiny:/ # 

• At first, /opt/sbin/dinit is running (presumably started by /opt/etc/init.d/rc.unslung (entware) which runs S01dinit.sh), but the /data/.dinitctl socket is missing.
• dinit can be successfully restarted.
• After restarting dinit, dinitctl can connect to the daemon.
• In the previous boot, at this point I only saw [[+] ] boot and needed to run dinitctl -u enable msp-osd-airside manually. Now, the boot after you can see that [{+} ] msp-osd-airside (pid: 954) is present.
• The configurator, which should have enabled msp-osd-airside in the first place, fails configuring Startup, since it tries running dinitctl which fails due to the missing socket.

[j005u]

Is this vista still in this state? If so please ping me (Joonas) on Discord so I can remotely take a look at your vista through the configurator reverse shell functionality.

Or alternatively, please post your dmesg output and the wtfos startup log from /blackbox/wtfos.log, that might offer some clues.

Also, how sure are you dinit is initially running with the socket missing? How did you determine this? I've seen something like this 6+ months ago and then it was an issue of starting dinit in the first place.

[LeoniePhiline]

I'll come back to you about this - no time at the moment. Please keep the issue open :)