# Failed to report status: EOF **URL:** \ **Category:** General Discussions\ **Created:** [September 13, 2021, 4:53pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074 "2021-09-13T16:53:31Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 13, 2021, 4:53pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/1 "2021-09-13T16:53:31Z")
Hello! A collegue of mine is suffering from a problem. His device reproducably rolls back deployments when it receives them in his home. Deployment seems to work fine first, but when booting into the new artifact, it cannot report status to the server. Here’s the error message: ```auto Failed to report status: Put "https://hosted.mender.io/api/devices/v1/deployments/device/deployments/0bf971b7-58fc-4457-b413-45342e1617dd/status": EOF ``` I would like to verify what this error message means _exactly_. I read it as: - Network connection is up - Device could set up a TLS connection to [hosted.mender.io](http://hosted.mender.io) - Device sends an HTTP PUT, but instead of a response it receives only EOF. But I don’t thank that to be true. It would mean something specifically eats the http data inside a TLS connection. That’s hard to believe, given that nothing should be able to peek inside the TLS stream. Given that error message, can I even trust that network was operational when that https PUT was sent? Thanks, Manuel ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 13, 2021, 4:55pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/2 "2021-09-13T16:55:39Z")
After the rollback, these two errors are printed into the log: ```auto error: Got unexpected HTTP status when reporting status: 500 error: statescript: Can not send start status to server: (request_id: ): reporting status failed, bad status 500 server error message: failed to parse server response: json: cannot unmarshal object into Go struct field .error of type string ``` ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 14, 2021, 3:45pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/3 "2021-09-14T15:45:17Z")
The problem just occured again, and this time I observed something rather interesting: The deployment already showed up as “successful” at the mender web gui. So I thought that we couldn’t reproduce the problem anymore. My collegue insisted to reboot his device, and indeed, it did a rollback then. When switching to the mender web gui browser tab again, the deployment jumped from “successful” to “failed”. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [September 16, 2021, 5:46am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/4 "2021-09-16T05:46:44Z")
Sounds like the server received the status update, but the device is unable to understand that. Which version of Mender client is it? And is this Hosted Mender, or self-hosted? It could be useful to check the server logs of the api-gateway and deployments services. ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 16, 2021, 7:54am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/5 "2021-09-16T07:54:16Z")
Hi kacf! We are using hosted Mender with mender client 2.5.0. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [September 16, 2021, 9:23am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/6 "2021-09-16T09:23:26Z")
I wonder if this could be related to [this fix](https://github.com/mendersoftware/mender/commit/608dc31141a334dd2f7c237b0f5478c7b53abb46). It was fixed quite recently, and has not been included in any release yet. Mender client 3.1.0 is right around the corner though, so you could try that, or if you have the chance to patch the client by yourself, you could also try the patch I linked to above. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [September 16, 2021, 9:25am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/7 "2021-09-16T09:25:40Z")
Oh wait, my mistake, it _is_ included in [Mender client 2.5.2](https://docs.mender.io/release-information/release-notes-changelog/mender-client#mender-2-5-2-1)! So I encourage you to try that! ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 17, 2021, 9:43am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/8 "2021-09-17T09:43:45Z")
We upgraded the mender client to 2.5.2 (which reports as 2.6.0) and still observe these EOF errors, but in contrast to 2.5.0 they don’t seem to cause a rollback anymore. Still, I’d like to find out what causes them, as this might cause other problems in the long run. Can you provide some background info on the EOF error? Does it mean the http request received an empty reply? Or was the reply just not parsable by mender? The collegue suffering from that problem is living at some rentable fully-furnished temporary home with a nonstandard internet connection. Don’t yet have complete information, but it seems to be some hotel-style internet connection. I can’t help myself but think there’s causality rather than correlation at play here. ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [September 20, 2021, 8:40am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/9 "2021-09-20T08:40:51Z")
Hello @manuel_vps , we can inspect the Hosted Mender logs for your device and see the full error message. Are you able to reproduce the issue on demand, if needed? If yes, can we agree on a date and time, so we can enable extended logging for your device/tenant? ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 21, 2021, 7:54am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/10 "2021-09-21T07:54:01Z")
Hello @tranchitella, we are able to reproduce it with high probability. Every know and then the problem doesn’t show, but usually it does. The collegue suffering from that problem is currently on a business trip and will be back next week. I’m sure we’ll find a date and time suitable for all of us. I’ll contact him and give notice when I know more. ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [September 21, 2021, 8:00am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/11 "2021-09-21T08:00:32Z")
Thanks @manuel_vps, just ping me here when your colleague is back. ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 27, 2021, 1:06pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/12 "2021-09-27T13:06:16Z")
Hi @tranchitella, could you activate extended logging starting from Wednesday, Sept. 29th 07:00 CEST? Our organization name as per mender web-ui settings page is `viewpointsystem GmbH`; the device id is `2e2dd41d-f194-40c1-8058-cf2b4b8aa8c2`. Thanks! ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [September 28, 2021, 7:08am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/13 "2021-09-28T07:08:51Z")
@manuel_vps yes, sure ---
**Author:** ![manuel\_vps](https://avatars.discourse-cdn.com/v4/letter/m/a87d85/32.png) [@manuel\_vps](https://hub.mender.io/u/manuel_vps)\ **Post date:** [September 29, 2021, 2:58pm UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/14 "2021-09-29T14:58:33Z")
Hello @tranchitella, just writing to inform you our tests are finished for today. We made quite a few deployments but unfortunately couldn’t reproduce the issue. (As the tests are finished, could you remove the company name from my [previous post](https://hub.mender.io/t/failed-to-report-status-eof/4074/12)? Can’t do it myself. Thanks.) Still, would like to take this opportunity to ask if the mender client fiddles with the networking stack right after flashing the new artifact onto the inactive partition. One of our tests showed “Failed to report status” errors immediately after concluding the writing. That network connection failure might be totally independent from mender, but that it fails just a few sec after the “Wrote 5166018560/5166018560 bytes to the inactive partition” got me thinking. Attaching the error log for reference. Note: The mender version gets reported as `-dirty` as we have some patches in place which prevent the client from checking for an update immediately after starting up. Thank you; regards Manuel ```auto {"level":"info","message":"Running Mender client version: 2.5.0-dirty","timestamp":"2021-09-29T12:26:58+02:00"} {"level":"info","message":"State transition: update-fetch [Download_Enter] -\u003e update-store [Download_Enter]","timestamp":"2021-09-29T12:26:59+02:00"} {"level":"info","message":"Installer: authenticated digital signature of artifact","timestamp":"2021-09-29T12:26:59+02:00"} {"level":"info","message":"Opening device \"/dev/mmcblk0p1\" for writing","timestamp":"2021-09-29T12:26:59+02:00"} {"level":"info","message":"Native sector size of block device /dev/mmcblk0p1 is 512 bytes. Mender will write in chunks of 1048576 bytes","timestamp":"2021-09-29T12:26:59+02:00"} {"level":"info","message":"All bytes were successfully written to the new partition","timestamp":"2021-09-29T12:46:13+02:00"} {"level":"info","message":"The optimized block-device writer wrote a total of 4927 frames, where 47 frames did need to be rewritten (i.e., skipped)","timestamp":"2021-09-29T12:46:13+02:00"} {"level":"info","message":"Wrote 5166018560/5166018560 bytes to the inactive partition","timestamp":"2021-09-29T12:46:14+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51943-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:24+02:00"} {"level":"error","message":"error reporting update status: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51943-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:24+02:00"} {"level":"info","message":"State transition: update-store [Download_Enter] -\u003e update-after-store [Download_Leave]","timestamp":"2021-09-29T12:46:24+02:00"} {"level":"info","message":"State transition: update-after-store [Download_Leave] -\u003e update-install [ArtifactInstall]","timestamp":"2021-09-29T12:46:24+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:33497-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:34+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:33497-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:34+02:00"} {"level":"info","message":"Collected output (stderr) while running script /etc/mender/scripts/Download_Leave_10_sendState\nSend state via dbus 'DownloadLeave'\n\n---------- end of script output","timestamp":"2021-09-29T12:46:34+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:36056-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:44+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:36056-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:44+02:00"} {"level":"info","message":"Collected output (stderr) while running script /etc/mender/scripts/Download_Leave_20_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 14, suffix: _a, retry_count: 7, boot_successful: 1\nslot: 1, priority: 15, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:1\nmender_boot_part=33\n\n---------- end of script output","timestamp":"2021-09-29T12:46:45+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:49052-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:55+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:49052-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:46:55+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51130-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:05+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51130-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:05+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:54665-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:15+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:54665-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:15+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Enter_10_sendState\nSend state via dbus 'ArtifactInstallEnter'\n\n---------- end of script output","timestamp":"2021-09-29T12:47:15+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48557-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:25+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48557-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:25+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Enter_20_printStaticInfo\ncat /var/lib/mender/mender.conf:\n{\n \"RootfsPartA\": \"/dev/mmcblk0p1\",\n \"RootfsPartB\": \"/dev/mmcblk0p33\"\n}\nfindmnt /:\nTARGET SOURCE FSTYPE OPTIONS\n/ /dev/mmcblk0p33 ext4 rw,relatime,data=ordered\n\n---------- end of script output","timestamp":"2021-09-29T12:47:25+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:50849-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:35+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:50849-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:35+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Enter_30_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 14, suffix: _a, retry_count: 7, boot_successful: 1\nslot: 1, priority: 15, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:1\nmender_boot_part=33\n\n---------- end of script output","timestamp":"2021-09-29T12:47:35+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:37164-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:45+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:37164-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:45+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:60455-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:55+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:60455-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:47:55+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:47498-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:05+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:47498-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:05+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48450-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:15+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48450-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:15+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:53123-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:25+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:53123-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:25+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:54134-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:35+02:00"} {"level":"error","message":"error reporting update status: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:54134-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:35+02:00"} {"level":"info","message":"Enabling partition with new image installed to be a boot candidate: 1","timestamp":"2021-09-29T12:48:35+02:00"} {"level":"info","message":"State transition: update-install [ArtifactInstall] -\u003e reboot [ArtifactReboot_Enter]","timestamp":"2021-09-29T12:48:35+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:35585-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:45+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:35585-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:45+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Leave_10_sendState\nSend state via dbus 'ArtifactInstallLeave'\n\n---------- end of script output","timestamp":"2021-09-29T12:48:45+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:46843-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:55+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:46843-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:48:55+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Leave_70_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 14, suffix: _a, retry_count: 7, boot_successful: 1\nslot: 1, priority: 15, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:1\nmender_boot_part=1\n\n---------- end of script output","timestamp":"2021-09-29T12:48:56+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:40227-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:06+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:40227-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:06+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Leave_80_bl-update\n+ mnt=\n+ echo 'Installing NVIDIA bootloader update payload'\n++ nvbootctrl get-number-slots\n+ num_slots=2\n+ '[' 2 '!=' 2 ']'\n++ nvbootctrl get-current-slot\n+ current_slot=1\n+ echo 'Current boot slot: 1'\n++ fw_printenv -n mender_boot_part\n+ new_boot_part=1\n++ mktemp -d -t nvbup.XXXXXX\n+ mnt=/tmp/nvbup.cgn5GB\n+ '[' -z /tmp/nvbup.cgn5GB -o '!' -d /tmp/nvbup.cgn5GB ']'\n+ mount /dev/mmcblk0p1 /tmp/nvbup.cgn5GB\n+ '[' '!' -d /tmp/nvbup.cgn5GB/opt/ota_package ']'\n+ mount --bind /sys /tmp/nvbup.cgn5GB/sys\n+ mount --bind /proc /tmp/nvbup.cgn5GB/proc\n+ mount --bind /dev /tmp/nvbup.cgn5GB/dev\n+ '[' -L /tmp/nvbup.cgn5GB/etc/nv_boot_control.conf -a -x /tmp/nvbup.cgn5GB/usr/bin/setup-nv-boot-control ']'\n+ rm /tmp/nvbup.cgn5GB/etc/nv_boot_control.conf\n+ chroot /tmp/nvbup.cgn5GB /usr/bin/setup-nv-boot-control\n+ chroot /tmp/nvbup.cgn5GB /usr/sbin/nv_update_engine --install no-reboot\n+ echo 'Successful bootloader update'\n+ cleanup\n+ '[' -n /tmp/nvbup.cgn5GB ']'\n+ for d in sys proc dev\n+ mountpoint -q /tmp/nvbup.cgn5GB/sys\n+ umount /tmp/nvbup.cgn5GB/sys\n+ for d in sys proc dev\n+ mountpoint -q /tmp/nvbup.cgn5GB/proc\n+ umount /tmp/nvbup.cgn5GB/proc\n+ for d in sys proc dev\n+ mountpoint -q /tmp/nvbup.cgn5GB/dev\n+ umount /tmp/nvbup.cgn5GB/dev\n+ mountpoint -q /tmp/nvbup.cgn5GB\n+ umount /tmp/nvbup.cgn5GB\n+ rmdir /tmp/nvbup.cgn5GB\n+ exit 0\n\n---------- end of script output","timestamp":"2021-09-29T12:49:07+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:56458-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:17+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:56458-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:17+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactInstall_Leave_90_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 0\nslot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:1\nmender_boot_part=1\n\n---------- end of script output","timestamp":"2021-09-29T12:49:17+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:56604-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:27+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:56604-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:27+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:33958-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:37+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:33958-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:37+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:49145-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:47+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:49145-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:47+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48819-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:57+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:48819-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:49:57+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:39130-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:07+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:39130-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:07+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactReboot_Enter_10_sendState\nSend state via dbus 'ArtifactRebootEnter'\n\n---------- end of script output","timestamp":"2021-09-29T12:50:07+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:42755-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:17+02:00"} {"level":"error","message":"statescript: Can not send start status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:42755-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:17+02:00"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactReboot_Enter_20_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 0\nslot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:1\nmender_boot_part=1\n\n---------- end of script output","timestamp":"2021-09-29T12:50:17+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51313-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:27+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:51313-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:27+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:59374-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:37+02:00"} {"level":"error","message":"statescript: Can not send finished status to server: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:59374-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:37+02:00"} {"level":"error","message":"Failed to report status: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:43286-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:47+02:00"} {"level":"error","message":"error reporting update status: reporting status failed: Put \"https://hosted.mender.io/api/devices/v1/deployments/device/deployments/f1f06ae7-8dea-4205-bcf0-83835fe3c0f3/status\": dial tcp: lookup hosted.mender.io on 192.168.0.1:53: read udp 192.168.0.104:43286-\u003e192.168.0.1:53: i/o timeout","timestamp":"2021-09-29T12:50:47+02:00"} {"level":"info","message":"Rebooting device(s)","timestamp":"2021-09-29T12:50:47+02:00"} {"level":"info","message":"Mender rebooting from active partition: /dev/mmcblk0p33","timestamp":"2021-09-29T12:50:47+02:00"} {"level":"info","message":"Daemon terminated with SIGTERM","timestamp":"2021-09-29T12:50:50+02:00"} {"level":"info","message":"Running Mender client version: 2.5.0-dirty","timestamp":"2021-09-29T10:51:57Z"} {"level":"info","message":"State transition: init [none] -\u003e after-reboot [ArtifactReboot_Leave]","timestamp":"2021-09-29T10:51:57Z"} {"level":"info","message":"State transition: after-reboot [ArtifactReboot_Leave] -\u003e after-reboot [ArtifactReboot_Leave]","timestamp":"2021-09-29T10:51:57Z"} {"level":"info","message":"State transition: after-reboot [ArtifactReboot_Leave] -\u003e update-commit [ArtifactCommit_Enter]","timestamp":"2021-09-29T10:51:57Z"} ... removed for brevity ... {"level":"info","message":"State transition: update-commit [ArtifactCommit_Enter] -\u003e update-pre-commit-status-report-retry [ArtifactCommit_Enter]","timestamp":"2021-09-29T10:51:58Z"} {"level":"info","message":"State transition: update-pre-commit-status-report-retry [ArtifactCommit_Enter] -\u003e update-commit [ArtifactCommit_Enter]","timestamp":"2021-09-29T11:01:58Z"} {"level":"info","message":"Committing update","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"State transition: update-commit [ArtifactCommit_Enter] -\u003e update-after-first-commit [none]","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"State transition: update-after-first-commit [none] -\u003e update-after-commit [ArtifactCommit_Leave]","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"State transition: update-after-commit [ArtifactCommit_Leave] -\u003e cleanup [none]","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactCommit_Leave_10_sendState\nSend state via dbus 'ArtifactCommitLeave'\n\n---------- end of script output","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"Collected output (stderr) while running script /var/lib/mender/scripts/ArtifactCommit_Leave_20_printVolatileInfo\nnvbootctrl dump-slots-info:\nmagic:0x43424e00, version: 3 features: 3 num_slots: 2\nslot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 1\nslot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1\nnvbootctrl get-current-slot:0\nmender_boot_part=1\n\n---------- end of script output","timestamp":"2021-09-29T11:01:59Z"} {"level":"info","message":"State transition: cleanup [none] -\u003e update-status-report [none]","timestamp":"2021-09-29T11:02:00Z"} ``` ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [September 30, 2021, 7:28am UTC](https://hub.mender.io/t/failed-to-report-status-eof/4074/15 "2021-09-30T07:28:53Z")
> [@manuel\_vps](#): > > Still, would like to take this opportunity to ask if the mender client fiddles with the networking stack right after flashing the new artifact onto the inactive partition. One of our tests showed “Failed to report status” errors immediately after concluding the writing. That network connection failure might be totally independent from mender, but that it fails just a few sec after the “Wrote 5166018560/5166018560 bytes to the inactive partition” got me thinking. The Mender client makes no changes to the network anywhere in its code. The point where it happens makes me think though: Do you have any `Download` type state scripts which enable/disable network access? It’s [a fairly common pattern](https://docs.mender.io/development/artifact-creation/state-scripts#enable-network-connectivity).