FOTA Failed for BBB

General Discussions
1

Hi Everyone,

I am trying the mender FOTA by demo mender setup. i am running a server in PC and i am getting data also at server side. so now i am trying to do a fota to a client device which is running in the BBB.
i attached the artifacts into the release section of mender demo server which i created by some steps(@drewmoseley, @mirzak ) i am loading the .mender file which is available in the deploy folder.
after deployment i am getting failed status.
here is the logs attached please let me the problem.

mender2
mender2.png1920Ă—1080 467 KB
mender3
mender3.png1920Ă—1080 452 KB
Mender1
Mender1.png1920Ă—1080 468 KB

2

Please share the logs in text format, and please copy/paste the log that you get on the server

3

new user can upload 10 links only

getting this error while copping and pasting in the comment session.
i can’t able to attach the txt file.

4

Do not attach it, just copy/paste it here using :

```
paste here
```
5 
2019-10-25 06:24:40 +0000 UTC info: Running Mender version 2.0.1
2019-10-25 06:24:40 +0000 UTC debug: handle update fetch state
2019-10-25 06:24:40 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:24:41 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Vary:[Origin] X-Content-Type-Options:[nosniff] Content-Length:[805706240] Accept-Ranges:[bytes] Last-Modified:[Fri, 25 Oct 2019 06:24:24 GMT] Strict-Transport-Security:[max-age=0; includeSubdomains; preload] Date:[Fri, 25 Oct 2019 06:24:41 GMT] Connection:[keep-alive] Content-Security-Policy:[block-all-mixed-content] X-Xss-Protection:[1; mode=block] X-Frame-Options:[DENY] Server:[openresty/1.13.6.2] Content-Type:[application/vnd.mender-artifact] X-Amz-Request-Id:[15D0CFBD1AD22764] Etag:["323772449c3b7c679313b2b7b7e43953"]] 0x196a550 805706240 [] false false map[] 0x188b300 0x1873800}+
2019-10-25 06:24:41 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2019-10-25 06:24:41 +0000 UTC debug: handle update install state
2019-10-25 06:24:41 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:24:41 +0000 UTC debug: Read data from device manifest file: device_type=beaglebone-sdcard
2019-10-25 06:24:41 +0000 UTC debug: Current manifest data: beaglebone-sdcard
2019-10-25 06:24:41 +0000 UTC info: no public key was provided for authenticating the artifact
2019-10-25 06:24:41 +0000 UTC debug: checking if device [beaglebone-sdcard] is on compatibile device list: [beaglebone-sdcard]
2019-10-25 06:24:41 +0000 UTC debug: installer: successfully read artifact [name: Nestle_VER_3.0.12; version: 3; compatible devices: [beaglebone-sdcard]]
2019-10-25 06:24:41 +0000 UTC debug: Trying to install update of size: 2717913088
2019-10-25 06:24:41 +0000 UTC debug: Active partition: /dev/mmcblk0p3
2019-10-25 06:24:41 +0000 UTC debug: Detected inactive partition /dev/mmcblk0p2, based on active partition /dev/mmcblk0p3
2019-10-25 06:24:41 +0000 UTC info: native sector size of block device /dev/mmcblk0p2 is 512, we will write in chunks of 1048576
2019-10-25 06:24:41 +0000 UTC info: opening device /dev/mmcblk0p2 for writing
2019-10-25 06:24:41 +0000 UTC info: partition /dev/mmcblk0p2 size: 4194304000
2019-10-25 06:38:36 +0000 UTC info: wrote 2717913088/2717913088 bytes of update to device /dev/mmcblk0p2
2019-10-25 06:38:37 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:38:37 +0000 UTC info: State transition: update-store [Download_Enter] -> update-after-store [Download_Leave]
2019-10-25 06:38:37 +0000 UTC info: State transition: update-after-store [Download_Leave] -> update-install [ArtifactInstall]
2019-10-25 06:38:37 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:38:37 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:38:37 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:38:37 +0000 UTC debug: Inactive partition: /dev/mmcblk0p2
2019-10-25 06:38:37 +0000 UTC debug: Marking inactive partition (/dev/mmcblk0p2) as the new boot candidate.
2019-10-25 06:38:37 +0000 UTC info: Enabling partition with new image installed to be a boot candidate: 2
2019-10-25 06:38:37 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=1
2019-10-25 06:38:37 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:1]
2019-10-25 06:38:37 +0000 UTC debug: Have U-Boot variable: mender_saveenv_canary=1
2019-10-25 06:38:37 +0000 UTC debug: List of U-Boot variables:map[mender_saveenv_canary:1]
2019-10-25 06:38:37 +0000 UTC debug: Marking inactive partition as a boot candidate successful.
2019-10-25 06:38:37 +0000 UTC info: State transition: update-install [ArtifactInstall] -> reboot [ArtifactReboot_Enter]
2019-10-25 06:38:37 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:38:37 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:38:37 +0000 UTC debug: handling reboot state
2019-10-25 06:38:37 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:38:37 +0000 UTC info: rebooting device(s)
2019-10-25 06:38:37 +0000 UTC info: Mender rebooting from active partition: /dev/mmcblk0p3
2019-10-25 06:39:13 +0000 UTC info: Running Mender version 2.0.1
2019-10-25 06:39:13 +0000 UTC info: State transition: init [none] -> after-reboot [ArtifactReboot_Leave]
2019-10-25 06:39:13 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=1
2019-10-25 06:39:13 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:1]
2019-10-25 06:39:13 +0000 UTC debug: Have U-Boot variable: mender_saveenv_canary=1
2019-10-25 06:39:13 +0000 UTC debug: List of U-Boot variables:map[mender_saveenv_canary:1]
2019-10-25 06:39:14 +0000 UTC debug: Have U-Boot variable: upgrade_available=1
2019-10-25 06:39:14 +0000 UTC debug: List of U-Boot variables:map[upgrade_available:1]
2019-10-25 06:39:14 +0000 UTC info: State transition: after-reboot [ArtifactReboot_Leave] -> after-reboot [ArtifactReboot_Leave]
2019-10-25 06:39:14 +0000 UTC debug: handling state after reboot
2019-10-25 06:39:14 +0000 UTC info: State transition: after-reboot [ArtifactReboot_Leave] -> update-commit [ArtifactCommit_Enter]
2019-10-25 06:39:14 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:39:14 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:39:14 +0000 UTC debug: handle update commit state
2019-10-25 06:39:17 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:17 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:17 +0000 UTC error: Failed to send status report to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:17 +0000 UTC info: State transition: update-commit [ArtifactCommit_Enter] -> update-pre-commit-status-report-retry [ArtifactCommit_Enter]
2019-10-25 06:39:46 +0000 UTC debug: wait complete
2019-10-25 06:39:46 +0000 UTC info: State transition: update-pre-commit-status-report-retry [ArtifactCommit_Enter] -> update-commit [ArtifactCommit_Enter]
2019-10-25 06:39:46 +0000 UTC debug: handle update commit state
2019-10-25 06:39:49 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:49 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:49 +0000 UTC error: Failed to send status report to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:49 +0000 UTC info: State transition: update-commit [ArtifactCommit_Enter] -> update-pre-commit-status-report-retry [ArtifactCommit_Enter]
2019-10-25 06:40:19 +0000 UTC debug: wait complete
2019-10-25 06:40:19 +0000 UTC info: State transition: update-pre-commit-status-report-retry [ArtifactCommit_Enter] -> update-commit [ArtifactCommit_Enter]
2019-10-25 06:40:19 +0000 UTC debug: handle update commit state
2019-10-25 06:40:22 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:22 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:22 +0000 UTC error: Failed to send status report to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:22 +0000 UTC info: State transition: update-commit [ArtifactCommit_Enter] -> update-pre-commit-status-report-retry [ArtifactCommit_Enter]
2019-10-25 06:40:52 +0000 UTC debug: wait complete
2019-10-25 06:40:52 +0000 UTC info: State transition: update-pre-commit-status-report-retry [ArtifactCommit_Enter] -> update-commit [ArtifactCommit_Enter]
2019-10-25 06:40:52 +0000 UTC debug: handle update commit state
2019-10-25 06:40:55 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:55 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:55 +0000 UTC error: Failed to send status report to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:40:55 +0000 UTC info: State transition: update-commit [ArtifactCommit_Enter] -> update-pre-commit-status-report-retry [ArtifactCommit_Enter]
2019-10-25 06:40:55 +0000 UTC error: transient error: Tried sending status report maximum number of times.
2019-10-25 06:40:55 +0000 UTC info: State transition: update-pre-commit-status-report-retry [ArtifactCommit_Enter] -> rollback [ArtifactRollback]
2019-10-25 06:40:55 +0000 UTC debug: transitioning to error state
2019-10-25 06:40:55 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:40:55 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:40:55 +0000 UTC info: performing rollback
2019-10-25 06:40:55 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=1
2019-10-25 06:40:55 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:1]
2019-10-25 06:40:55 +0000 UTC debug: Have U-Boot variable: mender_saveenv_canary=1
2019-10-25 06:40:55 +0000 UTC debug: List of U-Boot variables:map[mender_saveenv_canary:1]
2019-10-25 06:40:55 +0000 UTC debug: Have U-Boot variable: upgrade_available=1
2019-10-25 06:40:55 +0000 UTC debug: List of U-Boot variables:map[upgrade_available:1]
2019-10-25 06:40:55 +0000 UTC debug: Active partition: /dev/mmcblk0p2
2019-10-25 06:40:55 +0000 UTC debug: Detected inactive partition /dev/mmcblk0p3, based on active partition /dev/mmcblk0p2
2019-10-25 06:40:55 +0000 UTC debug: Marking inactive partition (/dev/mmcblk0p3) as the new boot candidate.
2019-10-25 06:40:55 +0000 UTC info: setting partition for rollback: 3
2019-10-25 06:40:55 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=1
2019-10-25 06:40:56 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:1]
2019-10-25 06:40:56 +0000 UTC debug: Have U-Boot variable: mender_saveenv_canary=1
2019-10-25 06:40:56 +0000 UTC debug: List of U-Boot variables:map[mender_saveenv_canary:1]
2019-10-25 06:40:56 +0000 UTC debug: Marking inactive partition as a boot candidate successful.
2019-10-25 06:40:56 +0000 UTC debug: will try to rollback reboot the device
2019-10-25 06:40:56 +0000 UTC info: State transition: rollback [ArtifactRollback] -> rollback-reboot [ArtifactRollbackReboot_Enter]
2019-10-25 06:40:56 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:40:56 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:40:56 +0000 UTC info: rebooting device(s) after rollback
2019-10-25 06:40:56 +0000 UTC info: Mender rebooting from inactive partition: /dev/mmcblk0p2
2019-10-25 06:41:30 +0000 UTC info: Running Mender version 2.0.1
2019-10-25 06:41:30 +0000 UTC info: Update was interrupted in state: rollback-reboot
2019-10-25 06:41:30 +0000 UTC info: State transition: init [none] -> verify-rollback-reboot [ArtifactRollbackReboot_Leave]
2019-10-25 06:41:30 +0000 UTC debug: transitioning to error state
2019-10-25 06:41:30 +0000 UTC debug: Have U-Boot variable: mender_check_saveenv_canary=1
2019-10-25 06:41:30 +0000 UTC debug: List of U-Boot variables:map[mender_check_saveenv_canary:1]
2019-10-25 06:41:30 +0000 UTC debug: Have U-Boot variable: mender_saveenv_canary=1
2019-10-25 06:41:30 +0000 UTC debug: List of U-Boot variables:map[mender_saveenv_canary:1]
2019-10-25 06:41:30 +0000 UTC debug: Have U-Boot variable: upgrade_available=0
2019-10-25 06:41:30 +0000 UTC debug: List of U-Boot variables:map[upgrade_available:0]
2019-10-25 06:41:30 +0000 UTC info: State transition: verify-rollback-reboot [ArtifactRollbackReboot_Leave] -> after-rollback-reboot [ArtifactRollbackReboot_Leave]
2019-10-25 06:41:31 +0000 UTC debug: handling state after rollback reboot
2019-10-25 06:41:31 +0000 UTC info: State transition: after-rollback-reboot [ArtifactRollbackReboot_Leave] -> update-error [ArtifactFailure]
2019-10-25 06:41:31 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:41:31 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:41:31 +0000 UTC debug: handle update error state
2019-10-25 06:41:31 +0000 UTC info: State transition: update-error [ArtifactFailure] -> cleanup [Error]
2019-10-25 06:41:31 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:41:31 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:41:31 +0000 UTC debug: Handling Cleanup state
2019-10-25 06:41:31 +0000 UTC info: State transition: cleanup [Error] -> update-status-report [none]
2019-10-25 06:41:31 +0000 UTC debug: statescript: timeout for executing scripts is not defined; using default of 1h0m0s seconds
2019-10-25 06:41:31 +0000 UTC debug: handle update status report state
2019-10-25 06:41:32 +0000 UTC debug: status reported, response 204 No Content
2019-10-25 06:41:32 +0000 UTC debug: attempting to upload deployment logs for failed update

Edit: @mirzak: formatting

6 
2019-10-25 06:39:17 +0000 UTC error: failed to report status: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:17 +0000 UTC error: error reporting update status: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host
2019-10-25 06:39:17 +0000 UTC error: Failed to send status report to server: transient error: reporting status failed: Put https://docker.mender.io/api/devices/v1/deployments/device/deployments/bb38db66-b7cb-423a-b57a-808ece42d9e5/status: dial tcp 192.168.1.65:443: connect: no route to host

It seems that you have a connectivity problem in the “new” Artifact, meaning that the Mender client was not able to reconnect to the Mender server, and for this reason rolled back.

What is your /etc/mender/mender.conf content? Are you using WiFi or wired connectivity?

1 Like
7

i am using wired (Ethernet) Connectivity for beagle bone and Server (PC) also.
content in file mender.conf

jithu@ibot032:~/mender-convert/rootfs_overlay_demo/etc/mender$ cat mender.conf
{
“InventoryPollIntervalSeconds”: 5,
“RetryPollIntervalSeconds”: 30,
“ServerURL”: “https://docker.mender.io”,
“ServerCertificate”: “/etc/mender/server.crt”,
“UpdatePollIntervalSeconds”: 5
}

8

yes mirzak,

you are correct, i have created a new image .mender and deployed it again. so now its successfully loaded.
Thanks.

9

Thanks for reporting back, and glad to hear that you where successful.

1 Like