question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

/dump fails with "WriteDumpAsync failed - HRESULT: 0x00000000"

See original GitHub issue

Description

When attempting to take a full dump by navigating to /dump endpoint (with defaults) the following error message is returned:

{"status":400,"detail":"WriteDumpAsync failed - HRESULT: 0x00000000"}

Only mention I see of this error is in #1216 but I’ve verified folder exists and is writable:

# on sidecar
            - name: DOTNETMONITOR_Storage__DumpTempFolder
              value: /dumps
# on both sidecar and app
            - mountPath: /dumps
              name: dumpsvol

Configuration

Pod with process running RHEL UBI8 (registry.access.redhat.com/ubi8/dotnet-60-runtime:6.0-5)

Dotnet --info
  Version: 6.0.2
  Commit:  839cdfb0ec

Sidecar (ms provided container) /info:

{"version":"6.1.1+17a566bc3228b2ea2a9bfa6d75423637c340943a","runtimeVersion":"6.0.4","diagnosticPortMode":"Connect","diagnosticPortName":null}

Configured with defaults other than “–no-auth” arg and DOTNETMONITOR_Urls and DOTNETMONITOR_Storage__DumpTempFolder env vars set.

Other information

  • /trace & /gcdump work without issue.
  • I’ve tried adding SYS_PTRACE capability to both and shareProcessNamespace as well since I saw those mentioned occasionally but same error occurred. I think those were for older dotnet dump versions anyway.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
hoyosjscommented, Apr 26, 2022
0reactions
plaistedcommented, Apr 26, 2022

I’ll close this, appears related to linked fix (or other photon os specific issue) and not specific to dotnet monitor tooling itself.

Read more comments on GitHub >

github_iconTop Results From Across the Web

WriteDump failed hresult: 0x00000000 - net core
1 Answer. If you get the SDK installed on the device, createdump can be used to dump single file apps. Didn't work for...
Read more >
dotnet-dump collect error: Writing dump failed (HRESULT ...
I'm trying to create a dump on Debian 10.4 of a dotnet core 3.1.301 x64 bit app running under a service controlled by...
Read more >
Troubleshoot crash and GC issues with dotnet-dump
Run dotnet-dump collect -p 15586 , and notice that this fails unexpectedly. Screenshot of dotnet collect command. The following error message is ...
Read more >
Identifying Memory Leaks with dotnet-dump and ...
In this tutorial, you will learn how to monitor memory usage of a Tizen .NET application and identify possible memory leaks using ...
Read more >
使用dotnet-monitor sidecar模式dump docker运行的 ...
如果我们的需要dump内存文件, 可能会遇到 WriteDumpAsync failed - HRESULT: 0x00000000 issues 1783这样的错误, 是因为权限问题.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found