#10684 closed defect (bug) (invalid)
Mu install issues w/ an auto_increment_offset other than 1.
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Upgrade/Install | Keywords: | mu auto-increment |
| Focuses: | Cc: |
Description
A) No Mu milestone anymore. Unsure which to assign to, http://codex.wordpress.org/Debugging_WPMU should be updated so we don't bug y'all.
A new install on a new DB server does actually work, when the auto_increment_offset & server-id are not 1. Because the installer creates tables with the blog id of 1, but then tries to insert into tables named with the server-id / aio of 7.
ex:
httpd: WordPress database error Table 'wordpressmu.wp_7_options' doesn't exist for query INSERT INTO wp_7_options (option_name,option_value,autoload) VALUES ('blogname','Mu.interactiveone.com Blogs','yes') made by require, include, step3, wpmu_create_blog, install_blog, update_option, add_option
Using 2.8.4 of mu, with mysql 5.0.67, on RHEL 5.3.
Vhost setup.
I was able to sucessfully install by using a different DB server, with an AIO of 1, (our qa db), and then dump & restore the wordpressmu db to the prod server. It worked perfectly (after switching the IP of the DB server in wp-config.php back to the prod server, obviously)
You need to raise this in the mu trac - trac.mu.wordpress.org
Not the core trac.