litespeedtech / lsws-docker-env

LiteSpeed Enterprise Docker Environment

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[ERROR] litespeed is not running.

ivmm opened this issue · comments

$ docker logs lsws-docker-env_litespeed_1

--2020-02-09 10:53:17--  http://license.litespeedtech.com/reseller/trial.key
Resolving license.litespeedtech.com (license.litespeedtech.com)... 34.231.236.27
Connecting to license.litespeedtech.com (license.litespeedtech.com)|34.231.236.27|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 256 [application/octet-stream]
Saving to: '/usr/local/lsws/conf/trial.key'

     0K                                                       100% 21.0M=0s

2020-02-09 10:53:18 (21.0 MB/s) - '/usr/local/lsws/conf/trial.key' saved [256/256]

[ERROR] litespeed is not running.
2020-02-09 10:53:19.397070 [NOTICE] Memory size is: 8167996KB.
2020-02-09 10:53:19.707399 [NOTICE] [OK] Updated license key has been created at /usr/local/lsws/conf/trial.key.
[OK] litespeed: pid=35.
litespeed is running with PID 35.
--2020-02-09 10:53:23--  http://license.litespeedtech.com/reseller/trial.key
Resolving license.litespeedtech.com (license.litespeedtech.com)... 34.231.236.27
Connecting to license.litespeedtech.com (license.litespeedtech.com)|34.231.236.27|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 256 [application/octet-stream]
Saving to: '/usr/local/lsws/conf/trial.key'

     0K                                                       100% 29.0M=0s

2020-02-09 10:53:23 (29.0 MB/s) - '/usr/local/lsws/conf/trial.key' saved [256/256]

[ERROR] litespeed is not running.
2020-02-09 10:53:24.988730 [NOTICE] Memory size is: 8167996KB.
2020-02-09 10:53:25.290836 [NOTICE] [OK] Updated license key has been created at /usr/local/lsws/conf/trial.key.
[OK] litespeed: pid=35.
litespeed is running with PID 35.

Cannot start LSWS via docker compose.

Maybe my test machine has too much memory? But the application of the trail key should not be unable to start because of too much memory.

commented

Yeah, thanks for the fast testing. Actually lsws start success and finished the job then exit container. So I am looking solutions for lsws running in daemon/foreground mode to avoid container exit 0.

commented

Should works now. Feel free to let me know if any issues.