HTTP server randomly closes, offers vague reason, refuses to elaborate further #1000
Labels
backlog candidate
Pull requests/issues that are candidates to be backlog items
community
Issues or PRs opened by an external contributor
Comments
|
Hi @grepwood! Welcome to the project! 🎉 Thanks for opening this issue! |
vepatel
added
the
backlog candidate
|
I'm facing the exact same issue for a couple of weeks now. What I managed to observe is the following by logging in the Nginx container's shell. (I interrupted the execution after more than 1 min.) / $ date && time curl -v 127.0.0.1:8000/stub_status && echo && echo && echo && date && time curl -v 127.0.0.1:9113/metrics; date
Thu May 8 21:03:24 UTC 2025
* Trying 127.0.0.1:8000...
* Connected to 127.0.0.1 (127.0.0.1) port 8000
* using HTTP/1.x
> GET /stub_status HTTP/1.1
> Host: 127.0.0.1:8000
> User-Agent: curl/8.12.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Server: nginx/1.26.3
< Date: Thu, 08 May 2025 21:03:24 GMT
< Content-Type: text/plain
< Content-Length: 107
< Connection: keep-alive
<
Active connections: 36
server accepts handled requests
313 313 14525
Reading: 0 Writing: 6 Waiting: 30
* Connection #0 to host 127.0.0.1 left intact
real 0m 0.00s
user 0m 0.00s
sys 0m 0.00s
Thu May 8 21:03:24 UTC 2025
* Trying 127.0.0.1:9113...
* Connected to 127.0.0.1 (127.0.0.1) port 9113
* using HTTP/1.x
> GET /metrics HTTP/1.1
> Host: 127.0.0.1:9113
> User-Agent: curl/8.12.1
> Accept: */*
>
* Request completely sent off
^C Command terminated by signal 2
real 1m 24.84s
user 0m 0.00s
sys 0m 0.00s
Thu May 8 21:04:49 UTC 2025Logs from the containers Events Configuration args:
- --nginx.scrape-uri=http://127.0.0.1:8000/stub_status
- --log.level=debug
image: nginx/nginx-prometheus-exporter:1.4.2
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
httpGet:
path: /metrics
port: 9113
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
name: nginx-prometheus-exporter
ports:
- containerPort: 9113
name: nginx-metrics
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /metrics
port: 9113
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 5
successThreshold: 1
timeoutSeconds: 3
resources:
limits:
memory: 64Mi
requests:
cpu: 100m
memory: 64Mi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: kube-api-access-4pnp9
readOnly: true
In the meanwhile, we lose the metrics in Grafana. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm running nginx-prometheus-exporter as a container sitting next to my nginx container. The container with NPE randomly dies for no reason. It just logs:
Despite the fact that NPE was started with
--log.level=debug, there's really nothing elaborated on why the HTTP server shut down.To reproduce
Steps to reproduce the behavior:
--log.level=debug.Expected behavior
NPE should explain why it shut down so that I actually fix it.
Your environment
The text was updated successfully, but these errors were encountered: