We are hoping to get a production setup running that will allow us to ensure our raspberrypi4 devices can connect to our server and do some simple protoype testing. I was able to get the demo version working but not the production one.
We are intending to use Mender on its own (no kubernetes, no yocto) so I installed the mender server 3.7.7 on my desktop machine using the installation instructions from the v2.7 docs and was able to get it up and running at http://192.168.2.114. However, after installing the client on the raspberrypi4 from the apt repository (deb bookworm on raspian os) and configuring the setup parameters, I’m unable to get the device to connect. I’ve also tried installing the client from source and using the express-install method as well.
Did the mender-setup as follows:
Enter a name for the device type (e.g. raspberrypi3): [raspberrypi4]
Are you connecting this device to hosted.mender.io? [Y/n] n
Demo server uses a self-signed certifcate for “docker.mender.io” and modifies device’s /etc/hosts with the server’s IP address (Required if using Mender demo server.)
Do you want to configure the client for a demo server? [Y/n] nSet the URL of the Mender Server: [https://docker.mender.io] http://192.168.2.114
Set the location of the certificate of the server; leave blank if using http (not recommended) or a certificate from a known authority (filepath, for example /etc/mender/server.crt):
Demo intervals uses short poll and retry intervals (Recommended for testing.)
Do you want to run the client in demo mode? [Y/n] y
Mender setup successfully.
I attempted to look into the logs but journalctl -u mender-client returns: “-- No entries --”.
I also tried to view the current status with journalctl -u mender-client -f but it just hangs and returns nothing.
systemctl status mender-client returns: “Unit mender-client.service could not be found.”
How can I troubleshoot this issue?
EDIT: I was able to see the output of mender-connect service:
Oct 28 17:40:31 raspberrypi systemd[1]: Started mender-connect.service - Mender Connect service.
Oct 28 17:40:31 raspberrypi mender-connect[6944]: time=“2024-10-28T17:40:31Z” level=info msg=“Loaded configuration file: /etc/mender/mender-connect.conf”
Oct 28 17:40:31 raspberrypi mender-connect[6944]: time=“2024-10-28T17:40:31Z” level=warning msg=“ShellArguments is empty, defaulting to [–login]”
Oct 28 17:40:31 raspberrypi mender-connect[6944]: time=“2024-10-28T17:40:31Z” level=warning msg="call to GetJWTToken on the Mender D-Bus API failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name io.mender.AuthenticationManager was not provided by any .service f
and here is the output of mender-updated:
Oct 28 19:35:46 raspberrypi mender-update[7785]: record_id=5 severity=error time=“2024-Oct-28 19:35:46.396187” name=“Global” msg=“Failed to submit inventory: Unauthorized error: Cannot submit API request”
Oct 28 19:35:46 raspberrypi mender-update[7785]: record_id=6 severity=error time=“2024-Oct-28 19:35:46.666987” name=“Global” msg=“Failed to set new authentication data on HTTP request”
Oct 28 19:35:46 raspberrypi mender-update[7785]: record_id=7 severity=error time=“2024-Oct-28 19:35:46.667108” name=“Global” msg=“Request to check new deployments failed: Cannot submit API request”