Rec’ing warning then fatal error in Chrome but not other browsers

  • Resolved Laurie

    (@tlmwebmaster)


    2 years, 5 months ago

    I have an intermittent problem that first started appearing on June 7. The support chat I had with my host Siteground said that because the error doesn’t name a plug-in it must be with the theme.

    In general, a page that has been deployed from our staging site to our main site *may* display the error message below to some endusers and not others or the same enduser (me) can see it in one browser but not others. The error is always the same, regardless of which page has been deployed.

    Warning: require_once(/home/customer/www/thelacemuseum.org/public_html/wp-includes/cache.php): failed to open stream: Too many open files in /home/customer/www/thelacemuseum.org/public_html/wp-includes/load.php on line 716

    Fatal error: require_once(): Failed opening required ‘/home/customer/www/thelacemuseum.org/public_html/wp-includes/cache.php’ (include_path=’.:/usr/local/php74/pear’) in /home/customer/www/thelacemuseum.org/public_html/wp-includes/load.php on line 716

    Today’s problem is that I see this error when I look at https://thelacemuseum.org/past-workshops-images/ in Chrome. I can see the page fine in Firefox and Opera. The Siteground support person could see it fine in Firefox, Chrome and Safari.

    Siteground support said “The error is – > failed to open stream: Too many open files meaning that one of the scripts that were running was possibly miscofugured an opening and running things without closing them until it hits the limit on the server side. Since the path of the error does not mention any specific plugin cause it, this mean it is likely connected to the theme of the website.”

    I’ve cleared all the caches in Chrome and Siteground. How can I fix this problem so it won’t happen again?

    • This topic was modified 2 years, 5 months ago by Laurie. Reason: Added info

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)

  • Hi there,

    theres nothing in the Theme that would cause this kind of issue.
    And the error is not present when i visit that page on any browser. Which makes it harder for us to advise.

    Did the error only arise on this page ? Or were there other pages it appeared on ?

    Thread Starter Laurie

    (@tlmwebmaster)

    Thank you for the reply. The error has also occurred in the past on https://thelacemuseum.org/ and on https://thelacemuseum.org/virtual-education/ both immediately after I used Siteground to edit the particular page on our staging site and then deployed our staging site to the main site. The error resolves itself after a time, usually several hours. The problem I was having last night no longer exists and I can view https://thelacemuseum.org/past-workshops-images/ in Chrome now. While the problem exists, it’s disruptive to end users.

    I don’t understand what the error message is telling me. I’ve never edited the cache.php or load.php file. The error message always refers to line 716 in load.php. These are lines 715, 716 and 717.

    if ( ! wp_using_ext_object_cache() ) {
    require_once ABSPATH . WPINC . ‘/cache.php’;
    }
    Do you have any insight as to what creates cache.php and load.php in an installation: GeneratePress, SiteGround (host) or WordPress 6.0?

    load.php is the core WordPress function that is used to load stuff.
    And some of what its loading will be stored in the WordPress Object Cache which is defined in cache.php.
    They are both core WP functions.

    Those errors are stating that WordPress ran the load.php and when it came to open the stream to the cache.php it failed.
    It failed because there were Too Many Files Open.
    Which meant the server had reached the limit it places on the number of open files, handles or sockets that can be open at any one time.

    There are two ways this could be fixed:

    1. The host could increase the Open file limit on the server. I would expect that siteground would have a handle on this, but it may be worth you asking.

    2. Find the ‘code’ that is responsible for opening too many files ( and not closing them when its done ) and fix that.

    Ultimately it is the Server that controls and limits the processes it can run. If there are processes getting stuck or leaving files open then the Host should be able to investigate this.

    Thread Starter Laurie

    (@tlmwebmaster)

    Thank you for the detailed answer. I will pursue this with our hosting service.

    You’re welcome.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Rec’ing warning then fatal error in Chrome but not other browsers’ is closed to new replies.