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 upPossible Bug: runtime error: invalid memory address or nil pointer dereference #4697
Comments
alevchuk
changed the title
go/src/sync/atomic/64bit_arm SIGSEGV: segmentation violation
Possible BUG: runtime error: invalid memory address or nil pointer dereference
Oct 5, 2018
alevchuk
changed the title
Possible BUG: runtime error: invalid memory address or nil pointer dereference
Possible Bug: runtime error: invalid memory address or nil pointer dereference
Oct 5, 2018
beorn7
self-assigned this
Oct 5, 2018
This comment has been minimized.
This comment has been minimized.
|
I'll take this. We simply have to update the vendoring for client_golang to include prometheus/client_golang@7973e47 . Note: This is not in the release-2.4 brunch, but only in master. |
beorn7
closed this
in
#4698
Oct 5, 2018
lock
bot
locked and limited conversation to collaborators
Apr 3, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
alevchuk commentedOct 5, 2018
Bug Report
Highlight:
panic: runtime error: invalid memory address or nil pointer dereference. created by github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb.Open /home/prometheus/gocode/src/github.com/prometheus/prometheus/vendor/github.com/prometheus/tsdb/db.go:272 +0x468What did you do?
Used https://github.com/prometheus/prometheus#building-from-source
to build Prometheus on Rasbperry Pi 3+, started node_exporter, and started Prometheus.
What did you expect to see?
Prometheus to keep running.
What did you see instead? Under which circumstances?
prometheus crashes about 1 minute after start
Environment
System information:
Linux 4.14.62-v7+ armv7l
Prometheus version:
It was built from f033f48