Cgroups checking

[hp2]

Following this KB, I don't have cgroups configured

# ls /sys/fs/cgroup/cgroup.controllers
ls: cannot access '/sys/fs/cgroup/cgroup.controllers': No such file or directory

# cat /sys/fs/cgroup/cgroup.subtree_control
cat: /sys/fs/cgroup/cgroup.subtree_control: No such file or directory

However, it's enabled in httpd-cgirlimit.conf. I am using CloudLinux already. Do I need to keep cgroups enabled? Or can I disable it?
Thanks.

 

[Cold-Egg]

If you have cloudlinux already, cgroup is not needed.

 

[hp2]

In httpd-cgirlimit.conf, I set cgroups 2 which is disabled. However, in stderr.log, full of this kind of log:

2024-03-12 21:52:23.806729 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1039.slice/litespeed-exec.scope/cgroup.procs, pid: 3307480
2024-03-12 21:53:06.256329 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1026.slice/litespeed-exec.scope/cgroup.procs, pid: 3307663
2024-03-12 21:53:20.888879 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1027.slice/litespeed-exec.scope/cgroup.procs, pid: 3307685

Why do those log appear in stderr.log file?

 

[Cold-Egg]

May I know if you have stopped and removed those system files?

 

[hp2]

No, I never touch those files. Not sure if it's related, but this OLS is installed with DirectAdmin.

 

[Cold-Egg]

I see. If the log keeps showing like that, please contact DA support to get more information.

 

[Jos Klever]

It took me some hours to get this investigated by DirectAdmin, but they found out that is was a bug in OpenLiteSpeed. The fix will be included in OLS 1.8.5, that I've just successfully tested.

 

[hp2]

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: 456729
2026-02-10 11:21:13.099288 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1003.slice/litespeed-exec.scope/cgroup.procs, pid: 456730
2026-02-10 11:21:13.100510 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1026.slice/litespeed-exec.scope/cgroup.procs, pid: 456734

 

[Cold-Egg]

Hi,
Could you try /usr/local/lsws/admin/misc/lsup.sh to make sure you are using the latest build version?

 

[hp2]

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)

 

[Cold-Egg]

1.8.5 has been repacked before, so if you haven't, could you try lsup again?

 

[hp2]

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/op...d/v1.8.5/openlitespeed-1.8.5-x86_64-linux.tgz. Here is the checksum.

# md5sum openlitespeed-1.8.5-x86_64-linux.tgz
a2c8d7a12de86888dc3cf6c3e1f48d6b  openlitespeed-1.8.5-x86_64-linux.tgz

Right after installing, I got this in stderr.log

2026-02-10 16:35:00.765434 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1024.slice/litespeed-exec.scope/cgroup.procs, pid: 506358
2026-02-10 16:35:09.420480 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1028.slice/litespeed-exec.scope/cgroup.procs, pid: 506393
2026-02-10 16:35:13.489985 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1022.slice/litespeed-exec.scope/cgroup.procs, pid: 506419
2026-02-10 16:35:29.210703 Cgroups returning success file: /sys/fs/cgroup/systemd/user.slice/user-1019.slice/litespeed-exec.scope/cgroup.procs, pid: 506435