# remoteit-main init script fails to start connectd services — r3\_start\_services() not sourced from sysvinit.sh **URL:** \ **Category:** OEM Registration\ **Created:** [April 11, 2026, 12:11am UTC](https://forum.remote.it/t/remoteit-main-init-script-fails-to-start-connectd-services-r3-start-services-not-sourced-from-sysvinit-sh/1475 "2026-04-11T00:11:11Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![JGG20](https://avatars.discourse-cdn.com/v4/letter/j/9f8e36/32.png) [@JGG20](https://forum.remote.it/u/JGG20)\ **Post date:** [April 11, 2026, 12:11am UTC](https://forum.remote.it/t/remoteit-main-init-script-fails-to-start-connectd-services-r3-start-services-not-sourced-from-sysvinit-sh/1475/1 "2026-04-11T00:11:11Z")
Package: remoteit 5.4.2 (arm64 RPi) Download: [https://downloads.remote.it/remoteit/latest/remoteit.arm64.rpi.deb](https://downloads.remote.it/remoteit/latest/remoteit.arm64.rpi.deb) Summary: The remoteit-main init script sources functions.sh and oem.sh, then calls r3\_start\_services. However, r3\_start\_services() is defined in sysvinit.sh, which is never sourced. The call silently fails because it’s wrapped in 2\>/dev/null. As a result, remoteit-main start runs successfully but never starts the connectd processes — the device registers and appears in the dashboard but stays permanently offline. Affected files: - /etc/init.d/remoteit-main — sources functions.sh and oem.sh, calls r3\_start\_services - /usr/share/remoteit/functions.sh — calls r3\_start\_services but does not define it - /usr/share/remoteit/sysvinit.sh — defines r3\_start\_services() but is never sourced Reproduction: 1. Install remoteit.arm64.rpi.deb on Raspberry Pi OS (Trixie/arm64) 2. Register device via bulk provisioning 3. Run sudo /etc/init.d/remoteit-main start 4. Observe: schannel and demuxer start, but no connectd processes are spawned 5. Device shows as offline in remote.it dashboard Workaround: echo ‘. /usr/share/remoteit/sysvinit.sh’ \>\> /usr/share/remoteit/functions.sh /etc/init.d/remoteit-main restart