610_device-onboarding-failure-codes.md

title	intro	weight	versions	layout	permissions	showMiniToc	miniTocMaxHeadingLevel	allowTitleToDifferFromFilename	mapTopic	hidden	redirect_from	gettingStartedLinks	popularLinks	guideLinks	introLinks	tags
Device Error Codes	rapyuta.io is a platform that enables robotics solution development by providing the necessary software infrastructure and facilitating the interaction between multiple stakeholders who contribute to the solution development.	611	free-pro-team enterprise-server * *	false	rapyuta.io	true	4	false	false	false						Troubleshoot

A device may fail due to several reasons. The below table lists all the possible error codes together with their description and recommended actions.

Device Error Codes and Recommended Actions

If the issue still persists, please contact support.

Error Code	Description	Recommended Actions
DEV_E100	Internal error	Contact support
DEV_E101	Downloading internal artifact failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device.
DEV_E102	Pulling internal docker image failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device. Ensure that the docker version on device is: docker-ce==17.12.1~ce-0~ubuntu for Ubuntu 16.04 docker-ce==5:18.09.7~3-0~ubuntu-bionic for Ubuntu 18.04 If not, uninstall it and re-onboard the device again.
DEV_E103	Installing pip package failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device. Ensure that the version of Python on device is Python>=2.7.8,<3 If not, uninstall it and re-onboard the device again. Try installing the package manually by executing source /opt/rapyuta/venv/bin/activate && pip install <python-package> and see if it fails. If it doesn’t fail, the issue may be transient. Now, re-onboard the device on successful installation of python package.
DEV_E104	Installing docker failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device. Ensure that the docker version on device is: docker-ce==17.12.1~ce-0~ubuntu for Ubuntu 16.04 docker-ce==5:18.09.7~3-0~ubuntu-bionic for Ubuntu 18.04 If not, uninstall it and re-onboard the device again.
DEV_E105	Installing system package failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device. Try installing the package manually by executing apt-get install <system-package> and see if it fails. If it doesn’t fail, the issue may be transient. Now, re-onboard the device on successful installation of system package.
DEV_E106	Managing files on device failed	Ensure that device has an active internet connection. Ensure that there is adequate disk space on device.
DEV_E107	Internal service failed to start	Contact support
DEV_E108	Initialization time exceeded	re-onboard the device again. Contact support
DEV_E109	Initialization failed due to network error	Ensure that device has an active internet connection.
DEV_E110	Initialization failed due to docker login error	Ensure that device has an active internet connection. Ensure that the package golang-docker-credential-helpers is not installed. If present remove it manually by executing apt-get remove golang-docker-credential-helpers. Now, re-onboard the device again.

Check for active internet connection

To check if a device has an active internet connection, execute the command: ping -c 4 8.8.8.8 at the device's terminal. The ping command will try to reach Google Public DNS. If successful, you should see an output as:

4 packets transmitted, 4 received, 0% packet loss.

Check for disk space

To check if there is adequate disk space on device, run the command: df -h at the device's terminal. The df command will display your disk usage. Ensure the value of percentage used for your main filesystem is not nearly 100%.