2.0 Install: Yet Another DB error.

  • Resolved flash87

    (@flash87)


    18 years, 11 months ago

    Sorry, but I don’t see any posts in the forum that seem to fix this.

    I have all the minimum requirements satsified with my hosting server. I’ve walked carefully through all the setup steps and believe I have them correct. When I get to step 2, I see the errors below. Some of the tables don’t get created and/or populated. Please help, and thanks!

    Second Step

    Now we’re going to create the database tables and fill them with some default data.

    WordPress database error: [Column ‘meta_key’ is used with UNIQUE or INDEX but is not defined as NOT NULL]
    CREATE TABLE wp_postmeta ( meta_id bigint(20) NOT NULL auto_increment, post_id bigint(20) NOT NULL default ‘0’, meta_key varchar(255) default NULL, meta_value longtext, PRIMARY KEY (meta_id), KEY post_id (post_id), KEY meta_key (meta_key) )

    WordPress database error: [Column ‘meta_key’ is used with UNIQUE or INDEX but is not defined as NOT NULL]
    CREATE TABLE wp_usermeta ( umeta_id bigint(20) NOT NULL auto_increment, user_id bigint(20) NOT NULL default ‘0’, meta_key varchar(255) default NULL, meta_value longtext, PRIMARY KEY (umeta_id), KEY user_id (user_id), KEY meta_key (meta_key) )

    WordPress database error: [You have an error in your SQL syntax near ‘autoload = ‘no’ WHERE option_name = ‘moderation_keys” at line 1]
    UPDATE wp_options SET autoload = ‘no’ WHERE option_name = ‘moderation_keys’

    WordPress database error: [You have an error in your SQL syntax near ‘autoload = ‘no’ WHERE option_name = ‘recently_edited” at line 1]
    UPDATE wp_options SET autoload = ‘no’ WHERE option_name = ‘recently_edited’

    WordPress database error: [You have an error in your SQL syntax near ‘autoload = ‘no’ WHERE option_name = ‘blacklist_keys” at line 1]
    UPDATE wp_options SET autoload = ‘no’ WHERE option_name = ‘blacklist_keys’

    WordPress database error: [You have an error in your SQL syntax near ‘rel_id, post_id, category_id) VALUES (1, 1, 1)’ at line 1]
    INSERT INTO wp_post2cat (rel_id, post_id, category_id) VALUES (1, 1, 1)

    WordPress database error: [You have an error in your SQL syntax near ‘(‘7669c5’), ‘[email protected]’, NOW(), ‘g3000’, ‘admin’)’ at line 1]
    INSERT INTO wp_users (ID, user_login, user_pass, user_email, user_registered, display_name, user_nicename) VALUES ( ‘1’, ‘admin’, MD5(‘7669c5’), ‘[email protected]’, NOW(), ‘g3000’, ‘admin’)

    WordPress database error: [Table ‘press.wp_usermeta’ doesn’t exist]
    INSERT INTO wp_usermeta (user_id, meta_key, meta_value) VALUES (2, ‘wp_user_level’, ’10’);

    WordPress database error: [Table ‘press.wp_usermeta’ doesn’t exist]
    INSERT INTO wp_usermeta (user_id, meta_key, meta_value) VALUES (2, ‘wp_capabilities’, ‘a:1:{s:13:”administrator”;b:1;}’);

    Finished!

    Now you can log in with the username “admin” and password “xxxxx”.

    Note that password carefully! It is a random password that was generated just for you. If you lose it, you will have to delete the tables from the database yourself, and re-install WordPress. So to review:

    Username
    admin
    Password
    ********[password moderated]
    Login address
    wp-login.php

Viewing 7 replies - 16 through 22 (of 22 total)
  • Thread Starter flash87

    (@flash87)

    Actually, I think I’m going to give up. There are a whole host of syntax errors to address besides the uncreated tables. It’s too much of a hassle.

    Thanks to everyone who tried to help.

    Thread Starter flash87

    (@flash87)

    OK…thought I’d try one more thing. (I’m not sure if the reply form will submit this right, but basically what i’m doing is taking out tickmarks and manually submitting commands and it’s working.)

    It turns out MySQL doesn’t like the backticks. In some cases, it doesn’t like tickmarks at all. With my most recent attempted installation, when I go into the shell and try entering a command that failed, like…

    INSERT INTO wp_post2cat (rel_id, post_id, category_id) VALUES (1, 1, 1)

    …it chokes. But if I change it to…

    INSERT INTO wp_post2cat (rel_id, post_id, category_id) VALUES (1, 1, 1)

    So, assuming I get it to work with all this manual setup, will it continue to work, or does WordPress code have these marks that will cause syntax errors with my installation of MySQL all the time? I’m confused.

    Thread Starter flash87

    (@flash87)

    Well, that only worked with some of the failed MySQL statements. I have no idea how to manually enter the others and make the syntax work.

    I appreciate any other suggestions anyone might have. The only other thing I’ve thought of was to check the error log. Might this mean anything?

    [Tue Mar 21 10:26:46 2006] [warn] module php4_module is already loaded, skipping
    [Tue Mar 21 10:26:46 2006] [warn] module php4_module is already loaded, skipping
    [Tue Mar 21 10:26:46 2006] [warn] module php4_module is already loaded, skipping
    [Tue Mar 21 10:26:46 2006] [warn] module php4_module is already loaded, skipping
    [Tue Mar 21 10:26:46 2006] [warn] module php4_module is already loaded, skipping
    PHP Fatal error: Unable to load dynamic library ‘mysql.so’ – Shared object “mysql.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘msql.so’ – Shared object “msql.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘imap.so’ – Shared object “imap.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘ftp.so’ – Shared object “ftp.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘mcrypt.so’ – Shared object “mcrypt.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘gettext.so’ – Shared object “gettext.so” not found in Unknown on line 0
    PHP Fatal error: Unable to load dynamic library ‘sockets.so’ – Shared object “sockets.so” not found in Unknown on line 0
    [Tue Mar 21 10:26:46 2006] [notice] Apache/1.3.33 (Unix) PHP/4.0.0 configured — resuming normal operations

    Thread Starter flash87

    (@flash87)

    If someone could just let me know if this is purely a hosting or server configuration issue, and has nothing to do with WordPress, that would help. I’m not getting any response from Verio and this will let me know if I have to really jump on them or find out if it’s something I could fix myself. Thanks.

    Those aren’t good errors — and WP doesn’t write them out. I’d, personally, start shopping for hosts.

    Hey, check your encoding — I just found mine is now Latin1_swedish_ci and prior to upgrade it was UTF8_general_ci

    Now if I could figure out how to change the collation back I could see if that fixes things for me.

    Thread Starter flash87

    (@flash87)

    Thanks for the idea. Where is the encoding set (and how do I change it)? In MySQL or the WordPress PHP scripts?

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘2.0 Install: Yet Another DB error.’ is closed to new replies.