Search results

  1. M

    LSWS - Mod_Rewrite QSD [Query String Discard]

    Does LiteSpeed support QSD [Query String Discard] in mod_rewrite? It looks like mod_rewrite with Apache 2.4 does support this although it doesn't seem to function with LSWS 5.1.X+.
  2. M

    Wordpress BackupBuddy and LiteSpeed

    We are on 4.2.2 - I will have the client try this.
  3. M

    Wordpress BackupBuddy and LiteSpeed

    We are constantly having people report BackupBuddy does not work with our services, something about there being no loopback. It works fine with Apache, just not LiteSpeed. It's unfortunate because a lot of our clients choose to use BackupBuddy.
  4. M

    LSWS 4.1.13 + Kayako Support Suite (and possibly other scripts)

    I'm surprised no response has been made to this thread, or the bug report I sent in... Hmm....
  5. M

    LSWS 4.1.13 + Kayako Support Suite (and possibly other scripts)

    Now here is 4.1.12 when submitting that exact same form: 4.1.12 - Apparently it's not rewriting the URL ============ 2012-07-15 04:14:17.003 [NOTICE] [69.243.173.1:35368-0#APVH_members.redacted.com] Content len: 16, Request line: 'POST /index.php?/Base/Search/Index HTTP/1.1' 2012-07-15...
  6. M

    LSWS 4.1.13 + Kayako Support Suite (and possibly other scripts)

    When LSWS 4.1.13 is running, none of the web forms in Kayako SupportSuite work - they all return error messages about not submitting a department ID, or not entering a search query, etc... When I roll back to 4.1.12 this issue disappears entirely and the site/script/forms work as expected. The...
  7. M

    [solved] Update via SSH/Shell without Prompts

    Nice indeed, that will make life easier :).
  8. M

    [solved] Update via SSH/Shell without Prompts

    I presume that requires LiteSpeed to have already downloaded the package. Let's say I wanted to upgrade to a debug build - short of running install.sh and answering all of the prompts by hitting "Q", "Yes", then enter a bunch of times - is there an alternative?
  9. M

    [solved] Update via SSH/Shell without Prompts

    I'm sure this is possible as the LiteSpeed Admin upgrades without asking you to re-accept the license, etc. Is there a script that can be run to update LiteSpeed to the latest version without all of the prompts of a normal install?
  10. M

    [Solved] Drastically Increased PHP RAM Usage after Rebuild, only via LiteSpeed

    I sorted it out, it's cPanel's "homeloader.so" Just in case anybody else come across this issue and can't sort it. Phew.
  11. M

    [Solved] Drastically Increased PHP RAM Usage after Rebuild, only via LiteSpeed

    Over the last couple of hours a lot of users are reporting memory exhaustion errors even with very light scripts that shouldn't be using more than a few megabytes. Without any other ideas/suggestions the only thing I can think to do is to roll back the PHP version to see if that resolves it...
  12. M

    [Solved] Drastically Increased PHP RAM Usage after Rebuild, only via LiteSpeed

    The message displayed in the browser is: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 261847360 bytes) in Unknown on line 0 When I run this via php 5.3 the issue does not occur, and if I run it via php 5.2 on the CLI the issue does not occur. This is only...
  13. M

    [Solved] Drastically Increased PHP RAM Usage after Rebuild, only via LiteSpeed

    Hello, This issue is quite odd and I've not yet been able to track down what is causing it. Users on a specific server running Drupal and one running Xenforo are reporting out of memory errors after recently rebuilding PHP 5.2.17 (to fix a GD Image issue). The configuration and options were...
  14. M

    LSWS Crashing (4.1.8 and 4.1.10)

    I'm seeing this on other servers as well, this happens and then the software restarts. It seems hit or miss as to whether LiteSpeed continues serving requests or not. On one server it does restart after a minute, on others it does not. 2012-01-22 16:06:11.013 [DEBUG] [MMAP] Release mapped...
  15. M

    LSWS Crashing (4.1.8 and 4.1.10)

    LSWS works fine for hours, days, or weeks and then it suddenly stops processing requests it seems. When I turned on full debug logging I see a TON of this right before it stops working: 2012-01-21 17:00:49.174 [DEBUG] [MMAP] Release mapped data at 0x2aaaad197000 2012-01-21 17:00:49.174 [DEBUG]...
  16. M

    [Not Resolved] LSWS 4.1 - Spinlock

    I haven't run into the issue in a while, but the issue only occurred when the maximum connections was set to something around 1k~9k. We have it set to something like 50k on each server which has totally prevented the issue from causing issues, not necessarily from occurring in the first place...
Top