ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

.core files in my server?

January 09, 2012 10:26pm

Subscribe [3]
  • #1 / Jan 09, 2012 10:26pm

    bmovie

    619 posts

    Hi have a lot .core files in my server, each have a size of 40mb!!! now I have around 50gb of those files; I ask to cpanel people and they say maybe is related with and app installed (expression engine) and the zend engine.

    I dont know anything about it, but I really need stop that get that kind of files, beacuse my server collapse.

    help please

    phpinfo:

    This program makes use of the Zend Scripting Language Engine:
    Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies
      with the ionCube PHP Loader v4.0.9, Copyright (c) 2002-2011, by ionCube Ltd., and
      with Zend Optimizer v3.3.9, Copyright (c) 1998-2009, by Zend Technologies

     

  • #2 / Jan 11, 2012 3:07am

    John Henry Donovan

    12339 posts

    Hi bmovie,

    EE does not use Zend in any way. It did once when the trial of EE came out first but not since then.
    Do you have any other applications running on your server?

    I found this on Google

    A core file is created when a program terminates unexpectedly, due to
    a bug, or a violation of the operating system’s or hardware’s
    protection mechanisms. The operating system kills the program and
    creates a core file that programmers can use to figure out what went
    wrong. It contains a detailed description of the state that the
    program was in when it died.

    If would like to determine what program a core file came from, use the
    file command, like this:

    $ file core

    Once you have determined what application is causing the dumps let us know. If it is EE then we can investigate this further

  • #3 / Jan 11, 2012 1:32pm

    bmovie

    619 posts

    Hi bmovie,

    EE does not use Zend in any way. It did once when the trial of EE came out first but not since then.
    Do you have any other applications running on your server?

    I found this on Google

    A core file is created when a program terminates unexpectedly, due to
    a bug, or a violation of the operating system’s or hardware’s
    protection mechanisms. The operating system kills the program and
    creates a core file that programmers can use to figure out what went
    wrong. It contains a detailed description of the state that the
    program was in when it died.

    If would like to determine what program a core file came from, use the
    file command, like this:

    $ file core

    Once you have determined what application is causing the dumps let us know. If it is EE then we can investigate this further

    thank you John, I go to search what app is, I know that just EE have installed, but can be any of the add ons the problem? any of the add on installed on ee? I have around 8 add-ons, zoo visitor, zembu, simple search, matrix, etc…

    I let you know

  • #4 / Jan 13, 2012 2:17am

    John Henry Donovan

    12339 posts

    bmovie,

    but can be any of the add ons the problem?

    You will need to run the file command as suggested or indeed contact your host with this information to run it for you

    Let us know what you find out.

  • #5 / Feb 07, 2012 1:25pm

    bmovie

    619 posts

    bmovie,

    but can be any of the add ons the problem?

    You will need to run the file command as suggested or indeed contact your host with this information to run it for you

    Let us know what you find out.

    I run the command and I get this:

    ———————————
    file core.1234

    core.1234: ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from
    ‘php’

    ———————————
    gdb httpd core.1234

    Can’t read symbols from system-supplied DSO at 0x7fff4399c000: File truncated
    Core was generated by `/usr/bin/php /home/atyoux/public_html/index.php’.
    Program terminated with signal 11, Segmentation fault.

    ?? confused
    the .core appear and appear everyday, each size 40mb!!! I get easily 4gb per day or more in my server, help please

  • #6 / Feb 10, 2012 5:58pm

    Dan Decker

    7338 posts

    Hi bmovie,

    Core was generated by `/usr/bin/php /home/atyoux/public_html/index.php’.

    Is that the same path to your ExpressionEngine index.php? If so, it would seem that ExpressionEngine is triggering the dump.

    What version of ExpressionEngine are you running? Can you copy and paste the contents of your index.php for us to examine? Be sure to take out any sensitive information.

    Cheers!

  • #7 / Feb 10, 2012 6:00pm

    bmovie

    619 posts

    Hi bmovie,

    Core was generated by `/usr/bin/php /home/atyoux/public_html/index.php’.

    Is that the same path to your ExpressionEngine index.php? If so, it would seem that ExpressionEngine is triggering the dump.

    What version of ExpressionEngine are you running? Can you copy and paste the contents of your index.php for us to examine? Be sure to take out any sensitive information.

    Cheers!

    hi thank you Dan, yes is the same path

    v2.2.2 - Build: date 20110801

    here is the .php

    I have 500 cores! 40 mb each and increment everyday!

    http://i.imgur.com/18qiy.png

  • #8 / Feb 13, 2012 4:06pm

    Dan Decker

    7338 posts

    Hi bmovie,

    I think we should get the team to take a closer look at this. I’m going to escalate this in order to get a closer look. Be on the lookout for an email from me.

    Cheers!

  • #9 / Feb 13, 2012 4:44pm

    Kevin Smith

    4784 posts

    bmovie,

    I’m afraid there’s just nothing else we can do to help prevent the core.* files from dumping to your web root. From the research I’ve done, it doesn’t appear to be unique to any application but is instead a product of the web server crashing and dumping its working memory to core.* files for sysadmins to debug. Your host may be able to make more sense of the files themselves, but I suspect the issue lies more with the server setup than anything. From EE’s perspective, the only thing I can recommend is to make sure your server is up to snuff with the necessary requirements. Then work with your host to determine where the misconfiguration in your server lies and tweak those settings.

    Best of luck!

  • #10 / Jun 08, 2012 4:40am

    amityweb

    162 posts

    Hi

    I am also getting this… but its ONLY on my Expression Engine sites. I have a lot of sites on the server, the server has been there for a while and worked fine. It only started happening recently on EE sites, so maybe its an upgraded/new version of EE.

    Using file core.xxxx outputs the same as bmovie.

    Using strings core.xxx outputs the file, too big to post, but the first line in it references EE’s index.php.

    /usr/bin/php /home/mysite/public_html/index.php

    The last bunch of lines in the file also reference EE’s index.php and some site pages… so its something to do with EE

    Thanks

  • #11 / Jun 08, 2012 4:47am

    amityweb

    162 posts

    I think I have figured out what is causing the core file, but not the cause of the cause!

    In the core file dump it references some site page URLs and server 500 errors. The URLs are like:
    /site/blog/a-blog-post/

    Well, I do not use /site/ in my site. I have removed this in .htaccess.

    So for some reason, someone (Bing is referenced in the files I checked) is calling this URL, EVEN though its not linked to on my site at all??

    This URL gives a server 500, and the core file is being created (a 40Mb error file for every error, wow!). I’m getting many every day.

    So I need to fix the server error at this page first.

    But then need to find out why Bing or anyone else is calling this page, when its not linked anywhere! UNLESS its EE calling it, before the .htaccess kicks in??

  • #12 / Jun 08, 2012 4:51am

    amityweb

    162 posts

    Figured out… I wasn’t actually using htaccess to remove site. But in htaccess I have some redirects from an older site URL indexed in Google to go to my new EE links, which had /site/ in it. I used to have /site/ in the URLs. I removed /site/, I think using pages, but did not update the htaccess redirects, which go to a server error 500.

    So anyway… in summary they were dumps based on server 500 errors. Running “strings core.xxx” at the command prompt, and looking at the very last 30 or so lines showed me the error and offending URLs causing it.

  • #13 / Jun 08, 2012 4:57am

    amityweb

    162 posts

    Final update on my problem…

    anything with /site/ in it (my main template group) should be redirected to my 404. But the check for this /site/ in the URL was in my header which my 404 used. So I guess the server 500 error was from a loop, because the 404 would have /site/ in the URL so be trying to redirect to itself all the time! So I need to fix that.

  • #14 / Jun 12, 2012 12:12pm

    Dan Decker

    7338 posts

    Hi amityweb,

    Thanks for keeping us in the “loop”, so to speak 😉

    I’m glad you were able to sort it out. Indeed, a redirect loop would make the server pretty sad.

    If you need anything else, please let us know.

    Cheers,

  • #15 / Jun 12, 2012 3:36pm

    bmovie

    619 posts

    I go to check all, related with amityweb and see if I can fixed too

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases