• OK, my system is WP V1.5 (31/01/2005) running on PHP V5.0.3, Apache V2.0.52 (PHP running as a module) & MySQL V4.19 runnig on a Win2K box (all patches applied). All this was freshly installed last week.

    After first changing:

    $step = $HTTP_GET_VARS[‘step’]; => $step = $_GET[‘step’];

    to get it to run, I hit major problems. Basically Apache crashes going to Step=1. I haven’t understood why. It keeps restarting and immediately crashing again repeatedly (if I was a remote user, I’d just see the page hang). Apache’s error log says nothing significant:

    [Tue Feb 01 19:33:12 2005] [notice] Parent: Created child process 1516
    [Tue Feb 01 19:33:13 2005] [notice] Child 1516: Child process is running
    [Tue Feb 01 19:33:13 2005] [notice] Child 1516: Acquired the start mutex.
    [Tue Feb 01 19:33:13 2005] [notice] Child 1516: Starting 250 worker threads.
    [Tue Feb 01 19:33:20 2005] [notice] Parent: child process exited with status 3221225477 -- Restarting.

    I am using a small MT test set of ~10kb, I can upload it for anyone who wants to test.

    I tried with Apache 1.3.33 (also using PHP 5 as a module) and it crashes Apache going to Step=2!!!

    It does start importing some entries (7 entries make it to the database). It also adds an unnamed (blank) new user – maybe this is the issue? The import data set contains 2 authors, but only 1 is shown in step 1 to map to a WP user…

    I suppose I can try installing PHP 4 and seeing if the issue is there. I have my database backed up so am happy to try various ideas. I don’t really code PHP, but i’m happy to hack and test if anyone has suggestions. It may be an issue with MySQL (it was unstable with V1.2.2 for me).

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter iandol

    (@iandol)

    I tried setting PHP5 up as a CGI under Apache 2 – and the crash still occurs (though this time in php-cgi.exe). I am betting there is some instability with MySQL 4.1.9 – but installing that is more of a pain, can two installs run off the same database?

    Thread Starter iandol

    (@iandol)

    Updates: OK, part of the problem is that WP doesn’t like using non alpha characters in the path (I’ll check mosquito and see if its known), so if I have:

    https://ip.address.here/-/

    As my root for the WP install, this causes a crash before getting to step 2. I made another install at:

    https://ip.address.here/bs/

    This time I get this error for the authors on step 1:

    Warning: Attempt to assign property of non-object in C:wwwbswp-includeswp-db.php on line 241

    Fatal error: Call to a member function query() on a non-object in C:wwwbswp-includeswp-db.php on line 244

    There are ONLY two authors in the MT file, and their names map to already existing users in WP.

    If I ignore that and click enter in one of the text fields, it starts to import a few entries, and then crashes Apache. This error is shown:

    Warning: Invalid argument supplied for foreach() in C:\www\brainsource\wp-admin\import-mt.php on line 130

    Warning: Invalid argument supplied for foreach() in C:\www\brainsource\wp-admin\import-mt.php on line 135

    If I keep trying to reload, it keeps crashing after adding just a few more items, with more errors such as:

    Warning: Attempt to assign property of non-object in C:wwwbrainsourcewp-includeswp-db.php on line 177
    Post imported successfully...
    Processing post... Temporal Evolution of Stereoscopic Processing...
    Warning: Unknown list entry type in request shutdown (2358529) in C:wwwbrainsourcewp-includeswp-db.php on line 142

    WordPress database error: [Duplicate entry '' for key 2]
    INSERT INTO wp_users (user_level, user_login, user_pass, user_nickname) VALUES ('1', '', 'MD5 Hash was here!!!', '')

    and

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0' at line 1]
    0

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND category_id = 27' at line 1]
    SELECT * FROM wp_post2cat WHERE post_id = AND category_id = 27

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 27)' at line 4]
    INSERT INTO wp_post2cat (post_id, category_id) VALUES (, 27)

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND category_id = 28' at line 1]
    SELECT * FROM wp_post2cat WHERE post_id = AND category_id = 28

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 28)' at line 4]
    INSERT INTO wp_post2cat (post_id, category_id) VALUES (, 28)

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND category_id = 27' at line 1]
    SELECT * FROM wp_post2cat WHERE post_id = AND category_id = 27

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 27)' at line 4]
    INSERT INTO wp_post2cat (post_id, category_id) VALUES (, 27)

    To reiterate: I run phpMyAdmin, Blog:CMS and WikkaWiki on this machine with NO problems – they NEVER crash either MySQL or Apache. Now this may not entirely be WP’s fault, but there is some specific instability that WP manages to evoke in Apache/MySQL…

    weefselkweekje

    (@weefselkweekje)

    I had the same problem. I had to import the mt data in a dummy install on a server that uses php4, and then export/import the tables to the php5 server using phpMyAdmin. It worked, but there definately is a problem with php5 and the MT import script…

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Lots of Problems with MT-Import’ is closed to new replies.