[ZBX-23702] Failed writing received data to disk/application - Web scenario problem Created: 2023 Nov 13 Updated: 2024 Jul 28 |
|
| Status: | Confirmed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 6.0.23 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Bartosz Mickiewicz (Inactive) | Assignee: | Zabbix Development Team |
| Resolution: | Unresolved | Votes: | 5 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
ZBX-23702-web-scenario-7.0.diff
image-1 (2).png
image.png
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Steps to reproduce:
1350650:20231113:165231.852 cannot process step "just test the page" of web scenario "custom scenario" on host "test": Failed writing received data to disk/application |
| Comments |
| Comment by Bartosz Mickiewicz (Inactive) [ 2023 Nov 13 ] |
|
Confirmed. |
| Comment by Vladislavs Sokurenko [ 2023 Nov 17 ] |
|
Please see https://github.com/curl/curl/pull/12340 |
| Comment by brendon [ 2024 May 25 ] |
|
I'm getting this on some sites on server 6.4.15. Is there a workaround? |
| Comment by Vladislavs Sokurenko [ 2024 May 27 ] |
|
For more information about workarounds please see https://github.com/curl/curl/pull/12340 it should be possible to workaround the issue by disabling compression by overriding headers Accept-Encoding: deflate, gzip, br, zstd To: Accept-Encoding: identity |
| Comment by Christos Papageorgiou [ 2024 Jun 11 ] |
|
This seems to cause a problem with Slack notifications. I'm using Zabbix 6.4.15 and I'm seeing this error:
Slack notification failed : Error: cannot get URL: Failed writing received data to disk/application. |
| Comment by Frank [ 2024 Jun 11 ] |
|
This is not limited to the web scenarios as we are seeing the same in the Javascript HTTP client as well. Our discoveries were no longer working until we added the Accept-Encoding: identity header to the request.. |
| Comment by Frank [ 2024 Jun 12 ] |
|
Are you using the Alpine version by any chance? While investigating a similar problem (ZBX-24639) I noticed that there was a different behavior when using the Ubuntu container instead. |
| Comment by Steven Foong [ 2024 Jun 14 ] |
|
I am using zabbix/zabbix-server-mysql:alpine-6.4-latest docker image. I have the same issue. Once I change the Agent to something (as long as not Zabbix) in web scenario, then this error will occur . If I add Accept-Encoding: identity to header , clear the history and trends, then the issue will gone. Or else I change the Agent back to Zabbix , clear the history and trends, then the issue will gone. |
| Comment by Frank [ 2024 Jun 19 ] |
|
Be advised: This now also affects the Alpine container for 6.4.16! The 6.4.15 Alpine container didn't have this problem. In 6.4.16 the Alpine base image updated from 3.19 to 3.20 (which is also being used by the 7.0.0 image). I have reported this on GitHub: https://github.com/zabbix/zabbix-docker/issues/1437 as I am not sure the maintainer of it checks issues here. |
| Comment by Manuel Frei [ 2024 Jun 21 ] |
|
I had the same error message for my Pushover action. They failed and sent every notification three times. I didn't want to downgrade and as a quick & dirty solution I installed the libcurl version from the Alpine edge repository in the container. I hope they will publish a new revision for the Alpine 3.20 repository soon. The process is documented here. |
| Comment by Vladislavs Sokurenko [ 2024 Jul 09 ] |
|
We can add a workaround by logging with debug level and ignoring this exact error if there is data, attached patch with example: ZBX-23702-web-scenario-7.0.diff |
