Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPanic in EC2 discovery: NetworkInterfaces #4441
Comments
simonpasquier
added
component/service discovery
kind/bug
labels
Aug 1, 2018
This comment has been minimized.
This comment has been minimized.
|
Looks like the code hasn't changed since 1.8.2, so this is still an issue. |
brian-brazil
added
the
low hanging fruit
label
Aug 1, 2018
noqcks
added a commit
to noqcks/prometheus
that referenced
this issue
Aug 7, 2018
brian-brazil
closed this
in
#4469
Aug 7, 2018
brian-brazil
added a commit
that referenced
this issue
Aug 7, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
nhinds commentedJul 31, 2018
•
edited
Bug Report
What did you do?
Ran Prometheus 1.8.2 with EC2 service discovery across many EC2 instances in unknown states.
What did you expect to see?
EC2 service discovery works without crashing.
What did you see instead? Under which circumstances?
Prometheus panicked about a nil pointer dereference:
This looks similar to #3001, but this time the the nil pointer was not in EC2 tags, it was in the ENI code: https://github.com/prometheus/prometheus/blob/v1.8.2/discovery/ec2/ec2.go#L190
I am unsure what AWS instance state caused the AWS SDK to return a
nilpointer in theNetworkInterfacesfield.I have not tried reproducing this with the latest Prometheus version as I am unsure how exactly to replicate it. However, the code in
masterfor iterating overinst.NetworkInterfacesdoes not seem to handlenilpointersEnvironment
System information:
Linux 3.10.0-693.17.1.el7.x86_64 x86_64
Prometheus version:
prometheus, version 1.8.2 (branch: HEAD, revision: 5211b96)
build user: root@1412e937e4ad
build date: 20171104-16:09:14
go version: go1.9.2
Alertmanager version:
(Not relevant)
Prometheus configuration file:
I do not believe the scrape configuration is relevant to this issue, please ask if there is a specific configuration section that is required.
Alertmanager configuration file:
(Not relevant)
Logs: