Bitbake core-image-minimal error

General Discussions
#36

Hi drawmoseley,
The deployments results found the following problems . please help me solve.Thanks!

2020-11-10 06:41:11 +0000 UTC debug: handle update fetch state
2020-11-10 06:41:11 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:41:11 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Accept-Ranges:[bytes] Content-Security-Policy:[block-all-mixed-content] Etag:[“0424dd61518bc968641efb3ce7514d7e-4”] X-Xss-Protection:[1; mode=block] X-Frame-Options:[DENY] X-Content-Type-Options:[nosniff] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Content-Type:[application/vnd.mender-artifact] Content-Length:[35420672] Last-Modified:[Tue, 10 Nov 2020 06:23:47 GMT] Vary:[Origin] X-Amz-Request-Id:[1646125481C58E7D] Server:[openresty/1.13.6.2] Date:[Tue, 10 Nov 2020 06:41:11 GMT] Connection:[keep-alive] Expires:[Tue, 10 Nov 2020 06:33:38 GMT]] 0x120632e0 35420672 [] false false map[] 0x11f7b800 0x11fb99e0}+
2020-11-10 06:41:11 +0000 UTC info: State transition: update-fetch [Download] -> update-store [Download]
2020-11-10 06:41:11 +0000 UTC debug: handle update install state
2020-11-10 06:41:11 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:41:11 +0000 UTC debug: Read data from device manifest file: device_type=imx6ull14x14evk
2020-11-10 06:41:11 +0000 UTC debug: Found needed line: device_type=imx6ull14x14evk
2020-11-10 06:41:11 +0000 UTC debug: Current manifest data: imx6ull14x14evk
2020-11-10 06:41:11 +0000 UTC info: no public key was provided for authenticating the artifact
2020-11-10 06:41:11 +0000 UTC debug: checking if device [imx6ull14x14evk] is on compatibile device list: [imx6ull14x14evk]
2020-11-10 06:41:11 +0000 UTC debug: installing update core-image-base-imx6ull14x14evk.ext4 of size 180355072
2020-11-10 06:41:11 +0000 UTC debug: Trying to install update of size: 180355072
2020-11-10 06:41:11 +0000 UTC debug: Active partition: /dev/mmcblk1p4
2020-11-10 06:41:11 +0000 UTC debug: Detected inactive partition /dev/mmcblk1p3, based on active partition /dev/mmcblk1p4
2020-11-10 06:41:11 +0000 UTC warning: Inactive partition “/dev/mmcblk1p3” is mounted at “/uboot”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.
2020-11-10 06:41:11 +0000 UTC warning: Performing umount on “/uboot”.
2020-11-10 06:41:11 +0000 UTC error: Error unmounting partition /dev/mmcblk1p3
2020-11-10 06:41:11 +0000 UTC error: update image installation failed: invalid argument
2020-11-10 06:41:11 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{core-image-base-imx6ull14x14evk.ext4 420 1000 1000 180355072 2020-11-10 05:21:01 +0000 UTC 48 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map[]}: update: can not install: invalid argument
2020-11-10 06:41:11 +0000 UTC info: State transition: update-store [Download] -> fetch-install-retry-wait [Download]
2020-11-10 06:41:11 +0000 UTC debug: handle fetch install retry state
2020-11-10 06:41:11 +0000 UTC debug: wait 1m0s before next fetch/install attempt
2020-11-10 06:42:11 +0000 UTC debug: wait complete
2020-11-10 06:42:11 +0000 UTC info: State transition: fetch-install-retry-wait [Download] -> update-fetch [Download]
2020-11-10 06:42:11 +0000 UTC debug: handle update fetch state
2020-11-10 06:42:11 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:42:11 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Last-Modified:[Tue, 10 Nov 2020 06:23:47 GMT] Vary:[Origin] X-Content-Type-Options:[nosniff] Accept-Ranges:[bytes] X-Amz-Request-Id:[164612629AA23C80] X-Xss-Protection:[1; mode=block] Date:[Tue, 10 Nov 2020 06:42:11 GMT] Content-Type:[application/vnd.mender-artifact] Expires:[Tue, 10 Nov 2020 06:33:38 GMT] Server:[openresty/1.13.6.2] Content-Length:[35420672] Connection:[keep-alive] Content-Security-Policy:[block-all-mixed-content] Etag:[“0424dd61518bc968641efb3ce7514d7e-4”] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] X-Frame-Options:[DENY]] 0x12052270 35420672 [] false false map[] 0x11f7bc00 0x122cec60}+
2020-11-10 06:42:11 +0000 UTC info: State transition: update-fetch [Download] -> update-store [Download]
2020-11-10 06:42:11 +0000 UTC debug: handle update install state
2020-11-10 06:42:11 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:42:11 +0000 UTC debug: Read data from device manifest file: device_type=imx6ull14x14evk
2020-11-10 06:42:11 +0000 UTC debug: Found needed line: device_type=imx6ull14x14evk
2020-11-10 06:42:11 +0000 UTC debug: Current manifest data: imx6ull14x14evk
2020-11-10 06:42:11 +0000 UTC info: no public key was provided for authenticating the artifact
2020-11-10 06:42:12 +0000 UTC debug: checking if device [imx6ull14x14evk] is on compatibile device list: [imx6ull14x14evk]
2020-11-10 06:42:12 +0000 UTC debug: installing update core-image-base-imx6ull14x14evk.ext4 of size 180355072
2020-11-10 06:42:12 +0000 UTC debug: Trying to install update of size: 180355072
2020-11-10 06:42:12 +0000 UTC debug: Inactive partition: /dev/mmcblk1p3
2020-11-10 06:42:12 +0000 UTC warning: Inactive partition “/dev/mmcblk1p3” is mounted at “/uboot”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.
2020-11-10 06:42:12 +0000 UTC warning: Performing umount on “/uboot”.
2020-11-10 06:42:12 +0000 UTC error: Error unmounting partition /dev/mmcblk1p3
2020-11-10 06:42:12 +0000 UTC error: update image installation failed: invalid argument
2020-11-10 06:42:12 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{core-image-base-imx6ull14x14evk.ext4 420 1000 1000 180355072 2020-11-10 05:21:01 +0000 UTC 48 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map[]}: update: can not install: invalid argument
2020-11-10 06:42:12 +0000 UTC info: State transition: update-store [Download] -> fetch-install-retry-wait [Download]
2020-11-10 06:42:12 +0000 UTC debug: handle fetch install retry state
2020-11-10 06:42:12 +0000 UTC debug: wait 1m0s before next fetch/install attempt
2020-11-10 06:43:12 +0000 UTC debug: wait complete
2020-11-10 06:43:12 +0000 UTC info: State transition: fetch-install-retry-wait [Download] -> update-fetch [Download]
2020-11-10 06:43:12 +0000 UTC debug: handle update fetch state
2020-11-10 06:43:12 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:43:12 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Etag:[“0424dd61518bc968641efb3ce7514d7e-4”] X-Content-Type-Options:[nosniff] Server:[openresty/1.13.6.2] Content-Length:[35420672] Connection:[keep-alive] Accept-Ranges:[bytes] Vary:[Origin] X-Xss-Protection:[1; mode=block] X-Frame-Options:[DENY] Date:[Tue, 10 Nov 2020 06:43:12 GMT] Content-Type:[application/vnd.mender-artifact] Content-Security-Policy:[block-all-mixed-content] Expires:[Tue, 10 Nov 2020 06:33:38 GMT] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Last-Modified:[Tue, 10 Nov 2020 06:23:47 GMT] X-Amz-Request-Id:[16461270B635959A]] 0x12062600 35420672 [] false false map[] 0x11f7a200 0x11fb8720}+
2020-11-10 06:43:12 +0000 UTC info: State transition: update-fetch [Download] -> update-store [Download]
2020-11-10 06:43:12 +0000 UTC debug: handle update install state
2020-11-10 06:43:12 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:43:12 +0000 UTC debug: Read data from device manifest file: device_type=imx6ull14x14evk
2020-11-10 06:43:12 +0000 UTC debug: Found needed line: device_type=imx6ull14x14evk
2020-11-10 06:43:12 +0000 UTC debug: Current manifest data: imx6ull14x14evk
2020-11-10 06:43:12 +0000 UTC info: no public key was provided for authenticating the artifact
2020-11-10 06:43:12 +0000 UTC debug: checking if device [imx6ull14x14evk] is on compatibile device list: [imx6ull14x14evk]
2020-11-10 06:43:12 +0000 UTC debug: installing update core-image-base-imx6ull14x14evk.ext4 of size 180355072
2020-11-10 06:43:12 +0000 UTC debug: Trying to install update of size: 180355072
2020-11-10 06:43:12 +0000 UTC debug: Inactive partition: /dev/mmcblk1p3
2020-11-10 06:43:12 +0000 UTC warning: Inactive partition “/dev/mmcblk1p3” is mounted at “/uboot”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.
2020-11-10 06:43:12 +0000 UTC warning: Performing umount on “/uboot”.
2020-11-10 06:43:12 +0000 UTC error: Error unmounting partition /dev/mmcblk1p3
2020-11-10 06:43:12 +0000 UTC error: update image installation failed: invalid argument
2020-11-10 06:43:12 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{core-image-base-imx6ull14x14evk.ext4 420 1000 1000 180355072 2020-11-10 05:21:01 +0000 UTC 48 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map[]}: update: can not install: invalid argument
2020-11-10 06:43:12 +0000 UTC info: State transition: update-store [Download] -> fetch-install-retry-wait [Download]
2020-11-10 06:43:12 +0000 UTC debug: handle fetch install retry state
2020-11-10 06:43:12 +0000 UTC debug: wait 1m0s before next fetch/install attempt
2020-11-10 06:44:12 +0000 UTC debug: wait complete
2020-11-10 06:44:12 +0000 UTC info: State transition: fetch-install-retry-wait [Download] -> update-fetch [Download]
2020-11-10 06:44:12 +0000 UTC debug: handle update fetch state
2020-11-10 06:44:12 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:44:13 +0000 UTC debug: Received fetch update response &{200 OK 200 HTTP/1.1 1 1 map[Content-Type:[application/vnd.mender-artifact] Etag:[“0424dd61518bc968641efb3ce7514d7e-4”] Vary:[Origin] X-Amz-Request-Id:[1646127ECD80FC10] X-Xss-Protection:[1; mode=block] X-Frame-Options:[DENY] Server:[openresty/1.13.6.2] Content-Security-Policy:[block-all-mixed-content] X-Content-Type-Options:[nosniff] Content-Length:[35420672] Connection:[keep-alive] Accept-Ranges:[bytes] Strict-Transport-Security:[max-age=63072000; includeSubdomains; preload] Date:[Tue, 10 Nov 2020 06:44:13 GMT] Last-Modified:[Tue, 10 Nov 2020 06:23:47 GMT] Expires:[Tue, 10 Nov 2020 06:33:38 GMT]] 0x120634f0 35420672 [] false false map[] 0x11f7a680 0x11fb99e0}+
2020-11-10 06:44:13 +0000 UTC info: State transition: update-fetch [Download] -> update-store [Download]
2020-11-10 06:44:13 +0000 UTC debug: handle update install state
2020-11-10 06:44:13 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:44:13 +0000 UTC debug: Read data from device manifest file: device_type=imx6ull14x14evk
2020-11-10 06:44:13 +0000 UTC debug: Found needed line: device_type=imx6ull14x14evk
2020-11-10 06:44:13 +0000 UTC debug: Current manifest data: imx6ull14x14evk
2020-11-10 06:44:13 +0000 UTC info: no public key was provided for authenticating the artifact
2020-11-10 06:44:13 +0000 UTC debug: checking if device [imx6ull14x14evk] is on compatibile device list: [imx6ull14x14evk]
2020-11-10 06:44:13 +0000 UTC debug: installing update core-image-base-imx6ull14x14evk.ext4 of size 180355072
2020-11-10 06:44:13 +0000 UTC debug: Trying to install update of size: 180355072
2020-11-10 06:44:13 +0000 UTC debug: Inactive partition: /dev/mmcblk1p3
2020-11-10 06:44:13 +0000 UTC warning: Inactive partition “/dev/mmcblk1p3” is mounted at “/uboot”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.
2020-11-10 06:44:13 +0000 UTC warning: Performing umount on “/uboot”.
2020-11-10 06:44:13 +0000 UTC error: Error unmounting partition /dev/mmcblk1p3
2020-11-10 06:44:13 +0000 UTC error: update image installation failed: invalid argument
2020-11-10 06:44:13 +0000 UTC error: update install failed: installer: failed to read and install update: update: can not install update: &{core-image-base-imx6ull14x14evk.ext4 420 1000 1000 180355072 2020-11-10 05:21:01 +0000 UTC 48 0 0 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC map[]}: update: can not install: invalid argument
2020-11-10 06:44:13 +0000 UTC info: State transition: update-store [Download] -> fetch-install-retry-wait [Download]
2020-11-10 06:44:13 +0000 UTC debug: handle fetch install retry state
2020-11-10 06:44:13 +0000 UTC info: State transition: fetch-install-retry-wait [Download] -> update-status-report [none]
2020-11-10 06:44:13 +0000 UTC debug: handle update status report state
2020-11-10 06:44:13 +0000 UTC debug: status reported, response 204 No Content
2020-11-10 06:44:13 +0000 UTC debug: attempting to upload deployment logs for failed update

#37

My initial guess is that your partition numbering is incorrect:

2020-11-10 06:43:12 +0000 UTC debug: Trying to install update of size: 180355072
2020-11-10 06:43:12 +0000 UTC debug: Inactive partition: /dev/mmcblk1p3
2020-11-10 06:43:12 +0000 UTC warning: Inactive partition “/dev/mmcblk1p3” is mounted at “/uboot”. This might be caused by some “auto mount” service (e.g udisks2) that mounts all block devices. It is recommended to blacklist the partitions used by Mender to avoid any issues.
2020-11-10 06:43:12 +0000 UTC warning: Performing umount on “/uboot”.

You seem to have a boot partition at mmcblk1p3 but for some reason Mender is configured to use that as a root filesystem. Can you run the following command and provide the output?

bitbake -e core-image-minimal | grep ^MENDER_

#38

Hi drewmoseley,
If the number of device exceeds 1000, is it only necessary to manually create a groups? Is there a smarter way to create a groups (for example, writing commands in the background can put customers in the same country in the same group)?

Best regards

#39

With Mender Enterprise, we do have some smarter grouping and filtering features that can help. The alternative would be to code up something using the API.

Drew

#40

Hi drewmoseley,
1. Can I import excel database into the sample program of mender API?
2. Why does it take 10 minutes for a customer’s device to use a 4G hotspot to connect to the mender server? Is there a solution?

