All work
- [API gateway] device update logs are stored in temporary filesMEN-1291eystein.maloy.stenberg
- api-gateway: nginx will cache resolved DNS addressesMEN-1227Resolved issue: MEN-1227Marcin Chalczynski
- Mender should read back what it was written to the update storage area to verify it hasn't been corruptedMEN-1216Resolved issue: MEN-1216
- mender client doesn't exit with error if device_type file is not foundMEN-1215Resolved issue: MEN-1215Ole Petter Orhagen
- deployments: verbose logging of s3/minio errorsMEN-1165Resolved issue: MEN-1165Maciej Borzecki
- Failure to process ServerCertificate in mender.conf if no trust roots are present on the systemMEN-1151Resolved issue: MEN-1151Ole Petter Orhagen
- Document upgrade processMEN-1112Resolved issue: MEN-1112Maciej Borzecki
7 of 7
[API gateway] device update logs are stored in temporary files
Details
Assignee
eystein.maloy.stenbergeystein.maloy.stenbergReporter
Maciej BorzeckiMaciej BorzeckiLabels
Priority
MediumBacklog
no
Details
Details
Assignee
eystein.maloy.stenberg
eystein.maloy.stenbergReporter
Maciej Borzecki
Maciej BorzeckiLabels
Priority
Backlog
no
Zendesk Support
Zendesk Support
Zendesk Support
Checklist
Checklist
Checklist
Created June 21, 2017 at 6:00 AM
Updated July 14, 2017 at 11:51 AM
Activity
Show:
eystein.maloy.stenbergJuly 14, 2017 at 11:51 AM
OK, let me know what you decide & estimate for prioritization.
MaciejJune 21, 2017 at 9:44 AM
Shouldn't Nginx handle cleaning this for itself ?
When an update fails, the device will upload its logs using PUT. nginx is apparently saving the upload to a temporary location.
mender-api-gateway_1 | 2017/06/20 19:20:40 [warn] 9#9: *103 a client request body is buffered to a temporary file /usr/local/openresty/nginx/client_body_temp/0000000001 while sending to client, client: 172.20.0.10, server: localhost, request: "PUT /api/devices/v1/deployments/device/deployments/d9ba6bdf-60a8-4ac3-aa0f-647e9f618f40/log HTTP/2.0", host: "docker.mender.io"
TBD whether this is ok or not