Hi @lluiscampos,
That worked! I have now restored all the files I need on my physical Ubuntu 22 Server. After that I was able to successfully register with hosted.mender.io
and deploy an artifact! This is the farthest I have made it so far.
I am now back to where I started with my device, and trying to deploy the update with my own Mender cluster on EKS.
To switch between these two Mender servers I:
- run
sudo mender-setup
and go through the interactive setup and type in my domain: mender.mydomain.com
- run
sudo systemctl restart mender-authd
and sudo systemctl restart mender-updated
Please let me know if this is the right way to switch my device between using Hosted Mender and my own.
I started digging into the Kubernetes logs for both the mender-deployments
pod and the mender-api-gateway
pod (are there any others I should dig through?).
mender-deployments
:
level=info msg="404 82μs POST /api/devices/v2/deployments/device/deployments/next HTTP/1.1 - -" byteswritten=30 caller="accesslog.(*AccessLogMiddleware).MiddlewareFunc.func1@middleware.go:82" device_id=bc7903f6-a1a5-4d0e-aee3-f7206fab4e19 method=POST path=/api/devices/v2/deployments/device/deployments/next plan=enterprise qs= request_id=580a9bcb-ca67-4ccc-bddb-6b451fc69111 responsetime=8.2819e-05 status=404 type=http
level=info msg="204 1449μs GET /api/devices/v1/deployments/device/deployments/next?artifact_name=REDACTED&device_type=REDACTED HTTP/1.1 - -" byteswritten=0 caller="accesslog.(*AccessLogMiddleware).MiddlewareFunc.func1@middleware.go:82" device_id=bc7903f6-a1a5-4d0e-aee3-f7206fab4e19 method=GET path=/api/devices/v1/deployments/device/deployments/next plan=enterprise qs="artifact_name=REDACTED&device_type=REDACTED" request_id=cdb67bca-4882-402c-8ca4-df22729ad94f responsetime=0.001449024 status=204 type=http
mender-api-gateway
:
{"ClientAddr":"10.0.25.204:2430","ClientHost":"10.0.25.204","ClientPort":"2430","ClientUsername":"-","DownstreamContentSize":54,"DownstreamStatus":404,"Duration":80030997,"OriginContentSize":54,"OriginDuration":316254,"OriginStatus":404,"Overhead":79714743,"RequestAddr":"mender.mydomain.com","RequestContentSize":123,"RequestCount":142880,"RequestHost":"mender.mydomain.com","RequestMethod":"POST","RequestPath":"/api/devices/v2/deployments/device/deployments/next","RequestPort":"-","RequestProtocol":"HTTP/1.1","RequestScheme":"http","RetryAttempts":0,"RouterName":"deployments@file","ServiceAddr":"mender-gui:8080","ServiceName":"error-responder@file","ServiceURL":"http://mender-gui:8080","entryPointName":"http","level":"info","msg":""}
{"ClientAddr":"10.0.10.53:47916","ClientHost":"10.0.10.53","ClientPort":"47916","ClientUsername":"-","DownstreamContentSize":0,"DownstreamStatus":204,"Duration":8890821,"OriginContentSize":0,"OriginDuration":1858589,"OriginStatus":204,"Overhead":7032232,"RequestAddr":"mender.mydomain.com","RequestContentSize":0,"RequestCount":142881,"RequestHost":"mender.mydomain.com","RequestMethod":"GET","RequestPath":"/api/devices/v1/deployments/device/deployments/next?artifact_name=test2-file\u0026device_type=ubuntu-server","RequestPort":"-","RequestProtocol":"HTTP/1.1","RequestScheme":"http","RetryAttempts":0,"RouterName":"deployments@file","ServiceAddr":"mender-deployments:8080","ServiceName":"deployments@file","ServiceURL":"http://mender-deployments:8080","entryPointName":"http","level":"info","msg":""}
These messages appear without a deployment even running. My ingress only has one rule pointing to the Mender API gateway. How can I further debug this on the Mender server side?
I greatly appreciate all the help!