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 upinvalid memory address or nil pointer dereference #3653
Comments
This comment has been minimized.
This comment has been minimized.
|
It doesn't panic when I use |
This comment has been minimized.
This comment has been minimized.
|
Sounds like this is already fixed then and will be in 2.1.0, but it would be by some other PR. |
brian-brazil
closed this
Jan 4, 2018
brian-brazil
added
component/service discovery
kind/bug
labels
Jan 4, 2018
This comment has been minimized.
This comment has been minimized.
|
@brian-brazil I think you've misread what I'm saying here. Master is broken. |
brian-brazil
reopened this
Jan 4, 2018
This comment has been minimized.
This comment has been minimized.
|
Ah. @krasi-georgiev this sounds like what you're working on at the moment. |
krasi-georgiev
referenced this issue
Jan 4, 2018
Merged
discovery - handle Discoverers that send only target Group updates. #3654
This comment has been minimized.
This comment has been minimized.
|
@errordeveloper at first glance this looks like a different bug in the |
This comment has been minimized.
This comment has been minimized.
stanxing
commented
Jan 5, 2018
|
I have the same problem |
This comment has been minimized.
This comment has been minimized.
|
@stanxing can you try the mentioned PR to see if it fixes it for you ? |
This comment has been minimized.
This comment has been minimized.
chalky9909
commented
Jan 10, 2018
|
@brian-brazil I see you have referenced an updated release 2.1.0 in the comments above. We have encountered the same panic (below) from the latest master release which we are currently troubleshooting:
We are using the :master release tagged quay.io/prometheus/prometheus SHA256: 0b745814b3c5 Do you have an approximate ETA for when the 2.10 release may be available that may resolve this issue? |
This comment has been minimized.
This comment has been minimized.
|
@chalky9909 hard to tell if it is the same issue without the full stack trace , but if it really is than I am pretty sure the PR reference above fixes this issue so once it is merged should be good to go. Otherwise if your full stack trace looks different please open a new issue. |
This comment has been minimized.
This comment has been minimized.
chalky9909
commented
Jan 10, 2018
|
@krasi-georgiev I have tested the PR reference above |
gouthamve
closed this
in
#3654
Jan 15, 2018
This comment has been minimized.
This comment has been minimized.
bamb00
commented
Oct 19, 2018
|
Hi @krasi-georgiev, What is the best way to reproduce this error with prometheus server? Thanks. |
errordeveloper commentedJan 4, 2018
What did you do?
I ran the latest build from master, and it paniced.
What did you expect to see?
Happy Prometheus.
What did you see instead? Under which circumstances?
Environment
Kubernetes 1.7 on GKE.