-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.25.0 crashes at backend reload maybe due to recent OpenResty changes #4311
Comments
@tailtwo you are right. This issue is related to missing instructions in your PowerEdge R805 (eleven years since the release date) We have no plans to support old hardware (or the resources to start adding these exceptions and new images). For that reason:
|
@aledbf I get the same kind of crashes. Are you saying our CPUs are too old?
|
@aledbf OpenResty itself now officially supports old hardware by having two variants of each image: |
@towolf yes, it seems the same issue. The release date of E5320 was on Nov 14, 2006 |
You should build a custom version to remove the sse42 version. |
@aledbf don't we exclude a lot of architectures then? What about ARM and Rpi and so on and so forth? |
@towolf This doesnt really affect ARM as SSE is a x86 specific extension. I just hit this myself for Intel E5345, and it took me a while to figure out how to build a working version, so for anyone else needing it this is what I did: 9fdae37 @aledbf It would be really great if there could be an official 'amd64-legacy' build for those of us who are stuck on older hardware. |
I just ran into this on my Dell R815 server. Sure, it's old, but it's also 48 real cores w/ 256 GB and perfectly capable of running modern workloads. 👍 |
Maybe this issue can be fixed if this PR openresty/luajit2#75 is merged |
Even if this issue is closed, Can you suggest a file to insert something like grep sse4_2 /proc/cpuinfo || echo "ERROR: CPU is not supporting sse-4.2" Thanks Note for the record it is also affecting microk8s v1.16.0 with CPU "AMD Athlon(tm) 64 X2 Dual Core Processor 4600+" Relate-to: openresty/luajit2#20 |
I'm running microk8s on a Dell PowerEdge 1900, using Intel Xeon E3510s I reverted back to the 0.24.1 release image. I want to keep an eye on this. |
Since the latest release (0.27.0) and the switch from openresty back to nginx, you can now run nginx-ingress without SSE42 like before. |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): yes
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): illegal opcode resty
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.25.0
Kubernetes version (use
kubectl version
):Environment:
uname -a
): Linux server1 4.19.0-5-amd64 Basic structure #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/LinuxWhat happened:
Upgrading from Nginx-ingress 0.24.1 to 0.25.0 make the Nginx controller crash on one specific server of my Kubernetes cluster. Other servers have a different hardware/OS.
System logs :
What you expected to happen:
Nginx controller init without issues.
How to reproduce it (as minimally and precisely as possible):
Upgrade from 0.24.1 to 0.25.0 on a specific server hardware.
Anything else we need to know:
The culpit may be Openresty. This issue seems to fit this case : openresty/docker-openresty#39
The text was updated successfully, but these errors were encountered: