I am using mender demo server version integration-2.1.0. I have hosted it on AWS EC2 instance.
Mender demo artifact deployment was working up to last week. But it has stopped working suddenly.
I am getting below error for OTA update:
2020-10-29 10:31:32 +0000 UTC info: Running Mender client version: b6dfc02
2020-10-29 10:31:33 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2020-10-29 10:31:34 +0000 UTC info: No public key was provided for authenticating the artifact
2020-10-29 10:31:41 +0000 UTC info: State transition: update-store [Download_Enter] -> update-after-store [Download_Leave]
2020-10-29 10:31:41 +0000 UTC info: State transition: update-after-store [Download_Leave] -> update-install [ArtifactInstall]
2020-10-29 10:31:41 +0000 UTC info: State transition: update-install [ArtifactInstall] -> update-commit [ArtifactCommit_Enter]
2020-10-29 10:31:45 +0000 UTC info: Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Leave_90_install_systemd_unit
Job for mender-demo-artifact.service failed because the control process exited with error code.
See “systemctl status mender-demo-artifact.service” and “journalctl -xe” for details.
---------- end of script output
2020-10-29 10:31:46 +0000 UTC error: transient error: error executing leave script for update-install state: error running leave state script(s) for ArtifactInstall state: statescript: error executing ‘ArtifactInstall_Leave_90_install_systemd_unit’: 1 : exit status 1
2020-10-29 10:31:46 +0000 UTC info: State transition: update-install [ArtifactInstall] -> rollback [ArtifactRollback]
2020-10-29 10:31:47 +0000 UTC info: Performing rollback
2020-10-29 10:31:47 +0000 UTC info: State transition: rollback [ArtifactRollback] -> update-error [ArtifactFailure]
2020-10-29 10:31:47 +0000 UTC info: State transition: update-error [ArtifactFailure] -> cleanup [Error]
2020-10-29 10:31:47 +0000 UTC info: State transition: cleanup [Error] -> update-status-report [none]
is there something changed in mender server or what is causing it to fail ?
Oct 30 10:12:00 alto-VirtualBox systemd: Starting mender-demo-artifact.service…
Oct 30 10:12:03 alto-VirtualBox entrypoint.sh: /usr/share/mender/inventory/mender-inventory-geo: Unable to get the geolocalization data from ipvigilante.com
Oct 30 10:12:03 alto-VirtualBox systemd: mender-demo-artifact.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 30 10:12:03 alto-VirtualBox systemd: mender-demo-artifact.service: Failed with result ‘exit-code’.
Oct 30 10:12:03 alto-VirtualBox systemd: Failed to start mender-demo-artifact.service.
This was working until few days back but suddenly stopped working
It seems that for some reason this systemctl restart is not working. I don’t know why but since you have “set -e” in your script, that will force the script to return an error code which is the signal to Mender to roll back. You need to either ignore the errors and explicitly return 0 or troubleshoot the failure to start the mender-demo-artifact script.
Using the Mender demo server requires these names but it also requires them to exist in /etc/hosts since you have to explicitly assign an IP address. For some reason your name resolution is not working. What are the contents of /etc/hosts and /etc/resolv.conf? What happens if you run ping 220.127.116.11?
Question: where (s3 bucket) OTA uploaded mender artifacts (xyz**.menter files**) stores in mender demo server integration-2.0 hosted on my EC2 install??
Actually, I want to stores .mender artifacts on my own aws account S3 bucket that was uploaded on the mender demo server. is it possible it using mender demo server?? if yes what changes suppose to make?
I’d suggest you move to a production server before setting up S3. That will ensure you are not using a shared certificate and the like that are part of the demo setup. It will also allow you to use your own domain name for the server rather than using the demo names and hacking it with the /etc/hosts file modifications.
I had tried to replace DEPLOYMENTS_AWS_AUTH_KEY as my AWS & DEPLOYMENTS_AWS_AUTH_SECRET with my aws access key & secret key. and also DEPLOYMENTS_AWS_URI as https://s3-us-west-1.amazonaws.com. Now after that, i am unable to upload mender artifacts. can you plz assist me that what wrong i make ??
I had also tried to update /home/ubuntu/mender-server/docker-compose.storage.s3.yml parameters below
docker-compose.storage.s3.yml file data is as below
# S3 access configuration - override with your own values
# Keys have to grant access to default bucket: mender-artifact-storage
I am able to upload artifacts on console but I didn’t get it in s3 bucket “mender-public-bucket”. currenlly i have made this s3 bucket “mender-public-bucket” as public. should bucket public?
what should be DEPLOYMENTS_AWS_URI value? is it right in my above .yml file?
thanks for using Mender. https://s3.amazonaws.com should work, and the bucket most certainly does not/should not be public, thats why you need AUTH_KEY and AUTH_SECRET settings.
do you have some logs from the deployments service and from the mender-client, so we can see what is the problem?