You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there is specific reason you are manually running the service and not letting the entrypoint just run? The entrypoint.sh script also performs some configuration copy steps. If you are overriding the entrypoint on your container startup then this is more likely the problem. I don't see that SSL error in my own running instance.
@timnolte I do not overriding the entrypoint and do not change anything to the docker image。I am run the docker in centos 8 which cpu type is Ampere。Otherwise,in other environment,I run the openlitespeed binary which download from offical website,get the same error in aarch64。
Possiblely,it is a problem by openlitespeed itself,I find the same error in the forums。
Here is the link: https://forum.openlitespeed.org/threads/failed-to-init-ssl-session-id-cache.6002/
I guess in arm,it has some hidden issues to be solved
So, interesting. I'm no longer building OLS from source as I originally started doing, there wasn't arm64 binaries when I started. I started having issues with building from source and then the arm64 binaries became available and that is what I began using to build the Docker image.
Have you tried to use an older tagged image? I'm wondering if we can pinpoint if it started with a specific OLS release.
I run the command:
get the output :
the error log is below
after I delete SSL.lock, it still not work
The text was updated successfully, but these errors were encountered: