Home > Enterprise >  Could not open output /home/logs/dumps/coredump. No such file or directory
Could not open output /home/logs/dumps/coredump. No such file or directory

Time:12-21

I am trying to deploy an xaf blazor 21.2.4, .Net 5 app to Linux in Azure. When I go to Diagnose and solve problems in Azure App Services I see an error. The Connection String Information is in Key Vault.

I can see in the Deployment Logs that deployment was successful.

CodePudding user response:

  • Core_pattern is used to specify a core dumpfile pattern name.

  • If the first character of the pattern is a '|', the kernel will treat the rest of the pattern as a command to run. The core dump will be written to the standard input of that program instead of to a file.

  • Make sure your current directory (at the time of crash -- server may change directories) is writable. If the server calls setuid, the directory has to be writable by that user.

  • Also check /proc/sys/kernel/core_pattern. That may redirect core dumps to another directory, and that directory must be writable. More info here.

In any case, the quick answer is that you should be able to find your core file in /var/cache/abrt, where abrt stores it after being invoked. Similarly, other systems using Apport may squirrel away cores in /var/crash, and so on.

Please refer Core dump file is not generated and Core dumped for more details.

  • Related