Strange Files Are Core.24397 Created In My Ftp Folder

Hi, I have installed latest version 4.6.2. I have noticed files with name core.24397 with huge size are being created in my FTP folder. Fresh Install looks alright, but when you click on any product it takes time and goes to 500 error Internal server error. I checked all folders having permission of 755. When ever I click on any product a core.24xxx file is created in the FTP folder. Please kindly advice me further to avoid these files created in my FTP. Please see attached FTP screen shot.

Here is the Screen Shot of FTP folder.

Here is the screen image of FTP folder.

errors_cscart462.jpg

Filezilla is not the best if you save passwords. This program saves passwords in text readable file, once I got virus in to pc and my website was corrupted instantly..

Core files are usually not present as a result of a hack.
Core files are memory dumps of a process that crashed, in this case, probably php.
Core dumps typically have a file name like: core####.

If you run Apache and have a VPS or dedicated server, you can add this line to your ‘/etc/init.d/httpd’ file, below other ulimit setting:

ulimit -c 0

Core files are usually not present as a result of a hack.
Core files are memory dumps of a process that crashed, in this case, probably php.
Core dumps typically have a file name like: core####.

If you run Apache and have a VPS or dedicated server, you can add this line to your '/etc/init.d/httpd' file, below other ulimit setting:

ulimit -c 0

Many thanks for your a reply. I have asked server people to do this. But they said..... "That line is not valid for the httpd configuration. I attempted to add it and Apache refused to load the configuration." Any further advice on this please.

Many thanks for your a reply. I have asked server people to do this. But they said..... [background=#ffffff]"That line is not valid for the httpd configuration. I attempted to add it and Apache refused to load the configuration." Any further advice on this please.[/background]

Sure, it depends on the server configuration and OS. Anyway if they are the server administrators, they may to know, in which "place/file" have to put the line. The file location and name can be different for each server/configuration. For example "/etc/security/limits.conf" for (Linux), "etc/default/apache2" (Debian) and so on.

If this has been done, you can check the output by executing this command:

ulimit -a

If the core-dump-file-creation has been disabled, then the output should looks like this:

# ulimit -a
core file size          (blocks, -c) 0

Sure, it depends on the server configuration and OS. Anyway if they are the server administrators, they may to know, in which "place/file" have to put the line. The file location and name can be different for each server/configuration. For example "/etc/security/limits.conf" for (Linux), "etc/default/apache2" (Debian) and so on.

If this has been done, you can check the output by executing this command:

ulimit -a
If the core-dump-file-creation has been disabled, then the output should looks like this:

# ulimit -a
core file size          (blocks, -c) 0

Many thanks. Now the problem is solved.

Many thanks. Now the problem is solved.

I'm glad i was able to help you.

John