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 upUnexpected fault address on 2.0.0-rc2 #3375
Comments
This comment has been minimized.
This comment has been minimized.
|
Thanks for reporting. Is this reproducible, i.e. does it crash again if you restart it? Crash happening here on memory access against an mmaped chunk file: https://github.com/prometheus/tsdb/blob/master/chunks.go#L354 From a bit of research, SIGBUS occurs in combination with mmap if the mapped region exceeds the actual file size. However, we call mmap exactly with the size of the file: https://github.com/prometheus/tsdb/blob/master/block.go#L406 The source of the crash is also not at the potential end of the file, which generally rules out an off-by-one error here. Also, every byte of chunk files are traversed on compaction and a general error would've caused this panic for virtually everyone. Assuming the instantiation is correct, the only potential cause seems to be modification/truncating of the file after loading it. There should be no code to hypothetically do this in Prometheus itself. AFAICS, there are no other potential causes for SIGBUS. |
This comment has been minimized.
This comment has been minimized.
|
I am not able to reproduce it consistently. But it happened couple times already. I have to wipe the data directory to recover it. |
This comment has been minimized.
This comment has been minimized.
@WeiBanjo You mean Prometheus crashes on start with the existing data? Is it the same error on restart? If yes, then that would be helpful in pinpointing whats wrong. |
This comment has been minimized.
This comment has been minimized.
|
Yes. Prometheus crashes on start with the existing data. When Prometheus in that state, it's a crash loop. |
This comment has been minimized.
This comment has been minimized.
|
Both my Prometheus containers crashed again today. Here is the log from first occurrence. Hopefully it's usefully to identify this issue.
|
This comment has been minimized.
This comment has been minimized.
|
How to proceed here? Is this a bug to block the final 2.0.0 release on? I'm missing the deeper insight to make that call. |
This comment has been minimized.
This comment has been minimized.
|
now that we are on the 2.2.1 this looks obsolete. |
krasi-georgiev
closed this
May 1, 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. |
WeiBanjo commentedOct 30, 2017
•
edited
What did you do?
Upgrade from 2.0.0-rc0 to 2.0.0-rc2
What did you see instead? Under which circumstances?
unexpected fault address
Environment
Prometheus version:
Starting Prometheus" version="(version=2.0.0-rc.2, branch=HEAD, revision=ce63a5a8557bb33e2030a7756c58fd773736b592)Logs:
Full crash log