Hi all

I download right now the dev version of drupal 8 of today (16.05.2013).
On trying to install this on my server, i became the follow error, after put the DB credentionals and information

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbname.cache_bootstrap' doesn't exist: DELETE FROM {cache_bootstrap} WHERE (cid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => system_list )

known error?

I dont find anything in the issue liste for drupal 8

regards and thx
cola

Comments

cola’s picture

cola commented
Status: Active » Needs work

Hi All

can anybody help with this bug?

regards

noneTaken’s picture

noneTaken commented

Same problem here with dev and alpha 2 version.

EDIT
In my case, it has something to do with either Zend server CE 5.6 or PHP5.3. Probably Zend server.

gamelodge’s picture

gamelodge commented

Same for me - both alpha and dev.
PHP 5.3.14

mpp’s picture

mpp commented

Error occurs during installation:

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'cache_bootstrap' doesn't exist: DELETE FROM {cache_bootstrap} WHERE (cid IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => system_list )

Using PHP 5.3.26

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Weird, those tables are supposed to be auto-created. Maybe not on delete?

chx’s picture

chx commented

That's not it. deleteMultiple is wrapped in try - catch (\Exception $e) { $this->catchException($e); } as everything else and catchException only propagates the exception if the table exists.

pflame’s picture

pflame commented

I am facing the same problem in my windows 7. Once when I select the minimal profile the installation finished but I got these errors every time I install a new module. When I drop the table which is mentioned in the error, the module is getting installed and the table is creating again.

pflame’s picture

pflame commented

After lot of research, I found that this is the issue with Operating System and Mysql. In my case the problem is with the INNODB engine. In the Mysql error log, I got errors saying Innodb can not have access to create file in the data directory.

When create table command executed, Mysql is able to create .frm file but .ibd file Innodb could not create, so because of that, the table creation is not complete, for insert command it will raise error saying table does not exists, for create command it will raise error saying the table already exists.

Finally I fixed this problem by installing Mysql 5.7 in F:\ drive. The issue might be because of the empty space in the Drive. Don't know exact solution but it is not related to Drupal, it is related to Mysql and Operating System.

cola’s picture

cola commented
Issue summary: View changes

We became this error with PHP 5.3
Now we change it to PHP 5.5 and it works fine

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Anonymous’s picture

Anonymous (not verified) commented
Status: Needs work » Closed (outdated)

Per #9 it was solved with PHP 5.5. Now it is minimal supported version.