Device is not recognized by the demo server

Tutorials Mender
,
1

Hi,

I am running a demo server but my device is not recognized by the server. Please help.

mender client version,
/usr/bin/mender -version
2.1.2-dirty

mender server version,
mendersoftware/deviceauth:mender-3.7.2
mendersoftware/deployments:mender-3.7.2

I am running mender using docker compose file from integration-3.7.2.

Thank you

2

Hi @jni,

The version sounds a bit strange: 2.1.2 is very outdated by now. So the first thing to do would be moving to a currently supported release.
Beyond that:

  • if using Yocto, have you added the meta-mender/meta-mender-demo layer for the demo server certificate?
  • how have you set the client up? Did you use the mender setup command, or the token?
  • what is in the client log?

Greets,
Josef

3

Hi Josef,

Thanks for your reply. the devices are released and cannot be upgraded immediately. so, i have a constraint to work with this client version.

  1. yes, its a yocto image. i did not change the device image. but i have updated the mender server config and the cert directly on the device.
  2. i modified the server ip to local address here,
    /etc/mender/mender.conf
    and copied my local server certificate here,
    /etc/mender/server.crt.

– Logs begin at Wed 2024-03-13 17:25:15 UTC, end at Tue 2024-03-19 14:21:02 UTC. –
Mar 19 14:08:16 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:16Z” level=debug msg=“handle check wait state” module=state
Mar 19 14:08:16 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:16Z” level=debug msg=“check wait state; next checks: (update: 2024-03-19 14:11:02.4712
26193 +0000 UTC m=+32236.875749275) (inventory: 2024-03-19 14:08:47.157590593 +0000 UTC m=+32101.562053840)” module=state
Mar 19 14:08:16 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:16Z” level=debug msg=“next check: 2024-03-19 14:08:47.157590593 +0000 UTC m=+32101.562
053840:inventory-update, (2024-03-19 14:08:16.95306424 +0000 UTC m=+32071.357527863)” module=state
Mar 19 14:08:16 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:16Z” level=debug msg=“waiting 30.204525977s for the next state” module=state
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=debug msg=“wait complete” module=state
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=info msg=“State transition: check-wait [Idle] → inventory-update [Sync]” m
odule=mender
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=debug msg=“statescript: timeout for executing scripts is not defined; using
default of 1h0m0s seconds” module=executor
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=debug msg=“Returning artifact name 7.1.0a from database.” module=device
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=debug msg=“Read data from device manifest file: device_type=unicorn” module
=device
Mar 19 14:08:47 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:08:47Z” level=debug msg=“Current manifest data: unicorn” module=device
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=error msg=“failed to submit inventory data: Patch https://100.76.41.75/api/
devices/v1/inventory/device/attributes: dial tcp 100.76.41.75:443: getsockopt: connection timed out” module=client_inventory
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=warning msg=“failed to refresh inventory: failed to submit inventory data:
inventory submit failed: Patch https://100.76.41.75/api/devices/v1/inventory/device/attributes: dial tcp 100.76.41.75:443: getsockopt: connection timed out”
module=state
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=info msg=“State transition: inventory-update [Sync] → check-wait [Idle]” m
odule=mender
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“statescript: timeout for executing scripts is not defined; using
default of 1h0m0s seconds” module=executor
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“statescript: timeout for executing scripts is not defined; using
default of 1h0m0s seconds” module=executor
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“handle check wait state” module=state
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“check wait state; next checks: (update: 2024-03-19 14:11:02.4712
26193 +0000 UTC m=+32236.875749275) (inventory: 2024-03-19 14:13:47.157590593 +0000 UTC m=+32401.562053840)” module=state
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“next check: 2024-03-19 14:11:02.471226193 +0000 UTC m=+32236.875
749275:update-check, (2024-03-19 14:11:00.713004662 +0000 UTC m=+32235.117473159)” module=state
Mar 19 14:11:00 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:00Z” level=debug msg=“waiting 1.758276116s for the next state” module=state
Mar 19 14:11:02 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:02Z” level=debug msg=“wait complete” module=state
Mar 19 14:11:02 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:02Z” level=info msg=“State transition: check-wait [Idle] → update-check [Sync]” modul
e=mender
Mar 19 14:11:02 flo-6c302a277cc3 mender[19669]: time=“2024-03-19T14:11:02Z” level=debug msg=“statescript: timeout for executing scripts is not defined; using
default of 1h0m0s seconds” module=executor

Thank you very much

4

Hi @jni,

This log suggests that the server at IP 100.76.41.75 is not reachable from the device. Have you checked the connectivity, like pinging it?

Greetz,
Josef

5

Hi @TheYoctoJester ,

Thanks for your reply. the connection issue did fix my problem.

Thank you

1 Like