Support » Fixing WordPress » Suddenly… an error?

  • I have had WP installed and running for several months and just today (while trying to post some new blogs) I get this error:

    Warning: main(/home/assisted/public_html/newsBlog/wp-includes/cache.php): failed to open stream: Too many open files in /home/assisted/public_html/newsBlog/wp-settings.php on line 108

    Fatal error: main(): Failed opening required ‘/home/assisted/public_html/newsBlog/wp-includes/cache.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/assisted/public_html/newsBlog/wp-settings.php on line 108

    I am running WP 2.0.4.

    Thoughts? Any help is appreciated.

Viewing 9 replies - 1 through 9 (of 9 total)
  • 1st thought: Upgrade.
    2nd thought: Disable cache – it doesn’t do anything useful.
    3rd thought: delete everything from wp-content/cache directory (I mean from the cache directory, or better delete it at all)

    Oh, guess I didn’t realize there was an upgrade. I will try that (and your other suggestions) and report results.

    OK, upgrading did not fix it. However, disabling cache (using the ‘define(‘DISABLE_CACHE’, true);’ in wp-config.php) did, it seems. Now, I have heard that adding that command is not, in fact permanent in some way? Is this true?

    OK, I take it back. Just posting some tests and wham… got the same error again. Any other ideas??

    FWIW, I don’t have a wp-content/cache directory or file.

    Wow. Now I am getting more errors:

    Warning: file(/home/assisted/public_html/newsBlog/wp-content/themes/default/style.css): failed to open stream: Too many open files in /home/assisted/public_html/newsBlog/wp-includes/functions.php on line 1762

    Warning: implode(): Bad arguments. in /home/assisted/public_html/newsBlog/wp-includes/functions.php on line 1762

    All I did was click on the link to go to Presentation in admin.

    I haven’t done anything to change my site or config. Why is this just now happening?

    Another thing is these go away if I wait a few minutes and try what ever gave the error originally again. Could this be some sort of bandwidth limitation? The blog certainly doesn’t get much use…

    Sorry guys… bump?

    Generally, if you’ve done nothing yourself to the blog files etc. then you should contact your server host provider to see if they did something to the programs on their end – apache, php, mysql, etc.

    Ask them, then let us know what they say….

    Cool. I have been in contact with my hosting provider and they are stumped. But I know it is on their end because I also run an XMB Forum on another site I have (on the same virtual dedicated server) and I get similar errors there now as well.

    But so far, no resolution. I may have to move to another provider if they can’t find this issue. And I’ve been with them for about 10 years now.

    If your blog is running on a Linux box:
    Tell your ISP to check what “ulimit -aS” spits out. They should also dump the contents of /proc/sys/fs/file-max. It’s rare for Linux to run out of file descriptors, but is possible, especially if they are hosting a lot of active websites on a single computer.

    I have no suggestions if it’s running on Windows as I would never run anything important on that toy OS.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Suddenly… an error?’ is closed to new replies.