thanos-io / thanos

Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
https://thanos.io
Apache License 2.0
13.15k stars 2.1k forks source link

Interactive example #5551

Open Akshit42-hue opened 2 years ago

Akshit42-hue commented 2 years ago

While running the Interactive example I am getting some errors

22:51:06 Starting cadvisor 22:51:37 Ports for container interactive-cadvisor >> Local ports: map[http:8080] Ports available from host: map[http:49153] 22:51:37 Starting monitoring 22:51:48 Ports for container interactive-monitoring >> Local ports: map[http:9090] Ports available from host: map[http:49154] 22:51:49 cadvisor: W0729 17:21:49.844312 1 machine_libipmctl.go:62] There are no NVM devices! 22:51:55 monitoring: level=error ts=2022-07-29T17:21:55.023Z caller=main.go:355 msg="Error loading config (--config.file=/shared/data/monitoring/prometheus.yml)" err="parsing YAML file /shared/data/monitoring/prometheus.yml: yaml: unmarshal errors:\n line 11: field enable_http2 not found in type config.ScrapeConfig\n line 22: field enable_http2 not found in type config.ScrapeConfig\n line 33: field enable_http2 not found in type config.ScrapeConfig\n line 44: field enable_http2 not found in type config.ScrapeConfig" 22:52:10 Killing monitoring 22:52:10 Error response from daemon: Cannot kill container: interactive-monitoring: No such container: interactive-monitoring

22:52:10 Unable to kill service monitoring : exit status 1 22:52:10 Killing cadvisor 22:52:15 monitoring-exec: Error: No such container: interactive-monitoring 22:52:15 Unable to kill service cadvisor : exit status 1 --- FAIL: TestReadOnlyThanosSetup (73.37s) interactive_test.go:122: interactive_test.go:122: unexpected error: the service monitoring is not ready: Get "http://127.0.0.1:49154/-/ready": dial tcp 127.0.0.1:49154: connect: connection refused

FAIL FAIL command-line-arguments 73.425s FAIL Screenshot from 2022-07-29 22-55-29

Akshit42-hue commented 2 years ago

Hey @douglascamata, can you please look into this :)

douglascamata commented 2 years ago

Works fine for me:

16:46:03 monitoring: ts=2022-08-03T16:46:03.861Z caller=main.go:996 level=info msg="TSDB started"
16:46:03 monitoring: ts=2022-08-03T16:46:03.861Z caller=main.go:1177 level=info msg="Loading configuration file" filename=/shared/data/monitoring/prometheus.yml
16:46:03 monitoring: ts=2022-08-03T16:46:03.862Z caller=main.go:1214 level=info msg="Completed loading of configuration file" filename=/shared/data/monitoring/prometheus.yml totalDuration=725.409µs db_storage=900ns remote_storage=2.5µs web_handler=400ns query_engine=900ns scrape=265.504µs scrape_sd=47µs notify=800ns notify_sd=1.4µs rules=1.7µs tracing=6.1µs
16:46:03 monitoring: ts=2022-08-03T16:46:03.862Z caller=main.go:957 level=info msg="Server is ready to receive web requests."
16:46:03 monitoring: ts=2022-08-03T16:46:03.862Z caller=manager.go:937 level=info component="rule manager" msg="Starting rule manager..."
16:46:04 monitoring: ts=2022-08-03T16:46:04.017Z caller=main.go:1177 level=info msg="Loading configuration file" filename=/shared/data/monitoring/prometheus.yml
16:46:04 monitoring: ts=2022-08-03T16:46:04.018Z caller=main.go:1214 level=info msg="Completed loading of configuration file" filename=/shared/data/monitoring/prometheus.yml totalDuration=705.11µs db_storage=1.6µs remote_storage=3µs web_handler=900ns query_engine=1.5µs scrape=57.8µs scrape_sd=74.301µs notify=2µs notify_sd=1.5µs rules=1.3µs tracing=6.101µs

Looks like some problem with your Docker setup or temporary files that the interactive test creates. I recommend deleting examples/tmp and examples/interactive/data if they exist, plus running docker system prune -a to ensure a clean environment.

stale[bot] commented 2 years ago

Hello 👋 Looks like there was no activity on this issue for the last two months. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.