Answers.Body: <p>Those aren't Craft log files.  I'd suggest contact your host and give them the files so they can look and see what's dumping them and what the root problem is.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-18T09:55:34.153Z
Answers.Text: haha I am the host with  server tech manager on hand. Its only happening on my craft installations. I noticed 3 dumps this morning and the craft logs show something weird. They show 2017/01/10 14:44:15 [error] [exception.CDbException] SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO). Almost like its reading my local dev config instead of the staging config...
Answers.UserDisplayName: joomkit
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-18T22:55:23.197Z
Answers.Text: I have found the matching of host names to config sections in Craft to misbehave at times, and therefore be dependent on order.
Answers.UserDisplayName: Jeremy Daalder
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-19T05:14:00.437Z
Answers.Text: @joomkit Just confused, I suppose. You said `core..xxx` files were dumped, but that error message looks like a Craft log entry.  Regardless, for that particular message, that's something that Craft/PHP/PDO will often return as an error message when it can't connect to the database (for whatever reason). It's a bit misleading, I agree.
Answers.UserDisplayName: Brad Bell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-20T13:38:50.443Z
Answers.Text: Just had this happen again and went thru the logs - there is nothing in craft logs to indicate anything prior to the dump - I have seen funky behaviour from host names before so suspect it might be that or some random nginx cache issue.....once i solve i'll post back
Answers.UserDisplayName: joomkit
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-29T11:43:17.550Z
Answers.Text: Seems to have been resolved now. I cant offer much in exact solution other than that we upgraded to easyapache 4 (WHM/Cpanel) and it's stopped happening. Switched to php7 and tested on php5.6 and problem has disappeared. Happy and confused about it. thx
Answers.UserDisplayName: joomkit
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-17T18:08:08.623Z
Answers.LastActivityDate: 2017-03-17T18:08:08.623Z
Answers.UserDisplayName: Brad Bell
Body: <p>Am suddenly finding lots of core..xxx files dumped in the root of my site.
  In devMode cant see any issues. Assume this is serious issue and memory dump?</p>
  
  <p>Where to start? Logs have loads of stuff but nothing that gives me a clue to this.</p>
  
Tags: <server>
Title: finding core dumps in public root
ThreadText: # finding core dumps in public root
  
  (Asked by: username_0 on 2017-03-17)
  
  Am suddenly finding lots of core..xxx files dumped in the root of my site.
  In devMode cant see any issues. Assume this is serious issue and memory dump?
  
  Where to start? Logs have loads of stuff but nothing that gives me a clue to this.
  
  **Tags:** server
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-03-17. Score: 1
  
  Those aren't Craft log files. I'd suggest contact your host and give them the files so they can look and see what's dumping them and what the root problem is.
  
  > **Comments:**
  > **username_0**: haha I am the host with  server tech manager on hand. Its only happening on my craft installations. I noticed 3 dumps this morning and the craft logs show something weird. They show 2017/01/10 14:44:15 [error] [exception.CDbException] SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO). Almost like its reading my local dev config instead of the staging config...  
  > **username_2**: I have found the matching of host names to config sections in Craft to misbehave at times, and therefore be dependent on order.  
  > **username_1**: @username_0 Just confused, I suppose. You said `core..xxx` files were dumped, but that error message looks like a Craft log entry.  Regardless, for that particular message, that's something that Craft/PHP/PDO will often return as an error message when it can't connect to the database (for whatever reason). It's a bit misleading, I agree.  
  > **username_0**: Just had this happen again and went thru the logs - there is nothing in craft logs to indicate anything prior to the dump - I have seen funky behaviour from host names before so suspect it might be that or some random nginx cache issue.....once i solve i'll post back  
  > **username_0**: Seems to have been resolved now. I cant offer much in exact solution other than that we upgraded to easyapache 4 (WHM/Cpanel) and it's stopped happening. Switched to php7 and tested on php5.6 and problem has disappeared. Happy and confused about it. thx  
  
  ---
  
  