- This topic has 2 replies, 2 voices, and was last updated 12 years, 7 months ago by .
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › The store is writing huge files to the server for each order
Hi,
Whenever a customer places an order, new files are showing up in our eStore directory. The files are all named “core” followed by a 5-digit number. (For example, “core.20501” or “core.30581”. The number is different every time.) What are these files and why do they appear each time there’s a new order? How do we make it stop?
Thanks!
Kristen
Sorry, just to clarify my previous message…
The files are not showing up in the eStore plugin directory, they’re showing up in the directory where WordPress and eStore are running. (i.e., http://www.OurDomain.com/shop)
Thanks
Not sure where you got the idea that eStore is creating those files (WP eStore can’t create those files even if it wanted to).
http://linux.die.net/man/5/core
One of the executable processes on your server is experiencing an exception error, of one kind or another. The core dump file is created by your server, and is supposed to aide in the debugging process. The number corresponds to the process ID of the process that crashed.
WordPress and all of its themes and plugins are scripts, that cannot directly “crash” and create core dump files. Most likely, something caused the PHP interpreter or MySQL database process to ABEND and restart.
Because you haven’t noticed any other errors that prevent order processing from properly occurring, it seems that when the server restarts the crashed process, that everything continues as it should. Given this, you have a decision to make; either “hunt down” and correct the cause of the process exceptions, or ignore them and supress the creation of the core dump files. In either case, you need to work with your hosting provider.