• I just installed WordPress 2.1 on RHEL4 (Red Hat Enterprise Linux ES release 4 (Nahant Update 3)) (redhat-release-4ES-4.1).

    When I enter the admin section and click on “Manage” and then the link for “Categories”, I get nothing. Depending on what browser I’m using it tries to download the php file, or tells me there’s an error.

    So, I got to the web server log and I see this:

    *** glibc detected *** free(): invalid next size (fast): 0x0a14e470 ***
    [Fri Feb 16 15:25:09 2007] [notice] child pid 20994 exit signal Aborted (6)

    From which I infer that the Apache mod that handles PHP files is being aborted entirely, resulting in the php file not being processed and Apache just trying to serve it up as a file with a php extension.

    So, is this some incompatibility with the version of PHP I’m running, or glibc? I would assume that something in the /wp-admin/categories.php file is blowing up something in my Apache module or in glibc resulting in the process meeting an unexpected and unsavory end.

    I’m going to try looking for updates to see if this fixes the problem, but surely someone else has encountered this already?

    Thanks in advance…

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    What version of PHP are you running? Might try upgrading it.

    Might also try checking the version of glibc installed. I know that RHEL has had a seeming lot of glibc related issues. Maybe there’s an update or 8 there as well.

    Thread Starter naql

    (@naql)

    Well, I’ve been running the up2date tool on anything I can think that might be related: mysql, httpd, php… here is the version of php I have:

    PHP 4.3.9 (cgi) (built: Nov  2 2006 16:39:38)
    Copyright (c) 1997-2004 The PHP Group
    Zend Engine v1.3.0, Copyright (c) 1998-2004 Zend Technologies
    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Ugh. I would highly recommend upgrading to PHP 5. I know a lot of people don’t like it, but I am not them. 🙂

    Your call though. It may or may not help you. It’s a sort of shotgun debugging approach, but with glibc issues, that’s often all you can do.

    WordPress runs fine under PHP 5, no worries there.

    Thread Starter naql

    (@naql)

    Well, I think I would have to do that independently of the RedHat up2date tool, so that will require some research this weekend.

    I don’t know if this is significant or not, but if I go to the command line and simply type in “php categories.php” it ouputs some html headers, no html file that I can see, but it doesn’t seem to crater out.

    I have the exact same problem. Everything works in WP admin except manage categories.

    I get the following error in my log file:
    *** glibc detected *** corrupted double-linked list: 0x0a30aae8 ***

    Ive searched a bit on google, and some people pointed it towards zend optimizer, which i disable, but the problem still persists.

    Im running apache 2.0.52 on CentOS and PHP 4.3.9 with Zend Optimizer v3.0.1 and WP 2.1

    Upgrading to PHP 5 is not an option.

    Would very much like to hear input on this. Thanks in advance.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    PHP 4.3.9 is over 2 years old and known to have security flaws. Why would you stick with outdated and buggy software? I mean, even the 4.x series is up to 4.4.5 or so by now.

    And people wonder how their sites get hacked…

    Well, upgrading PHP didn’t fix the problem. I upgraded to PHP 5.1.6, and the “Categories” page is still a completely white page. No sign of life…

    And BTW – RedHat Enterprise Linux (and CentOS and other derivates) do patch their packages when bugs and security holes are reported.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Problem with Categories Admin WP 2.1’ is closed to new replies.