By sp_key on

Hi all,

This is a fresh installation of Drupal 7 on a subdomain.
It is as downloaded from Drupal.org.

Can you please share your thought?
Thanks!

⋅ Categories: Drupal 7.x

Comments

heine’s picture

heine commented

The installation failed.

Without more info, there's not much we can say.

sp_key’s picture

sp_key commented

I thought the subject was a good indication since it is the only error I received.

However, please disregard this post.
I had edited the setiigns.php file prior to installation thinking it a good practice.
It seems I have now managed to install d7 properly.

Thanks for your time

codare’s picture

codare commented

Hi

I had the exact same problem. Had used auto installer from my web host cPanel =>softaculous and also retried with fantastico BUT still had the same issue. It looked like there was something wrong with the auto installation process even though everytime it said it was successful.

Then I remembered I'd seen a file in the root folder of my site called install.php

Opened up Chrome and typed in the uri - http://mydomain/install.php and magically the "real" installation process started AND it worked beautifully.

Worked for me... might work for you (worth a try)

roblog’s picture

roblog
Primary language English
Location Cymru
commented

Thanks .. I'd never have figured that out. Just wasted about 2 hours trying to get install to work. This has never happened to me on an install before. Weird

heine’s picture

heine commented

If you believe this is common with this particular 'auto' install, please consider adding a page to the troubleshooting faq.

dirckdigler’s picture

dirckdigler commented

Your solution Codare, work for me, I put this path into the url borwser: http://127.0.0.1/name_project/install.php and started the Drupal initialization

hyates’s picture

hyates commented

I wish drupal.org had a downvote feature so I could give this utterly useless comment one.

heine’s picture

heine commented

See the relevant page in the Troubleshooting faq if you are still having this problem.

See also Tips for posting to the Drupal forums.

gumpdotfr’s picture

gumpdotfr commented

For hyates
Despite the trolling I agree.
I wish there was at least a UpVote feature so each solution could rise among the mud...
Let's make this a goal linked to our commits http://drupal.org/user/718592/track/code
Yet I don't know how, sorry Hates I might need your help for this...

"I wish drupal.org had a
Posted by on October 12, 2011 at 3:09pm
I wish drupal.org had a downvote feature so I could give this utterly useless comment one."

ahmed.raza’s picture

ahmed.raza commented

I wish drupal.org had a downvote feature so I could give this utterly useless comment one.

+1

AhmedSiddieg’s picture

AhmedSiddieg commented

I had this problem .. and I found the problem came when my database name match the dataBase username
..

Just try the change them to be different ..

and don't forget to change the setting file in sites folder
( delete 'setting' file ,copy default.setting and rename it 'setting' ).

lexbi’s picture

lexbi commented

Seem to be getting this error when I import a backup database from another server on a working fresh install of Drupal.

I get it despite me not edited the 'settings.php' file.

The table exists, and, works on another server. Any ideas?

Will contact server host and let you know what comes up.

I don't think I'm doing anything to derpy, but I'm sure you'll let me know if I am being :P

Anything help would be great, thanks.

Joe

hbblogger’s picture

hbblogger commented

I have the same error. I'm importing a database from WAMP to a working installation on my server and I get the error.

aendra’s picture

aendra commented

I found this thread after being really confused while importing a SQL dump from dev to staging. I had just imported the dump and was getting the message, which was really confusing considered I'd connected via MySQL and was looking at the very table Drupal said was missing.

Then after about 10 minutes I realized I had done everything into a local terminal window, and not the one with a SSH session on staging.

I even have them colour-coded so I don't do that sort of thing.

Seriously, I feel dumb right now.

Ændrew Rininsland
News Developer and polynerd
http://www.aendrew.com

digibrill’s picture

digibrill commented

I am also importing a DB from live to dev and got this error. Anyone have an idea? Thank you!

digibrill tic

heine’s picture

heine commented

Does the table exist in the dump? Did the import give any errors?

digibrill’s picture

digibrill commented

I guess not, as the error still appears. When I create the table using a create table SQL statement I found here, the message stops-but I now have a WSOD. I have no error message yet and am going to check the logs when I get in tomorrow. Repeating the import and recreating the table with the SQL statement, I get the same WSOD.

digibrill tic

heine’s picture

heine commented

Why not check the sql file with eg grep? That would at least provide some indication whether the export or import have a problem.

digibrill’s picture

digibrill commented

Have not used grep, but am familiar with reg exp. What am I searching for?

Thanks.

digibrill tic

tkittich’s picture

tkittich commented

I just got the same error in a dev machine with database restored from a live machine. Have anyone found a solution?

Also, for me the error message shows the wrong database prefix. "Base table or view not found: 1146 Table 'db.semaphore' doesn't exist" should be 'db.d7_semaphore' because I have a 'd7_' prefix on both the live and dev machine and in settings.php too.

tkittich’s picture

tkittich commented

I got this figured out. I am using Acquia Dev Desktop and imported a site to a dev machine as localhost7 to be accessed locally as http://localhost7. Somehow in drupal "sites" directory i got both "default" and "localhost7" directories containing the same set of files. And that confuses drupal. Once I removed "sites/localhost7" this issue is gone. ^^

Soundean’s picture

Soundean commented

I got this while trying to recover from a site crash, I dumped and restored the db from a backup and got this error message.
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mydb.drupal_semaphore' doesn't exist: SELECT expire, value FROM {semaphore} WHERE name = :name; Array ( [:name] => variable_init ) in lock_may_be_available() (line 167 of mysite.com/includes/lock.inc).

Replacing the current db generated this same error. Any suggestions? Site currently down.

christopher james francis rodgers’s picture

christopher james francis rodgers commented

Drupal 7 - I downloaded existing online-webhost site
originally created/maintained by webhost's
free Control-Panel 'automated script service', SimpleScripts;

& Now I am trying to run it locally on my computer
using 'Acquia Dev Desktop'.

===

My [Solution]:

Add
'prefix' => 'dr_',
to settings.php

[1 Solution] Error: PDOException: SQLSTATE[42S02]: ... semaphore

 


All the best; intended.
-Chris (great-grandpa.com)
___
"The number one stated objective for Drupal is improving usability." ~Dries Buytaert *

mohsin.rafi’s picture

mohsin.rafi commented

Adding the database data to settings.php makes Drupal "believe" it is already installed.

Do not edit settings.php manually; please follow the steps in INSTALL.txt.
In most cases you cannot rescue the install by visiting install.php, as the installation will now abort with the error

Table variable already exists.

To solve this, discard your manually edited settings.php file, empty the database, then follow the steps in INSTALL.txt.

mark_fullmer’s picture

mark_fullmer
he/him
Primary language English
Location Tucson
commented

One reason this might happen:
(A) You are copying an existing database onto a new install
(B) You correctly import the database
(C) You copy default.settings.php lines below and forget to check whether the "prefix" item is correct:

  $databases['default']['default'] = array(
    'driver' => 'mysql',
    'database' => '',
    'username' => '',
    'password' => '',
    'host' => 'localhost',
    'prefix' => 'main_',
    'collation' => 'utf8_general_ci',
  );

In other words, if you're using underscores in your database names, this might get confused with the default prefix

sashkernel’s picture

sashkernel commented

Also had this issue when moving site from WAMP server to my Linux server.
Noticed that all my tables had "primary_" prefix in them. Adding this prefix in SETTINGS.PHP resolved this issue for me.
Making solution (C) to be a valid fix for me.