Mender V2.7 deployment getting error

General Discussions
1

mender server: v2.7 production open-source
Architecture: Debian X86 Ubuntu18.4
mender convert: v2.4.0
mender-connect: latest

I have set up a self-hosted mender server: v2.7 production-grade successfully. I have also created a mender client image using the mender_convert v2.4.0 tool. Here Deployment status is showing “Pending” and the device-side getting below error.

Below log using the command on target device journalctl -f -u mender-client.service as

May 03 05:50:13 alto-VirtualBox mender[25725]: time=“2021-05-03T05:50:13-04:00” level=error msg=“Error receiving scheduled update data: (request_id: ): Invalid response received from server server error message: failed to parse server response: json: cannot unmarshal object into Go struct field .error of type string”
May 03 05:50:13 alto-VirtualBox mender[25725]: time=“2021-05-03T05:50:13-04:00” level=error msg=“Update check failed: transient error: (request_id: ): Invalid response received from server server error message: failed to parse server response: json: cannot unmarshal object into Go struct field .error of type string”
May 03 05:50:13 alto-VirtualBox mender[25725]: time=“2021-05-03T05:50:13-04:00” level=info msg=“State transition: update-check [Sync] → error [Error]”
May 03 05:50:13 alto-VirtualBox mender[25725]: time=“2021-05-03T05:50:13-04:00” level=info msg=“Handling error state, current error: transient error: (request_id: ): Invalid response received from server server error message: failed to parse server response: json: cannot unmarshal object into Go struct field .error of type string”

image
image1280×681 152 KB

can anyone assist me to resolve this error?

2

what logs are you getting on the server?

3

@oleorhagen
sudo ./run logs --tail 10 mender-deployments

Getting error as below

image
image1287×484 156 KB

4

@oleorhagen

Attached prod.yml for reference.
prod.yaml (5.4 KB)

Note: I have replaced ec2-XX-XXX-XXX-XXX with actual DNS.
if anything wrong in the prod.yml file . Please let me know how can go off this error.

5

hi, I’m not sure which artifact storage you’re using
the URI - ec2-XX-XXX-XXX-XXX.compute-1.amazonaws.com may suggest you’re using actual amazon AWS, but you have minio in your setup too;
if you’re using amazon AWS for storing artifacts try to remove networks part of the mender-api-gateway section;
the result should be like this
prod.yaml (4.9 KB)