I installed the service on a Rpi a month ago and ran smoothly with ssh. Today I installed rdp + apt install xrdp to remote desktop access (with successful connection). But after a temporary network drop the services were no longer available on the platform. Checking on the service status systemctl status connectd.service I got the next log showing the failure.
jun 25 03:00:12 raspberrypi systemd[1]: Started Remote tcp connection service.
jun 25 03:00:36 raspberrypi root[1058]: [connectd_start] Loop
jun 25 03:00:44 raspberrypi connectd_start[554]: /usr/bin/connectd_control: 777:local: bulk_identification_code
jun 25 03:00:44 raspberrypi root[1226]: [connectd_start]
jun 25 03:00:44 raspberrypi root[1227]: [connectd_start] Call bprovision
jun 25 03:00:44 raspberrypi root[1239]: [connectd_start] FAIL: nothing to provision
jun 25 03:00:44 raspberrypi root[1253]: /usr/bin/connectd_start started: FAIL: No active devices to start
jun 25 03:00:44 raspberrypi root[1256]: [connectd_start] exit
is there a way to prevent this from happening?
Kind regards
ps: I recovered the services by loggin into the device with other remote service and reinstalled ssh and rdp.
ref: https://github.com/remoteit/connectd/issues/4
I installed the service on a Rpi a month ago and ran smoothly with ssh. Today I installed rdp + apt install xrdp to remote desktop access (with successful connection). But after a temporary network drop the services were no longer available on the platform. Checking on the service status systemctl status connectd.service I got the next log showing the failure.
is there a way to prevent this from happening?
Kind regards
ps: I recovered the services by loggin into the device with other remote service and reinstalled ssh and rdp.
ref: https://github.com/remoteit/connectd/issues/4