Search results

  1. N

    [Resolved] crashes - segfault and some more jargon

    so pcre's version is 8.32, matches with document: http://php.net/manual/en/pcre.installation.php 5.5.0 / 5.4.14 / 5.3.24 8.32 since your php is 5.3.29, so the bundled pcre version is 8.32 php 5.2.19 to 5.3.28, its version is 8.31 starting from php 5.5.10, the bundled version is 8.34...
  2. N

    unexpected signal=11, a core file is created

    this is an old thread. for now, the latest version is 4.2.14. please force re-install 4.2.14 also, install gdb if you have not: #yum install gdb then you may receive email with more detail info regarding the error. send the information here.
  3. N

    [Resolved] crashes - segfault and some more jargon

    it's memory address, no much valuable info in it. do you still have the problem ? A staff mentioned me your post not answered yet, so I came back to follow up. we received a similar report recently, the info is insufficient so not sure how to reply but we recommended...
  4. N

    A setenv question

    >SetEnvIfNoCase ^arg$ .+ allowed=1 not sure what "arg" here mean, an http request header? if so, try following rewrite rules: <Location /> RewriteEngine on RewriteCond %{HTTP:arg} ^$ RewriteCond %{REMOTE_ADDR} !^127\.0\.0\.1$ RewriteRule (.*) - [F,L] </Location> are lsws the latest 4.2.14?
  5. N

    white/blank page with charset variables

    can you PM the link of the 2 websites ? I'd take a more closer check and testing. probably a html encoding issue.
  6. N

    Cached memory

    the "cached memory" is managed by linux automatically 12GB mean only 12GB are used to cache file data by linux at a specific time point. if you serve a video or download site, when traffic is high, you'll see the "cached" increasing automatically.
  7. N

    litespeed + apache vs just litespeed?

    usually don't need run apache and litespeed in parallel, that's just slow down all the things and not necessary at all. but there may be rare case only apache can function well and litespeed not cover it yet. need review the details case by case. and litespeed is in active development, it may...
  8. N

    Slow Scheduled Cron Job

    >It runs slowly on it's own but if I do it it runs really quickly. when you run it manually on command line, it runs as root. when it's scheduled to run by cron through vBulletin, it should run as a user or nobody ? non-root user may be restricted by limited resources, for example cloudlinux is...
  9. N

    Admin console giving (110) Connection timed out Error

    should local access is ok. although you said >The admin console is not loading the server.We have tried disabling csf. most likely still a firewall issue. access to :82 outside the server is blocked by firewall on the server(iptables) or at the server's upper link --- gate etc. if it's gateway...
  10. N

    Litespeed - Accept-Encoding: gzip issue - FB Open graph garbled content

    please force re-install 4.2.14 see if this issue still exists. We received a facebook related bug report and has fixed it about 2 days ago in latest 4.2.14 build. if the issue still there, we need more technical detail so that we can reproduce and fix it.
  11. N

    Slow Scheduled Cron Job

    not sure what's the reason, and not heard of similar issue before. anyway, please try lsws web admin->General->External Application Abort:No Abort to see if any difference
  12. N

    how to edit page 404 not found for all users

    for example: in apache's httpd.conf, put ErrorDocument 404 "Sorry, File Not Found" just follow apache's document
  13. N

    Admin console giving (110) Connection timed out Error

    can you access :82 when ssh to the server ? 1. ssh to the server 2. try #curl -I 127.0.0.1:82 the admin console log is under /usr/local/lsws/admin/logs
  14. N

    [Resolved] crashes - segfault and some more jargon

    from the first post of this thread: you can know lsphp-5.4.31 is used.
  15. N

    [Resolved] IP Apache vs Litespeed

    So the default cache expire time must be set very long :)
  16. N

    Litespeed cPanel account suspension

    please force re-install 4.2.14, see if this issue still exists. #/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.14
  17. N

    Eror port 80 ready in use

    maybe other web server(apache, nginx etc) are running, they are listening to port 80 as well. the solution is to stop apache or nginx before start up litespeed. run #netstat -ntlp to check which processes listen to which ports.
  18. N

    [Resolved]invalid path - /usr/local/lsws/fcgi-bin/lsphp55

    these errors can be safely ignored, should not be the reason of restart. to eliminate the errors regarding php55, just do ln -s /usr/local/lsws/fcgi-bin/lsphp5 /usr/local/lsws/fcgi-bin/lsphp55
  19. N

    [Resolved]/home/mysite/public_html/404.shtml and 403.shtml

    does both server have same lsphp5 ? check and compare phpinfo.php on both sides.
Top