Mysterious core files filling up disk on ArcGIS Server on Linux

a month ago
New Contributor II

Hello, I'm on version 10.8 for ArcGIS Server from the Enterprise package.

There are very large files filling up my disk and I can't figure out what they're for in my /arcgis/server/framework/etc/scripts folder, anyone else running into this?

Deleting them does not seem to impact arcgisserver or break any of our geocoders:

[root@localhost scripts]# ls -lah
total 6.5G
drwx------. 1 arcgis arcgis 210 Apr 15 00:00 .
drwx------. 1 arcgis arcgis 4.0K Apr 12 16:01 ..
-rwx------. 1 arcgis arcgis 2.3K Nov 23 2019
-rwx------. 1 arcgis arcgis 16K Nov 23 2019
-rwx------. 1 arcgis arcgis 1.7K Nov 23 2019 arcgisserver
-rwx------. 1 arcgis arcgis 1.8K Aug 25 2020 arcgisserver.service
-rwx------. 1 arcgis arcgis 721 Nov 23 2019
-rw-------. 1 arcgis arcgis 749M Apr 14 00:00 core.19055
-rw-------. 1 arcgis arcgis 541M Apr 14 00:00 core.19118
-rw-------. 1 arcgis arcgis 607M Apr 14 00:00 core.19140
-rw-------. 1 arcgis arcgis 492M Apr 14 00:00 core.19285
-rw-------. 1 arcgis arcgis 500M Apr 13 00:00 core.603
-rw-------. 1 arcgis arcgis 547M Apr 13 00:00 core.605
-rw-------. 1 arcgis arcgis 607M Apr 13 00:00 core.621
-rw-------. 1 arcgis arcgis 750M Apr 13 00:00 core.693
-rw-------. 1 arcgis arcgis 493M Apr 15 00:00 core.8593
-rw-------. 1 arcgis arcgis 551M Apr 15 00:00 core.8651
-rw-------. 1 arcgis arcgis 604M Apr 15 00:00 core.8674
-rw-------. 1 arcgis arcgis 748M Apr 15 00:00 core.8708
-rwx------. 1 arcgis arcgis 1.6K Nov 23 2019 rmid

Tags (2)
0 Kudos
3 Replies
Esri Frequent Contributor

I would recommend reaching out to Esri Technical Support on this for them to review and potentially investigate.

--- George T.
0 Kudos
New Contributor II

Yeah I'll have them investigate as to why they have horrendously terrible documentation on literally every single one of their products. How does no one know what these are?

Esri Contributor

Core files are created by the Linux OS when a program ends unexpectedly. They contain a snapshot of the process memory at time of termination, and the .#### portion of the filename indicates the process id. They are safe to delete but it would be better to analyze them and determine what is failing and why. Here is an article with some good info but the details may differ depending on your version of Linux.

0 Kudos