mudmanc4 Posted May 9, 2013 CID Share Posted May 9, 2013 These files are being dumped in " /" (not root) on a dedicated VPS The machine gets anywhere between 2-10 / 15 minutes. They are binary files (executable files ) with no extension, just leaving successive numbering system after " core.XXXX " I'll drag one to an editor later if I have time to see what can be found , but what is legible outside of ASCII code appears to be related to the mail server. I cannot see any way that the server has been rooted, and permissions of the files are all rw , so they cannot be executed. Idea's ? Quote Link to comment Share on other sites More sharing options...
TriRan Posted May 10, 2013 CID Share Posted May 10, 2013 Nope never seen that before.. What os? What mail server? Quote Link to comment Share on other sites More sharing options...
Solution CA3LE Posted May 11, 2013 Solution CID Share Posted May 11, 2013 They are binary files (executable files ) with no extension, just leaving successive numbering system after " core.XXXX " ... Idea's ?... That's a core dump bro. ref http://www.inmotionhosting.com/support/website/website-troubleshooting/what-are-core-dumps -- hope that helps Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted May 11, 2013 Author CID Share Posted May 11, 2013 I took some time last night deciphering what I could using GDB and figured that out, and thank you. It seems postfix was configured with debug. Fair enough, thought I've not had time enough to find out why it keeps crashing. Have time hopefully this coming week to get into it. Right now I'm seeing it coming from a horde/plesk issue. Quote Link to comment Share on other sites More sharing options...
mudmanc4 Posted May 16, 2013 Author CID Share Posted May 16, 2013 Now I did not care to take the time to find out what was the 'core' issue , but I did find by using GDB that this had something to do with domain authentication between postfix and nginx - since I had not yet gotten terrible deep into using nginx as a reverse proxy, it was eliminated, and the problem for now, at least has been solved. Maybe once nginx allows for .htaccess files I'll dive into that, having so many throughout an older site, even anything latest can cause hours of extra work. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.