On Monday, 31 August 2020 14:12:31 UTC+1, Redneck_prm wrote: > > cat /proc/1/cmdline > > /bin/prometheus--web.console.templates=/etc/prometheus/consoles--web.console.libraries=/etc/prometheus/console_libraries--config.file=/etc/prometheus/config_out/prometheus.env.yaml--storage.tsdb.path=/prometheus--storage.tsdb.retention.time=30m--web.enable-lifecycle--storage.tsdb.no-lockfile--web.external-url= > http://prometheus.loc/--web.route-prefix=// > > --web.route-prefix=// looks wrong.
--storage.tsdb.no-lockfile doesn't even appear to be documented <https://prometheus.io/docs/prometheus/latest/storage/#operational-aspects>. But if prometheus operator sets these by default, then I guess they must be OK. > > strace -f > stream hangs on for a few seconds on different places: > > [pid 15911] <... read resumed> 0xc0043b7000, 4096) = -1 EAGAIN (Resource > temporarily unavailable) > [pid 15338] tgkill(1, 13, SIGURG <unfinished ...> > [pid 15911] epoll_pwait(4, [{EPOLLIN|EPOLLOUT, {u32=976213944, > u64=140562370910136}}], 128, 0, NULL, 99926) = 1 > [pid 15349] madvise(0xc00d600000, 4194304, MADV_HUGEPAGE <unfinished ...> > [pid 15911] read(92, <unfinished ...> > [pid 15338] <... tgkill resumed> ) = 0 > > Those are different threads mixed up so it's hard to see what's what, and you'd also need to look at more context to find what these fd's actually refer to (e.g. fd 92 for the read, find the corresponding open or connect call). These might just be scrapes. Sorry, I can't help you. I've not seen the problem you describe. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/12b65478-2f67-434b-8af3-500e5a13893ao%40googlegroups.com.
