By vako on

I noticed that there are several files in the root folder of Drupal 6.x named core.####, where #### is a number. Each is more than 50MB in size and seems to be multiplying in number.
What are these files, is it safe to delete them?

⋅ Categories: Drupal 6.x

Comments

vako’s picture

vako commented

Strange, I thought I will be getting a solution for this issue quickly, since people usually don't like to see their website grow exponentially with huge files. Is this happening only to me?? I doubt it.

Please anyone! let me know if I can delete those 50MB files and where they are coming from.

Thanks!

WorldFallz’s picture

WorldFallz commented

http://drupal.org/search/node/core.

===
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime." - Lao Tzu
"God helps those who help themselves." - Ben Franklin
"Search is your best friend." - Worldfallz

vako’s picture

vako commented

Here's a probably solution:
The core dump files might be caused by the print module's PDF option. Drupal's 'normal' cache can't handle PDFs, so if you have that option enabled, it might be the culprit that creates the dump files.
There is an update that solves this issue: http://drupal.org/node/362121

deanflory’s picture

deanflory commented

I too am having this issue with core.XXXXX files showing up in the Drupal 7 folder on my server.

They've maxed out my drive space to the point the site is no longer operational. SOOO, I'm going to try deleting them and see what happens. This is the third night this has happened but the first time I've "caught" them as it appeared they somehow removed themselves the past 2 nights before I could find the bloating (they've added up to 8GB per day).

deanflory’s picture

deanflory commented

I found another posting and possible semi-answer from styro here:
http://drupal.org/node/115654

vako’s picture

vako commented

I've found out over years, that it's totally safe to delete those files. But strangely, they are not happening on my sites anymore. A module must've caused it.