WordPress.org

Support

Support » Installation » [Resolved] Getting internal server error after install

[Resolved] Getting internal server error after install

Viewing 15 replies - 1 through 15 (of 28 total)
  • foolswisdom

    @foolswisdom

    Moderator

    Just guessing, but possibly you uploaded the wrong/another .htaccess file?

    If you just have the one first try renaming it to something else and see if you still have an issue.

    I took a look, and what has happened is that it did sort of a nested install. I’m deleting the new install and going to upload elements one by one and see if that helps.

    Ok, now I’m getting: Warning: main(/home/content/e/l/v/mydatabasename/html/wp-includes/wp-db.php): failed to open stream: No such file or directory in /home/content/e/l/v/mydatabasename/html/wp-settings.php on line 100

    Fatal error: main(): Failed opening required ‘/home/content/e/l/v/mydatabasename/html/wp-includes/wp-db.php’ (include_path=’.:/usr/local/lib/php’) in /home/content/e/l/v/mydatabasename/html/wp-settings.php on line 100

    Make sure you’ve uploaded the following two files right:
    wp-includes/wp-db.php

    And: /wp-settings.php

    The first goes in the wp-includes/ folder.
    The second files goes into the blog’s root folder, where the wp-config.php file is..

    spencerp

    Still getting the message. I checked to make sure they were there, and then noticed that once again, I had the 2.1 Content file nested into my old content file. And I also noticed a Backup file in my root directory that I did not put there? I removed the extra content file and now the backup file is also gone, but still getting the exact same message.

    Thanks for the help, Spencer!

    Oops, I take that back. The backup file is in my content. I specifically did the backup as a download when I did this last night, and I also did NOT nest any files manually.

    Could the backup be interfering with the program finding the right path?

    One of the files spencer mentioned must be corrupted. Maybe download fresh ones and upload again?

    Ok, I’ll give that a shot. I’m a pretty complete newbie at this. My first install of 2.0.6 was three weeks ago. Knowing this one was coming I didn’t upgrade to .7.

    WOW! This is aggravating, but thanks for all your patience. Now my page is coming up, http://www.womanwithmanyhats.com , but I first get an error message that stays on the screen after the theme loads, and there are no posts on the page. I’m not getting the setup link at all.

    Here’s the error message: Warning: fopen(/home/content/e/l/v/my databasename/html/wp-content/cache/wp_cache_mutex.lock): failed to open stream: No such file or directory in /home/content/e/l/v/mydatabasename/html/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 94

    I’d rather not have my database name out there any longer!

    That message points to a plugin conflict. Try deactivating them then re-activating them one by one?

    There aren’t any activated. I do, however, have wp-cache as a plugin (not activated).

    And what about that backup? Is that an issue?

    Are you sure your wp-cache plugin was upgraded to the latest version?
    http://codex.wordpress.org/Plugins/Plugin_Compatibility/2.1#W_-_Z

    spencerp

    Nope, I hadn’t done anything yet. On first upgrading, I was getting a 500 error and couldn’t get into my site at all. This last effort produced my website, but no wp-admin/upgrade.php screen. So that’s as far as I’ve gotten. I haven’t upgraded anything other than WP itself yet.

    Ok, I dropped the upgrade.php into my browser and it loaded, still with that message at the top of the screen, and all my posts are there again. I’ll try upgrading my plugins and see if that works. Again, none have been activated; would it still be doing that if not?

    Oh ok, well make sure ALL of your plugins are compatible with 2.1 okay? If they aren’t listed over here, contact the plugin authors to update them and add them to the page.

    http://codex.wordpress.org/Plugins/Plugin_Compatibility/2.1

    Also, *some* might work regardless, but if they don’t, disable them until the plugin authors update them.

    spencerp

Viewing 15 replies - 1 through 15 (of 28 total)
  • The topic ‘[Resolved] Getting internal server error after install’ is closed to new replies.
Skip to toolbar