Several emails arriving with the error Core files for executables have been found in /var/db/system/cores/

TrueNAS General
1

Hello everyone! I’m running a TrueNAS Scale 25.04.1 on a Dell T130 server. Yesterday, after starting to copy 1.5TB of data from a Western Digital NAS share, my TrueNAS started sending several emails with the following alert:

Core files for executables have been found in /var/db/system/cores/. Please open the shell, copy any core files present in /var/db/system/cores/, and then generate a system debug. Next, create a ticket at https://ixsystems.atlassian.net/ and attach the core files and debug. After creating the ticket, the core files can be removed from the system by opening the shell and entering 'rm /var/db/system/cores/*'.

I ran the command to remove the files, but the messages continued to appear.

Does anyone know what might be the cause? I’ve run tests and the services I’m using on this TrueNAS, Samba and FTP, are working perfectly, so I’d like some help understanding the cause of the problem and how to fix it.

2

Did you do as it says and create a Bug Report, attached the system debug and the core files to the ticket? Link the ticket number created in this thread

2 Likes
3

Simply removing the coredumps is not fixing the problem, it simply hides the issue from you until whatever is crashing does so again.

The instructions explain that you should report it to the developer.
The easiest way of doing that is using the bug report button at the top of the TrueNAS GUI.

1 Like
4

Sorry for the delay in responding; I hadn’t been notified by email that the post had been answered.

In this case, when I ran the command to generate the report, it generated several Python errors. However, I ended up getting sick, and since it was running, I ended up not using it.

From yesterday to today, due to an extratropical cyclone that affected this client’s region, we lost power for a few hours, and when it came back on, the error no longer appeared.

I believe the Samba-related error (the log files were from Samba RPC, if I understood correctly) was probably due to a server reboot or something similar. Luckily, after the reboot, everything stabilized!