[Resolved] 4.0.16-> 4.0.17 Broke my wordpress blog

Discussion in 'Bug Reports' started by lugus, Oct 9, 2010.

  1. lugus

    lugus New Member

    Upgraded using cp to 4.0.17. When I went to login to my Wordpress blog it tried to download the file login.php rather than run it. Same with other admin php files. When I went back to 4.0.16 the problem went away.

    Any ideas?

    PHP 5.3.3 on Centos 5.x
    Last edited by a moderator: Oct 11, 2010
  2. NiteWave

    NiteWave Administrator

    looks a serious issue and hard to trace...

    what's your wordpress version? I upgraded to 4.017 on a wpmu 2.9.2 site, php 5.3.2, without problem.
  3. lugus

    lugus New Member

    Version 3 of Wordpress. Is there a chance I need to rebuild php after the upgrade? Have you tinkered with php memory or anything along those lines?
  4. NiteWave

    NiteWave Administrator

    4.0.17 select latest APC 3.1.4 instead of 3.1.3p1 when build PHP in admin console. so if you want to try APC 3.1.4, rebuild PHP in 4.0.17
  5. lugus

    lugus New Member

    I would if I thought it could help but I do not have APC compiled in my php at all and 4.0.16 works fine without it. Are you saying I have to have it now for 4.0.17?
  6. NiteWave

    NiteWave Administrator

    do you have other opcode cache like eAccelerator, XCache enabled?
    if none of them enabled, recommend you have one, absolutely it'll improve the php performance a lot.

    opcode cache is built as php extension, you can save/keep your current php binary, just build out apc.so, xcache.so, eaccelerator.so. and enable one(and only one) in php.ini.
  7. lugus

    lugus New Member

    I do not have any opcode cache compiled at the moment while I experiment. I will when this server goes into full use. I definitely do not want to add it now until I sort out why patch 4.0.17 is breaking the php.
  8. lugus

    lugus New Member

    Also I have just found if I try and compile php under 4.0.17 I receive:

    Fail to generate build script, please try to manually fix the error first.
    Failed to create manual install script: /usr/local/lsws/phpbuild/buildphp_manual_run.sh
  9. NiteWave

    NiteWave Administrator

    maybe a permission issue? please check
  10. lugus

    lugus New Member

    Produces:


    drwx------ 3 lsadm lsadm 4096 Oct 10 23:05 /usr/local/lsws/phpbuild/
  11. NiteWave

    NiteWave Administrator

    no problem of the permission. it's strange of your issue. Can you PM me the access to your server.
  12. lugus

    lugus New Member

    Message sent.
  13. lugus

    lugus New Member

    Problem solved. Thanks for the incredible support. Look forward to 4.1 in the future.
  14. IrPr

    IrPr New Member

    Would you please let me know whats the solution for PHP compile issue ?
  15. lugus

    lugus New Member

    Unfortunately there was an issue with the update that the Litespeed team repaired for me. In the past when I had a similar error using apache it was down to there being insufficient memory allocated to php.
  16. NiteWave

    NiteWave Administrator

    the issue was introduced by 4.0.17 new feature:mod_action support. its PHP Content-Type is "handler/fcgid-script". the new 4.0.17 build ignore "fcgid-script" and fixed the problem.

    lugus,
    can you give more info about your current problem? you can post here or through PM.
  17. lugus

    lugus New Member

    Sorry, I did not mean to imply I had an issue now. I should have said, the update originally caused a problem but was cured after work by the Litespeed team.
  18. Jos

    Jos New Member

    To experience wordpress "WSOD" (white screen of death) when upgrading isn't funny and very timeconsuming. You'll get no clues at all, nothing in the logs. Just a white screen telling nothing.

    I did an uprade to lsws 4.0.17 and instantly it killed my blog. Now it is up and running again, but it took a while before finding out what it was which caused the downtime. A bug, hacking or something else?

    In my case the lsws upgrade in cooperation with the debian server did corrupt the mysql database by giving it a mix of UTF8 and latin1 encodings which resulted in "funny characters". It wasn't easy to restore the database and reinstall everything. Now lsws 4.0.14 is installed together with php 5.2.13 and it seems to work very well.

    Finally after searching the net I learned the path how to get out of the mess. Valuable search terms are: "Turning MySQL data in latin1 to utf8 utf-8" (I cannot link to the actual site due to this is my 1st post in this forum).
    Last edited: Oct 24, 2010

Share This Page