Physical device deployment failure please check attachment log file and screenshot

gpram · May 10, 2019, 12:51pm

PHYSICAL DEVICE DEPLOYMENT FAILURE PLEASE CHECK ATTACHMENT LOG FILE AND SCREENSHOT

Screenshot%20from%202019-05-10%2018-20-55

mirzak · May 10, 2019, 12:55pm

The images for 1.7 demo environment can be found here,

https://docs.mender.io/1.7/getting-started/download-test-images

Could you also paste the full log of the failed deployment, as text preferably.

gpram · May 10, 2019, 1:14pm

PLEASE READ THIS LOG FILE OPEN BELLOW LINK
https://jpst.it/1ItFd

2019-05-10 12:30:16 +0000 UTC debug: handle update fetch state
2019-05-10 12:30:16 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:30:17 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Server:[openresty/1.13.6.2] Date:[Fri, 10 May 2019 12:30:17 GMT] Accept-Ranges:[bytes] Last-Modified:[Fri, 10 May 2019 11:09:36 GMT] X-Xss-Protection:[1; mode=block] X-Amz-Request-Id:[159D523117A0BE8D] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Content-Type:[application/vnd.mender-artifact] Content-Length:[36845056] Connection:[keep-alive] Content-Security-Policy:[block-all-mixed-content] X-Content-Type-Options:[nosniff] Etag:["c5c40d79e6b13c26821a5ef89baf7d91"] Vary:[Origin] X-Frame-Options:[DENY]] 0xd5ecc0 36845056 [] false false map[] 0xc8a700 0xc675c0}+
2019-05-10 12:30:17 +0000 UTC info: State transition: update-fetch [Download] -> update-store [Download]
2019-05-10 12:30:17 +0000 UTC debug: handle update install state
2019-05-10 12:30:17 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:30:17 +0000 UTC debug: Read data from device manifest file: device_type=beaglebone-yocto-grub
2019-05-10 12:30:17 +0000 UTC debug: Found needed line: device_type=beaglebone-yocto-grub
2019-05-10 12:30:17 +0000 UTC debug: Current manifest data: beaglebone-yocto-grub
2019-05-10 12:30:17 +0000 UTC info: no public key was provided for authenticating the artifact
2019-05-10 12:30:17 +0000 UTC debug: checking if device [beaglebone-yocto-grub] is on compatibile device list: [beaglebone-yocto-grub]
2019-05-10 12:30:17 +0000 UTC debug: installing update core-image-base-beaglebone-yocto-grub.ext4 of size 234881024
2019-05-10 12:30:17 +0000 UTC debug: Trying to install update of size: 234881024
2019-05-10 12:30:17 +0000 UTC debug: Active partition: /dev/mmcblk0p2
2019-05-10 12:30:17 +0000 UTC debug: Detected inactive partition /dev/mmcblk0p3, based on active partition /dev/mmcblk0p2
2019-05-10 12:30:17 +0000 UTC info: opening device /dev/mmcblk0p3 for writing
2019-05-10 12:30:17 +0000 UTC info: partition /dev/mmcblk0p3 size: 234881024
2019-05-10 12:32:13 +0000 UTC info: wrote 234881024/234881024 bytes of update to device /dev/mmcblk0p3
2019-05-10 12:32:15 +0000 UTC debug: installer: successfully read artifact [name: release-1_1.7.1; version: 2; compatible devices: [beaglebone-yocto-grub]]
2019-05-10 12:32:15 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:32:15 +0000 UTC info: State transition: update-store [Download] -> update-install [ArtifactInstall]
2019-05-10 12:32:15 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:15 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:15 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:32:15 +0000 UTC debug: Inactive partition: /dev/mmcblk0p3
2019-05-10 12:32:15 +0000 UTC debug: Marking inactive partition (/dev/mmcblk0p3) as the new boot candidate.
2019-05-10 12:32:15 +0000 UTC info: Enabling partition with new image installed to be a boot candidate: 3
2019-05-10 12:32:15 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=
2019-05-10 12:32:15 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:]
2019-05-10 12:32:16 +0000 UTC debug: Marking inactive partition as a boot candidate successful.
2019-05-10 12:32:16 +0000 UTC info: State transition: update-install [ArtifactInstall] -> reboot [ArtifactReboot_Enter]
2019-05-10 12:32:16 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:16 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:16 +0000 UTC debug: handling reboot state
2019-05-10 12:32:16 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:32:16 +0000 UTC info: rebooting device
2019-05-10 12:32:16 +0000 UTC info: Mender rebooting from active partition: /dev/mmcblk0p2
2019-05-10 12:32:40 +0000 UTC debug: handling state after reboot
2019-05-10 12:32:40 +0000 UTC info: State transition: after-reboot [ArtifactReboot_Leave] -> update-verify [ArtifactReboot_Leave]
2019-05-10 12:32:40 +0000 UTC debug: handle update verify state
2019-05-10 12:32:40 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=
2019-05-10 12:32:40 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:]
2019-05-10 12:32:40 +0000 UTC debug: Have U-Boot variable: upgrade_available=1
2019-05-10 12:32:40 +0000 UTC debug: List of U-Boot variables:map[upgrade_available:1]
2019-05-10 12:32:40 +0000 UTC info: State transition: update-verify [ArtifactReboot_Leave] -> update-commit [ArtifactCommit]
2019-05-10 12:32:40 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:40 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:32:40 +0000 UTC debug: handle update commit state
2019-05-10 12:32:40 +0000 UTC debug: Read data from device manifest file: artifact_name=release-1_1.7.1
2019-05-10 12:32:40 +0000 UTC debug: Found needed line: artifact_name=release-1_1.7.1
2019-05-10 12:32:40 +0000 UTC debug: Current manifest data: release-1_1.7.1
2019-05-10 12:32:40 +0000 UTC info: successfully running with new image release-1_1.7.1
2019-05-10 12:32:41 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=
2019-05-10 12:32:41 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:]
2019-05-10 12:32:41 +0000 UTC debug: Have U-Boot variable: upgrade_available=1
2019-05-10 12:32:41 +0000 UTC debug: List of U-Boot variables:map[upgrade_available:1]
2019-05-10 12:32:41 +0000 UTC info: Commiting update
2019-05-10 12:32:41 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=
2019-05-10 12:32:41 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:]
2019-05-10 12:32:42 +0000 UTC info: Storing commit state data
2019-05-10 12:32:42 +0000 UTC info: State transition: update-commit [ArtifactCommit] -> update-status-report [none]
2019-05-10 12:32:42 +0000 UTC debug: handle update status report state
2019-05-10 12:32:42 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:32:42 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:32:42 +0000 UTC error: failed to send status to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:32:42 +0000 UTC info: State transition: update-status-report [ArtifactCommit] -> update-retry-report [none]
2019-05-10 12:33:12 +0000 UTC debug: wait complete
2019-05-10 12:33:12 +0000 UTC info: State transition: update-retry-report [ArtifactCommit] -> update-status-report [ArtifactCommit]
2019-05-10 12:33:12 +0000 UTC debug: handle update status report state
2019-05-10 12:33:12 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:12 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:12 +0000 UTC error: failed to send status to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:12 +0000 UTC info: State transition: update-status-report [ArtifactCommit] -> update-retry-report [none]
2019-05-10 12:33:42 +0000 UTC debug: wait complete
2019-05-10 12:33:42 +0000 UTC info: State transition: update-retry-report [ArtifactCommit] -> update-status-report [ArtifactCommit]
2019-05-10 12:33:42 +0000 UTC debug: handle update status report state
2019-05-10 12:33:42 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:42 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:42 +0000 UTC error: failed to send status to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:33:42 +0000 UTC info: State transition: update-status-report [ArtifactCommit] -> update-retry-report [none]
2019-05-10 12:34:12 +0000 UTC debug: wait complete
2019-05-10 12:34:12 +0000 UTC info: State transition: update-retry-report [ArtifactCommit] -> update-status-report [ArtifactCommit]
2019-05-10 12:34:12 +0000 UTC debug: handle update status report state
2019-05-10 12:34:12 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:34:12 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:34:12 +0000 UTC error: failed to send status to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp: lookup docker.mender.io on [2001:4860:4860::8888]:53: dial udp [2001:4860:4860::8888]:53: connect: network is unreachable
2019-05-10 12:34:12 +0000 UTC info: State transition: update-status-report [ArtifactCommit] -> update-retry-report [none]
2019-05-10 12:34:12 +0000 UTC info: State transition: update-retry-report [ArtifactCommit] -> status-report-error [ArtifactFailure]
2019-05-10 12:34:12 +0000 UTC debug: transitioning to error state
2019-05-10 12:34:12 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:12 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:12 +0000 UTC error: handling report error state with status: success
2019-05-10 12:34:12 +0000 UTC info: State transition: status-report-error [ArtifactFailure] -> rollback [ArtifactRollback]
2019-05-10 12:34:12 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:12 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:12 +0000 UTC info: performing rollback
2019-05-10 12:34:12 +0000 UTC debug: Active partition: /dev/mmcblk0p3
2019-05-10 12:34:12 +0000 UTC debug: Detected inactive partition /dev/mmcblk0p2, based on active partition /dev/mmcblk0p3
2019-05-10 12:34:12 +0000 UTC debug: Marking inactive partition (/dev/mmcblk0p2) as the new boot candidate.
2019-05-10 12:34:12 +0000 UTC info: setting partition for rollback: 2
2019-05-10 12:34:12 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=
2019-05-10 12:34:12 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:]
2019-05-10 12:34:13 +0000 UTC debug: Marking inactive partition as a boot candidate successful.
2019-05-10 12:34:13 +0000 UTC debug: will try to rollback reboot the device
2019-05-10 12:34:13 +0000 UTC info: State transition: rollback [ArtifactRollback] -> rollback-reboot [ArtifactRollbackReboot_Enter]
2019-05-10 12:34:13 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:13 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:13 +0000 UTC info: rebooting device after rollback
2019-05-10 12:34:13 +0000 UTC info: Mender rebooting from active partition: /dev/mmcblk0p3
2019-05-10 12:34:32 +0000 UTC debug: handling state after rollback reboot
2019-05-10 12:34:33 +0000 UTC info: State transition: after-rollback-reboot [ArtifactRollbackReboot_Leave] -> update-error [ArtifactFailure]
2019-05-10 12:34:33 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:33 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 60 seconds
2019-05-10 12:34:33 +0000 UTC debug: handle update error state
2019-05-10 12:34:33 +0000 UTC info: State transition: update-error [ArtifactFailure] -> update-status-report [none]
2019-05-10 12:34:33 +0000 UTC debug: handle update status report state
2019-05-10 12:34:33 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp 192.168.1.248:443: connect: network is unreachable
2019-05-10 12:34:33 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp 192.168.1.248:443: connect: network is unreachable
2019-05-10 12:34:33 +0000 UTC error: failed to send status to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp 192.168.1.248:443: connect: network is unreachable
2019-05-10 12:34:33 +0000 UTC info: State transition: update-status-report [ArtifactFailure] -> update-retry-report [none]
2019-05-10 12:35:01 +0000 UTC debug: wait complete
2019-05-10 12:35:01 +0000 UTC info: State transition: update-retry-report [ArtifactFailure] -> update-status-report [ArtifactFailure]
2019-05-10 12:35:01 +0000 UTC debug: handle update status report state
2019-05-10 12:35:53 +0000 UTC debug: status reported, response 204 No Content
2019-05-10 12:35:53 +0000 UTC debug: attempting to upload deployment logs for failed update

