Search results

Hey! So sorry for the long delay to reply here! Just want to let you know that it is finally working. I don't know if I did something wrong before or was the version I was using (now I'm using 1.5.7), but I can now see which site is reaching max children limit :) root@ip-95-216-157-xxx:/srv#...

Hmm, I tried that with no luck. What OLS version are you using? I have loaded some extensions twice, so they can produce a PHP Warning, and all warnings are going to /usr/local/lsws/logs/stderr.log instead of /tmp/stderr1.log :/ I'm using LiteSpeed/1.5.6 Open

Yeah, I know. I was trying to simulate the "Max children" error. :) But believe me, a lot of our clients DEMAND to limit the php process to 2~4, so they can put like 50 wordpress sites on a 1gb-ram server haha

Hi David. Great suggestion as always :) Someday I will write a compact guide about all the things we can accomplish with env variables and .htaccess ENV too But it doesn't seem to be working as expected: root@ip-95-216-157-207:/srv/zlx.com.br/log/php# ls -lah /tmp/stderr.log -rw-r--r-- 1 zlx...

I understand that. But I'm asking you to see more a scenario where we have 2000 managed cloud servers, with 1 to 400 sites in each. Most of those servers are running nginx with php-fpm. On those servers, I can easily spot any problem checking the php-fpm.log, since it clearly say which pool is...

Hi guys :) I noticed OLS is logging every "Reached max children process" kind of error on stderr.log instead of the vhost's own error.log In another post (https://forum.openlitespeed.org/threads/custom-error-log-for-vhost-not-working.2620/) someone said that stderr always go to stderr.log " due...

Ok, setting the initTimeout higher indeed seems to fix the problem most of the time. I'm still getting one or another deadlock, but the script is running until the end. My problem now was caused by nginx, since we are using nginx in front of OLS because of sub_filter module. I adjusted...

Right, I only have the VHost PHP extprocessor created. I removed the server level php I'll install OLS on a new server and keep all default values, changing only initTimout to test the provided scripts. I will keep you updated if I find anything else. Thanks guys :)

I used the code you provided :) Maybe some other configuration is wrong? extprocessor xxxxxxxxxxxxxx { type lsapi address UDS://srv/xxxxxxxxxxxxxx/etc/php/lsws.sock maxConns 2 env PHP_LSAPI_CHILDREN=2 initTimeout...

Hi David! Glad to see you here taking care of this problem :) I see you "fixed" the problem in your test setting initTimeout to 600 and I thoght to give it a try, but when I checked my config, my timeout was on 3000 and the deadlock still occurs. I spent the last few hours trying various...

By the way, since this seems to be a default wordpress cookie value, shouldn't it be added to LiteSpeed Cache .htaccess rules without the user needing to edit it? It would be more user-friendly for sure

Oh, I thought it would work out of the box. I will update my client. Thanks! ;)

I removed the cache so you can test. I'm using wordpress own password protected function, so I really don't know how it is done. I think it is setting a cookie: "wp-postpass_9abXXXXXXX"

Hi guys, how are you? :) I'm trying to password protect a page on a new wordpress install with no other plugins, only LSCache, but the page asking for the password is being cached and served instead of showing the real page after I enter the password. You can check the test page here...

Hi I'm having the same problem with lots of clients too At least two wordpress-api sites are broken when using OLS because of dead locks. If some script takes too long (a few seconds, actually) to return any data, we get a lot of deadlocks on log and eventually everything dies. I've searched...

Wow! You are a genius :D Thank you very much, David :) rewrite { enable 1 autoLoadHtaccess 1 RewriteCond %{HTTPS} on RewriteRule ^(.*) $1 [E=SERVER_PORT:443] RewriteCond %{HTTPS} off RewriteRule ^(.*) $1 [E=SERVER_PORT:80] } It worked perfectly =)

Hello, We are using OLS behind a proxy on several servers and almost everything works out of the box. However, some applications tries to redirect users after some actions using the _SERVER["SERVER_PORT"] variable. Since we are running OLS on localhost:9443 por HTTPS and localhost:8088 for HTTP...

2019-08-01 17:06:30.147206 [INFO] RewriteFile [/srv/xxxxxxxxx/www/dir1/.htaccess] parsed, return 0. 2019-08-01 17:06:30.147260 [INFO] RewriteBase [/dir1/dir2/] parsed, set to HttpContext 0x2118410. 2019-08-01 17:06:30.147283 [INFO] RewriteFile [/srv/xxxxxxxxx/www/dir1/dir2/.htaccess] parsed...

This is the .htaccess content on dir1: RewriteBase /dir1/ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ info.php [L,QSA] And this is the .htaccess content on dir2: RewriteBase /dir1/dir2/ RewriteCond %{REQUEST_FILENAME} !-f RewriteCond...

Hi, sorry the delay, was out of office already. =/ So, I disabled the previous context and enable the log to debug as you asked. The context of /dir2/ wasnt created. When I requested something from dir1/dir2, only dir1 context is created: 2019-08-01 10:51:17.437870 [NOTICE] [Child: 15211]...