Ready to get started?Download WordPress


Yet Another Step 2 Post (4 posts)

  1. gehwokka
    Posted 9 years ago #

    I would like to use WordPress but so far I haven't been able to get past the install. It keeps stopping at Step 2. I've triple-checked my password, dbname, etc. and it's all good.

    When the screen goes to Step 2, it appears that some of it is missing. In fact, when I view the source code for the returned page it stops right after the "Now we're going to create a few tables" sentence. There's NO more HTML at all - no /body tags, no /html tags.

    Looking at the source code, I see that the next PHP line is


    Why is it stopping there?
    Do I have to tell my ISP to do something special in order for the flush command to work?
    What is flush()?
    What am I doing wrong?

    Thanks for your patience in dealing with this humble newbie.


  2. moshu
    Posted 9 years ago #

  3. gehwokka
    Posted 9 years ago #

    Yes, I saw this. This poster goes into great detail - but mine is the problem NOT addressed. I should have mentioned this in the prior message - NO database tables are being created either! I checked this using PHPMyAdmin (which my ISP provides).

    As far as the posting goes, he says (paraphrasing) "if you created tables, great. All you have to do is change your password, but if your script did not create tables, then the install failed"

    I'm in the "install failed" category... Hence this posting...

    any ideas??

  4. wiseburn
    Posted 8 years ago #

    Hi, I had this problem too. no tables created. However, I'm installing WordPress on my server so I could debug it as well. The flush() just outputs the content that the server had published up to that point.

    I found my apache instance would terminate during step2 with a segmentation fault (likely trying to read [virtual] memory that isn't there).

    from /var/log/apache/error.log
    [Tue Oct 25 22:33:46 2005] [notice] child pid 7170 exit signal Segmentation fault (11)

    Further searches for this crash led to this.

    commenting out the following line in wp-db.php:
    $this->col_info[$i] = @mysql_fetch_field($this->result);

    fixed the problem.


Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.