Search results

Freebsd does not get the same level of attentions & cares as Linux.:p

Just download again and update your installation, bundled OpenSSL lib has been updated to 1.0.1f for freebsd6 packages.

Please try updated 4.2.7 . The previous build works for me. Maybe need to enable modsec debug logging to find out what happened with that rule.

It is highly likely that .shtml was assigned with "text/html" MIME type some where, override the application/x-httpd-shtml MIME type set in the mime.properties. so they are just served as regular static file.

By default it is on for native LSWS configuration, so SSI should work with a default installation. If SSI is disabled, you will get log message like in the error.log at INFO level. Are you using latest version 4.2.7?

turn on debug logging and check the log. It requires Apache style configuration to turn it on.

how about just use regular pattern match? Make sure the GeoIP setup is working properly, and GEOIP_XXXX variables appear in a phpinfo() page.

Please force reinstall 4.2.7 see if it works.

Not the CGI memory limit, the memory limit for the PHP external app. http://www.litespeedtech.com/docs/webserver/config/extapps#memSoftLimit Also take opcode cache memory into consideration against the memory limit. You can let PHP execute "ulimit -a" to find out the current limit applied to...

OK, looks like we got it. It failed to mmap() 2MB for the DNS lib. Maybe the memory limit for lsphp external app was set too low, or the LVE memory limit was too low. raise the memory limit should fix it.

Can you capture one strace with success DNS lookup, one strace with failed DNS lookup. Do a comparison see when they start to show the difference.

I read those strace logs, I think it might be that /etc/resolv.conf sometimes for some reason is not available when lsphp process was started, all requests served by that lsphp process will not query DNS server, only check against /etc/hosts . If lsphp process can read /etc/resolv.conf when...

Check error_log and stderr.log for reason of 503 errors.

I wonder if CloudLinux LVE limit causes interim DNS lookup failure. Increase LVE limit see if the problem goes away. It is better to avoid the DNS lookup if the DB has a fixed domain name, set it in the /etc/hosts .

it should be.

If there was no log entry about PID > 304809 and all lshttpd processes are dead, it means some process killed all lshttpd with signal 9. You need to find out what software package does that, some anti-hacking script may do that. If there are still lshttpd process alive, it is another story, need...

add <IfModule LiteSpeed> ... </IfModule> around it.

However, in the mean time, might work.

We add that to our LSWS 5.0 to-do list.

Looks normal, need to look for log entries about PID 304809 that's the current http main server process. We may need to full log for analysis, the partial log does not help. please PM or send to bug@litespeed...