I’ve never noticed it until today but it shows it was created about the time I updated from 2025.10.x to 2025.11.x around December 4th.
I had been wondering my my disc usage number has been slowly rising recently and noticed this huge file when I was doing a backup that usually takes 45 seconds was taking several minutes.
Does anyone know what it’s for, why it got created and more importantly if I can get rid of it.
EDIT:
Opening it up in Notepad++ looks like it contains lots of system data that isn’t decipherable.
the first part looked like it had all of my automation trace data but the later on it was lots of other non-automation related system/integration stuff.
It seems kind of useless to create a crash log that’s not a log file and then don’t tell you that it was even created. I never even saw anything that looked like a crash at the time.
but thanks for the info. It’s gone now and everything still seems to be working so like I said…useless.
Unfortunately that doesn’t tell me why my disc use is slowly increasing along with my DB.
UNIX and derivatives like Linux have had an emergency debug feature built into them since the 1970’s where the OS kernel will panic and dump core (write the entire contents of RAM back when RAM was still magnetic core memory) into a core file in the event of a fatal processor crash, so that the developer can examine the machine’s state with a debugger to determine what went wrong. Things are so far gone when the kernel panics that it can’t even write a log file, and has no way to tell the user that it’s dumping core other than via text on the system console/terminal. As was said above, just delete the file…
well I guess that it least dumped it somewhere that I was able to fairly easily notice it (even if by accident) so that I could delete it and not just have it hanging around wasting system resources for no benefit.
But the question is if it was a system level crash (that was in no way apparent to me at all that it had crashed) that was created by the Linux kernel itself then why did it create it in my HA config folder or better how did it know to create it there? I’m not using HA OS (running HA Container) so the OS is not in any way related to the Docker container that HA is running in. I would have expected it to create the crash file in the OS somewhere, not in a docker container folder.