Edit: @mirzak: embed log in post

mirzak · May 11, 2019, 7:37pm

Posting the same question 3 times (+ sending an email) will not speed up the process of you getting an answer. It might even have the opposite effect.

Please be patient while waiting for an answer.

mirzak · May 13, 2019, 6:17am

You deployment is marked as failed because it is not able to reach the Mender server after you have updated, and thus will perform a roll-back.

These error messages:

2019-05-10 12:34:33 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/12a3e3ef-e4e2-45c7-8c43-ce64ec37fb64/status: dial tcp 192.168.1.248:443: connect: network is unreachable

Unclear why this would be case, and please verify that the above address is correct.

mirzak · May 13, 2019, 6:41am

All the necessary commands, when you are working with demo images and are deploying to physical devices are here,

https://docs.mender.io/2.0/getting-started/deploy-to-physical-devices

gpram · May 13, 2019, 9:17am

am using 1.7 version…

mirzak · May 13, 2019, 9:27am

The documantion for 1.7 is here, and should cover all the necessary steps,

https://docs.mender.io/1.7/getting-started/deploy-to-physical-devices

Topic		Replies	Views
Mender deployment error Expected \"upgrade_available\" flag to be true but it was false General Discussions x86	5	1204	January 13, 2023
View logs through Mender web UI of successful deployments? General Discussions	3	675	August 3, 2021
Deployment management for failures and new devices General Discussions deployment	3	557	February 10, 2020
Mender OTA Update successful but reported by Enterprise server as a failure General Discussions	5	543	February 7, 2022
Mender deployment failure General Discussions hosted-mender , deployment	1	881	January 31, 2020

Physical device deployment failure please check attachment log file and screenshot

Related Topics