-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.3.0
-
None
-
None
-
None
-
ZStream
-
rhel-sst-cs-stacks
-
ssg_core_services
-
22
-
None
-
False
-
-
None
-
None
-
Approved Blocker
-
Pass
-
Needed
-
RegressionOnly
-
None
What were you trying to do that didn't work?
I have an application that was using ubi8/nginx-122 as the base image, it was working.
I then tried to move up to ubi9/nginx-122, but the nginx process can't start, it seg faults.
I was able to isolate the directive(s) that causes the problem. If I have proxy_ssl_certificate and proxy_ssl_certificate_key set in my location block, the seg fault happens
(same cert and key also set as ssl_certificate and ssl_certificate_key for the entire server and this doesn't cause the problem, so this suggests the cert is valid)
Please provide the package NVR for which bug is seen:
registry.access.redhat.com/ubi9/nginx-122
How reproducible:
Steps to reproduce
- Add proxy_ssl_certificate and proxy_ssl_certificate_key to a location block in nginx config
- Start the container
Expected results
The container starts
Actual results
The container does not start due to nginx process seg fault
- account is impacted by
-
RHEL-37683 Segfault when setting proxy_ssl_certificate and proxy_ssl_certificate_key
-
- Closed
-
- clones
-
RHEL-32650 Nginx seg faults when proxy_ssl_certificate is set
-
- Closed
-
- links to
-
RHBA-2024:137515 nginx:1.24 module bug fix