kirsty
Best regards

#41

Hi @triampmeili

Regarding the excel database, I’m not sure what you are trying to do. We do have a single file update module that will copy one file onto the target.

As for the device connection time, it’s hard to say. Devices need to have a synchronized time source using NTP before the TLS certificates can be validated. That can be one source of delay. If you can provide the output from running journalctl -u mender-client on the device that took so long, we may be able to see other things.

Drew

#42

Hi drewmoseley,

   Thanks for your help.
   My Mender Server Starter has a deployment that cannot be deleted, the error message is as follows: There was wan error while aborting the deployment: Deployment already finished [Request ID: 9c1b2e3c]

please tell how to detele？Thanks!

#43

The error message indicates that it has completed. What is the purpose of deleting it? We don’t support that. If a deployment is in progress, it can be aborted but once it has finished, there is nothing to delete or abort.

#44

1
11156×462 20.9 KB
2
21078×469 33.8 KB

I want to delete this deployments.

#45

Strange. If you refresh the page, does anything change? Change you post a screen shot of the whole UI when the deployments tab is open?

#46

I refresh the page can’t change anything.

#47

How can i do this? Thanks

#48

NTP is a big topic and it’s going to depend a lot on your OS/Distro setup. Since this thread is ostensibly about a Yocto build, assuming you are using the standard systemd-based configuration then you just need to make sure that the timesyncd option is enabled in the system recipe PACKAGECONFIG.

Is your deployment issue on one of our hosted instances or are you using a self-hosted server? If it is our instance, can you provide the deployment ID?

#49

My deployment issue on your hosted. I don’t know what our deployment ID is?

#50

It should be visible in the deployment details screen.

#51

triamp@triamp-Macmini:~$ curl -H “Authorization: Bearer $JWT” $MENDER_SERVER_URI/api/management/v1/deployments/deployments/1a694a4e-882b-4d53-a1b2-a3cced36c9ef
{“name”:“test”,“artifact_name”:“release-test-0904-2”,“created”:“2020-11-23T02:41:38.614Z”,“finished”:“2020-11-23T02:42:25.763Z”,“id”:“1a694a4e-882b-4d53-a1b2-a3cced36c9ef”,“artifacts”:[“ee52791d-104c-40f5-9d40-2e62cf8dbd88”],“status”:“finished”,“device_count”:0,“max_devices”:2}

What command do i need to delete the deployment? Thanks!

#52

What command do i need to read finished status( success, failure, already-installed, aborded)?

Thanks!

#53

What command do i need to delete the deployment? Thanks!

You cannot as far as I know. What I don’t understand is why the GUI continues to show the deployment as your curl command clearly shows the status as Finished. @mzedel @tranchitella do you guys have any idea on this one?

What command do i need to read finished status( success, failure, already-installed, aborded)?

You can use something like

curl -X GET -H "Authorization: Bearer $JWT" https://hosted.mender.io/api/management/v1/deployments/deployments?status=scheduled

but note that is only the status of the deployment as a whole. Valid values for the status are scheduled, pending, inprogress and finished. To determine the reason for an individual failure you need to something like

curl -X GET -H "Authorization: Bearer $JWT" https://hosted.mender.io/api/management/v1/deployments/deployments/${id}

using the id you found earlier.

#54

Hi drewmoseley,
I’d like to know if there is customerized Mender server or not. If there is, please advise me . Thank you in advance!

#55

Hi @triampmeili I’m not sure what you mean by “customerized” version. You can see the details of our plans here. Let me know if that doesn’t address your question.

Drew