Recent content by hp2

Thank you. The new build seems fixing the issue. I have another issue, can you take a look, please?

I have multiple lines like this in /var/log/openlitespeed/stderr.log 2026-02-12 09:23:39.214 [STDERR] 2026-02-12 09:23:39.214630 lscgid (784228): failed to change stderr log to: /var/log/openlitespeed/stderr.log 2026-02-12 09:23:49.201 [STDERR] 2026-02-12 09:23:49.050953 lscgid (784412): failed...

I am using on DirectAdmin server, so I am using DA for updating. Just ran it again, and see DA downloads from https://github.com/litespeedtech/openlitespeed/releases/download/v1.8.5/openlitespeed-1.8.5-x86_64-linux.tgz. Here is the checksum. # md5sum openlitespeed-1.8.5-x86_64-linux.tgz...

Yes, it's 1.8.5 # /usr/local/lsws/bin/lshttpd -v LiteSpeed/1.8.5 Open (BUILD built: Thu Jan 8 15:41:40 UTC 2026) module versions: lsquic 4.4.1 modgzip 1.1 cache 1.66 mod_security 1.4 (with libmodsecurity v3.0.14)

I still see this kind of log with a new DA server and OLS 1.8.5. Double checked, cgroups is 2 in httpd-cgirlimit.conf by default. Any idea? 2026-02-10 11:21:13.095835 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1027.slice/litespeed-exec.scope/cgroup.procs, pid...

Nothing appears in error_log and stderr.log. In the syslog, comparing the date time, there are something like this only Dec 8 17:33:01 servername systemd[1]: Reloading The OpenLiteSpeed HTTP Server... Dec 8 17:33:01 servername lswsctrl[484478]: [OK] Send SIGUSR1 to 480341 Dec 8 17:33:04...

OLS status shows: # systemctl status lsws ● openlitespeed.service - The OpenLiteSpeed HTTP Server Loaded: loaded (/etc/systemd/system/openlitespeed.service; enabled; preset: disabled) Active: active (running) since Thu 2025-12-04 16:26:25 +07; 3min 46s ago Process: 898882...

I haven't got Almalinux 10 yet, so I am not sure, but with CloudLinux 8 and 9, I also get [ERROR] litespeed is not running. randomly, even the OLS service is still ON / ready. Again, only randomly. The cron is working most of the time. And I am only using reload, not restart in my cron. It would...

There was no OOM at that time. And when it happened, I tried systemctl restart lsws, but it didn't work either. Had to kill manually.

The only errors are: 2025-06-25 00:04:13.679325 [ERROR] [3929394] HttpListener::start(): Can't listen at address adminListener: Address already in use! 2025-06-25 00:04:13.679420 [ERROR] [3929394] HttpServer::addListener(adminListener) failed to create new listener 2025-06-25 00:04:13.679426...

Suddenly, the OLS 1.8.3 on my CloudLinux 9 was dead. In stderr.log, there are these lines 2025-06-25 00:04:01.202 [STDERR] 2025-06-25 00:04:01.140229 Cgid: Child process with pid: 3927493 was killed by signal: 1, core dump: 0 2025-06-25 00:04:01.492 [STDERR] 2025-06-25 00:04:01.492104 Cgid...

@Cold-Egg any thought about these bugs?

Thanks for sharing. Have you got a chance to check again with the latest version? Currently it's 6.5.4 while version 5.7 was released from October 2023.

I wonder if you can show more details why it's faulty and uses wrong cache vary?

I am on a DirectAdmin server, CloudLinux 9 with OLS 1.8.2, PHP Selector. In /usr/local/lsws/conf/httpd-phplimits.conf, I have added env LSAPI_ALLOW_CORE_DUMP=1 However, when testing with kill -SIGSEGV 1527388 The PID 1527388 was killed, but no core dump file was created. How...