Have you checked "journalctl -eu prometheus" - does it say any more than the logs you quoted?
Given what you showed, prometheus appears to be crashing without reporting an error - not even a panic. That seems like a bug. If it's a configuration issue then it might be something to do with filesystem permissions. If you're running it as the "prometheus" user, then make sure that the prometheus data directory and all files under it are owned by "prometheus" too. Perhaps one became owned by root accidentally? Or it could be something else. You might be able to find out a bit more by running it under strace. But if it is a bug, I'd say it's likely fixed in a newer version, and upgrading is the best and easiest approach to fixing your issue. On Wednesday, 26 January 2022 at 09:52:53 UTC thanh...@gmail.com wrote: > Yes, I got it > Im using version the prometheus 2.8.1, Is it too old? And i see my drive > is not full > im sorry guys and Hope you can help me because Im in need of configuration > Thank you verry much!! > Vào lúc 16:08:01 UTC+7 ngày Thứ Tư, 26 tháng 1, 2022, Brian Candler đã > viết: > >> The version of prometheus you're running is ancient - nearly 3 years >> old. Unless you have a specific reason for this version, then I'd suggest >> trying something more modern. There have been lots of improvements in the >> timeseries database internals since then, and if you still have a problem, >> you're more likely to get help resolving it. >> >> Otherwise, the first thing to check is: is your disk full? >> >> On Wednesday, 26 January 2022 at 08:24:48 UTC thanh...@gmail.com wrote: >> >>> I have one case, I restart the service prometheus then it says >>> [root@vps38 ~]# systemctl status prometheus >>> ● prometheus.service - Prometheus >>> Loaded: loaded (/etc/systemd/system/prometheus.service; enabled; >>> vendor preset: disabled) >>> Active: failed (Result: exit-code) since Wed 2022-01-26 15:14:31 +07; >>> 7s ago >>> Process: 9532 ExecStart=/usr/local/bin/prometheus (code=exited, >>> status=1/FAILURE) >>> Main PID: 9532 (code=exited, status=1/FAILURE) >>> >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.56140132Z caller=main.go:285 msg="no time or size >>> retention was set so using the default time retention" duration=15d >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.56145687Z caller=main.go:321 msg="Starting >>> Prometheus" version="(version=2.8.1, branch=HEAD, >>> revision=4d60eb36dcbed725fcac5b27018574118f12fffb)" >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.561472639Z caller=main.go:322 >>> build_context="(go=go1.11.6, user=root@bfdd6a22a683, >>> date=20190328-18:04:08)" >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.561486513Z caller=main.go:323 host_details="(Linux >>> 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 vps38 >>> (none))" >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.561499697Z caller=main.go:324 fd_limits="(soft=1024, >>> hard=4096)" >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.561510835Z caller=main.go:325 >>> vm_limits="(soft=unlimited, hard=unlimited)" >>> Jan 26 15:14:31 vps38 prometheus[9532]: level=info >>> ts=2022-01-26T08:14:31.56193411Z caller=main.go:640 msg="Starting TSDB ..." >>> Jan 26 15:14:31 vps38 systemd[1]: prometheus.service: main process >>> exited, code=exited, status=1/FAILURE >>> Jan 26 15:14:31 vps38 systemd[1]: Unit prometheus.service entered failed >>> state. >>> Jan 26 15:14:31 vps38 systemd[1]: prometheus.service failed. >>> I hope to get help with this case. ths all >>> >> -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/88b9a466-09f0-4a0f-8580-d55960fe620an%40googlegroups.com.
