Search results

I am not using OLS admin GUI at https://myserver:7080 In CSF, I don't open that port either. However, when accessing https://myserver:7080, it's still showing the admin login screen. How can I block completely that GUI? Thanks.

Interesting, I didn't notice this. Any ETA for the stable release?

It looks like this issue is only happening with PHP 8.3. I downgraded to PHP 8.2 for a while, no more warning. Then in a new server, I have PHP 8.3, the same warning appears. Something is not fully compatible between OLS and PHP 8.3?

I still don't have any solution for it yet.

Borgbackup and Borgmatic

I don't know how to customize the socket name, but I do differently. 1. Customize the OLS log, insert the PID. 2. Using lsof to log all the socket processes. 3. When I get warning with socket ID, I search in the log file, get a bunch of PIDs. 4. With those PIDs and the timestamp from the...

What are you wondering about OLS and DirectAdmin? Are you looking for a shared host with OLS, or a dedicated server / VPS?

This happens again. How to customize the socket name like you mentioned, please?

And how to customize that way, please?

Here is log with timestamps around the time I checked Sat May 25 23:27:01 +07 2024 restart, LSWS running: 1 Sat May 25 23:28:58 +07 2024 stop, LSWS running: 1 Sat May 25 23:29:25 +07 2024 start, LSWS running: 0 Sat May 25 23:31:01 +07 2024 start, LSWS running: 0 Sat May 25 23:32:23 +07 2024...

In /usr/local/lsws/conf/httpd-cgirlimit.conf, I have cgroups 2 by default which is disabled completely. Have no idea why there is still cgroups logs there.

OLS on one server was crashed. At [27/May/2024:06:59:10 +0700], web server with pid=1673370 received unexpected signal=11, a core file is created. A new instance of web server will be started automatically! Please forward the following debug information to bug@litespeedtech.com. Environment...

That's nothing related to OLS. Migrating from MariaDB to MySQL, you first need to check the compatibility. Recent versions of MariaDB and MySQL have different functions, which might lead to problems with your websites.

Now it happens again. But full stop didn't help. [root@servername ~]# /usr/local/lsws/bin/lswsctrl stop [ERROR] litespeed is not running. [root@servername ~]# systemctl stop lsws [root@servername ~]# systemctl status lsws × litespeed.service - The OpenLiteSpeed HTTP Server Loaded: loaded...

Yes, it's working fine.

Sometimes I got warnings from LFD like Time: Sat May 25 13:57:30 2024 +0700 File: /tmp/lshttpd/lsphp83.sock.11490.pid Reason: Script, starts with #! Owner: apache:apache (989:989) Action: No action taken I tried to locate pid 11490 with ps aux, but no process with that ID. In...

There is no lsrestat.log. I tried to search in other log files, in /var/log/messages, there are 2 lines happening at the same time I received notification May 13 21:45:01 trondheim lswsctrl[1049171]: [OK] Send SIGUSR1 to 1047094 May 13 21:51:01 trondheim lswsctrl[1050184]: [OK] Send SIGUSR1 to...

Will try next time if it's happening again. But what is the reason for that happening?

I see this issue many times recently. The OLS service has been running for a while, no change in its config. Suddenly, got a warning: litespeed.service is not active, cannot reload. systemctl status confirm its status is inactive. # systemctl status lsws × litespeed.service - The OpenLiteSpeed...

With DA servers, the GUI is read-only. It would be very helpful if you can update the directives here. Thank you :)