Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

ingress: uninitialized "proxy_upstream_name" variable while logging request #1801

Closed
kayrus opened this issue Sep 29, 2016 · 1 comment · Fixed by #1802
Closed

ingress: uninitialized "proxy_upstream_name" variable while logging request #1801

kayrus opened this issue Sep 29, 2016 · 1 comment · Fixed by #1802

Comments

@kayrus
Copy link
Contributor

kayrus commented Sep 29, 2016 •
edited
Loading

I tried the latest nginx.tmpl with the #1751 change and get lots of error logs in nginx pod:

2016/09/29 14:49:36 [warn] 24#24: *454 using uninitialized "proxy_upstream_name" variable while logging request, client: 1.2.3.4, server: example.com, request: "HEAD / HTTP/1.0", host: "example.com"

these logs relate to newrelic:

1.2.3.4 example.com [1.2.3.4] - - [29/Sep/2016:14:54:58 +0000] "HEAD / HTTP/1.0" 301 0 "-" "NewRelicPinger/1.0 (767762)" 219 0.000 [] - - - -
@aledbf aledbf mentioned this issue Sep 29, 2016
Merged
@aledbf
Copy link
Contributor

aledbf commented Sep 29, 2016

@kayrus please check if #1802 removes the warning

k8s-github-robot pushed a commit that referenced this issue Sep 29, 2016
Merge pull request #1802 from aledbf/fix-vars
0e7f260 
Automatic merge from submit-queue

[nginx-ingress-controller] Initialize proxy_upstream_name variable

fixes #1801
aledbf pushed a commit to aledbf/contrib that referenced this issue Nov 10, 2016
Merge pull request kubernetes-retired#1802 from aledbf/fix-vars
90d8402 
Automatic merge from submit-queue

[nginx-ingress-controller] Initialize proxy_upstream_name variable

fixes kubernetes-retired#1801
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[nginx-ingress-controller] Initialize proxy_upstream_name variable aledbf/contrib
2 participants
@aledbf @kayrus