are the network unreachable errors from when you boot up the device?
I’m not sure core-image-minimal is appropriate here. I seem to recall that it does not necessarily have all the bits needed for networking. Can you try with core-image-base?
I have used bitbake core-image-base to build.
I have completed the production mender server, but my device(imx6ullevk) cannot connect to the production mender server I created. Want to ask where is wrong?
Thanks!
Something is wrong with your network settings. Hard to say what. Does removing the mender layers and settings result in an image that connects to the network?
I have build Production mender server, and the following message will appear when you can command in th Terminal. How can I modify it?
command:
sudo ./mender-cli login --server https://mender.example.com:9000 --username user1@host.com --password 123456789
FAILURE: POST /auth/login request failed: Post https://mender.example.com:9000/api/management/v1/useradm/auth/login: x509: certificate signed by unknown authority
One thing to double check is at some point your mender production server IP address changed it was 192.168.0.126 then at some point it changed to 192.168.0.122. Are you using a static IP address for your mender production server? the entry 192.168.0.126 mender.example.com in your /etc/hosts file needs updating if you change the IP address of your mender server.
Also if testing also your desktop machine with curl or mender-cli you also need to repeat the procedure of adding the entry to your /etc/hosts on those machines also for testing.
The production mender server should not be using the name mender.example.com and the keys that are generated with those instructions should have the actual host name embedded. You should just be able to change the server and username parameters to match your server setup.
“mender.triamp.com” for production mode mender can’t not login ok,but “hosted.mender.io” is login ok.
Could you tell me how to fix this bug? Thanks!
If you are using a self-signed certificate you may need to add the -k option to avoid trying to verify the TLS cert of your production server. Of course we recommend using a properly signed certificate for better security.
Drew
Thank you for solving the login failure problem. Then I have question that mender client (imx6ull device) pending to mender server. Below is the screen displayed by the device
NXP i.MX Release Distro 4.14-sumo imx6ull14x14evk ttymxc0
imx6ull14x14evk login: root
root@imx6ull14x14evk:~#
root@imx6ull14x14evk:~#
root@imx6ull14x14evk:~# ifconfig eth1 61.216.xxx.xx up
Micrel KSZ8081 or KSZ8091 20b4000.ethernet-1:02: attached PHY driver [Micrel KSZ
8081 or KSZ8091] (mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
root@imx6ull14x14evk:~# fec 2188000.ethernet eth1: Link is Up - 100Mbps/Full - f
low control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
root@imx6ull14x14evk:~#
root@imx6ull14x14evk:~#
root@imx6ull14x14evk:~# mender -daemon
INFO[0000] Configuration file does not exist: /var/lib/mender/mender.conf modul
e=config
INFO[0000] Loaded configuration file: /etc/mender/mender.conf module=config
INFO[0000] Mender running on partition: /dev/mmcblk1p3 module=main
INFO[0001] API Gateway certificate (in PEM format):
-----BEGIN CERTIFICATE-----
MIIBfzCCASWgAwIBAgIJAPf9g9mjlyXAMAoGCCqGSM49BAMCMBwxGjAYBgNVBAMM
EW1lbmRlci50cmlhbXAuY29tMB4XDTIwMTAyODA0MTQ0NFoXDTMwMTAyNjA0MTQ0
NFowHDEaMBgGA1UEAwwRbWVuZGVyLnRyaWFtcC5jb20wWTATBgcqhkjOPQIBBggq
hkjOPQMBBwNCAATg3zrb80vwAxyD6TErWm20143uuIw/cpv42DgUT0uWF43irZUg
SAPdc3isHpDYXxXd2T3PIZBl7QNlFR3/vULdo1AwTjAdBgNVHQ4EFgQUBEvk6tOs
GsWDJilV0J8Irtkbhb8wHwYDVR0jBBgwFoAUBEvk6tOsGsWDJilV0J8Irtkbhb8w
DAYDVR0TBAUwAwEB/zAKBggqhkjOPQQDAgNIADBFAiAqfP2jyh0g0tz76NNgrH1T
qnTarxTTP9/9jsRFtijQQQIhANWe/U+sA5OErRMJb4WBSHzVAKL7chVdOplN2xw7
16lT
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
MIIBgDCCASWgAwIBAgIJAMw2dV1Znoa5MAoGCCqGSM49BAMCMBwxGjAYBgNVBAMM
EW1lbmRlci50cmlhbXAuY29tMB4XDTIwMTAyODA0MTQ0NFoXDTMwMTAyNjA0MTQ0
NFowHDEaMBgGA1UEAwwRbWVuZGVyLnRyaWFtcC5jb20wWTATBgcqhkjOPQIBBggq
hkjOPQMBBwNCAASBXLoJGjxVdRd4J9e4BtHOMOLbv8johV2u+fkdsMFgTKeUSntT
vAtWpg5AMcvxVHOxqxd61e82nOsTXK+t+55Eo1AwTjAdBgNVHQ4EFgQUuGe+AHN8
ZZpC19aHz+fetJwXyLowHwYDVR0jBBgwFoAUuGe+AHN8ZZpC19aHz+fetJwXyLow
DAYDVR0TBAUwAwEB/zAKBggqhkjOPQQDAgNJADBGAiEApPTPuafzdT0/wZtxpjCR
GQ84EjCmxR7V1LHodC6v7CICIQCvBYnNKYWQFw9fTV7bom85OS7ejh5DLefRdw/k
vAqEhw==
-----END CERTIFICATE-----
module=client
INFO[0001] Issuer: [], Valid from: 2020-10-28 04:14:44 +0000 UTC, Valid to: 2030
-10-26 04:14:44 +0000 UTC module=client
INFO[0001] State transition: init [none] -> init [none] module=mender
INFO[0001] State transition: init [none] -> idle [Idle] module=mender
INFO[0001] State transition: idle [Idle] -> authorize-wait [Idle] module=mender
INFO[0001] State transition: authorize-wait [Idle] -> authorize [Sync] module=m
ender
random: crng init done
random: 7 urandom warning(s) missed due to ratelimiting
ERRO[0045] Failure occured while executing authorization request: &url.Error{Op:
“Post”, URL:“https://mender.triamp.com/api/devices/v1/authentication/auth_reques
ts”, Err:(*net.OpError)(0x11e5f080)} module=client_auth
ERRO[0045] authorization request error: dial tcp 61.216.xxx.xx:443: getsockopt:
connection refused module=client_auth
ERRO[0045] authorize failed: transient error: authorization request failed: gene
ric error occured while executing authorization request: Post https://mender.tri
amp.com/api/devices/v1/authentication/auth_requests: dial tcp 61.216.xxx.xx:443:
getsockopt: connection refused module=state
INFO[0045] State transition: authorize [Sync] -> authorize-wait [Idle] module=m
ender
INFO[0045] State transition: authorize-wait [Idle] -> authorize [Sync] module=m
ender
ERRO[0046] Failure occured while executing authorization request: &url.Error{Op:
“Post”, URL:“https://mender.triamp.com/api/devices/v1/authentication/auth_reques
ts”, Err:(*net.OpError)(0x11e5fb60)} module=client_auth
ERRO[0046] authorization request error: dial tcp 61.216.xxx.xx:443: getsockopt:
connection refused module=client_auth
ERRO[0046] authorize failed: transient error: authorization request failed: gene
ric error occured while executing authorization request: Post https://mender.tri
amp.com/api/devices/v1/authentication/auth_requests: dial tcp 61.216.xxx.xx:443:
getsockopt: connection refused module=state
INFO[0046] State transition: authorize [Sync] -> authorize-wait [Idle] module=m
ender
^C
It appears that there is no server listening on port 443 of mender.triam.com: dial tcp 61.216.xxx.xx:443: getsockopt: connection refused.
Drew
YES,I have.
Dell Green via Mender Hub <mender@discoursemail.com> 於 2020年10月22日 週四 下午6:30寫道：
Hi dellgreen,
- Our linux embedded device pending takes 15 minutes to respond successfully.
- A Device deployments ota takes 15 minutes to respond successfully (release .mender file capacity 33.78MB)
Why does the production mender server take too long to deal with the above two problems? - How can the production mender server join the firewall to block hackers?
We are very urgent to deal with it, please reply me as soon as possible
Best regards,
MEI LI LU <triampmeili@gmail.com> 於 2020年11月10日 週二 上午9:18寫道：
The time of deployment can vary for a couple of reasons.
First, the Mender client polls the server using a set of defined polling intervals. There is no coordination among the devices so that they can start any time but if a deployment is triggered right after a poll, then you may have to wait the entire polling interval before the client starts downloading. The Mender demo configuration reduces those polling intervals to about 5s but the defaults are much higher. In general you probably don’t need the polling intervals to be very low but your particular requirements will dictate the appropriate amount.
Second, the deployments can take some time to install. Depending on the hardware this can go slower or faster. I have some raw-flash based boards where the image write is extremely fast but then Raspberry Pi boards, using SDCards, tend to be fairly slow.
How can the production mender server join the firewall to block hackers?
I’m not sure exactly what you mean by that. You do need to manage the security of your server just like any other piece of network infrastructure. The Mender server generally only requires ports 443 and 9000 to be open so you can certainly use a firewall to block any other port accesses.
Drew
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
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_
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
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
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