jamshid
jamshid
FWIW I switched my image to mbentley/apt-cacher-ng (https://github.com/mbentley/docker-apt-cacher-ng) and I don't seem to be seeing the weird `Hash Sum mismatch` errors anymore. ``` services: aptcacherng: deploy: resources: limits: memory: 300m...
Yeah wondering the same thing, is there a recommended dashboard for this (standard?) prometheus exporter plugin or a list of ones that work with it? I use this one https://grafana.com/grafana/dashboards/266...
FWIW I also get it on Elasticsearch 7.5.2: ``` [2021-05-11T15:21:48,063][WARN ][r.suppressed ] [ivory4.X] path: /_prometheus/metrics, params: {} java.lang.NullPointerException: null at org.compuscene.metrics.prometheus.PrometheusMetricsCollector.updatePerIndexContextMetrics(PrometheusMetricsCollector.java:468) ~[?:?] at org.compuscene.metrics.prometheus.PrometheusMetricsCollector.updatePerIndexMetrics(PrometheusMetricsCollector.java:461) ~[?:?] at org.compuscene.metrics.prometheus.PrometheusMetricsCollector.updateMetrics(PrometheusMetricsCollector.java:947) ~[?:?] at org.elasticsearch.rest.prometheus.RestPrometheusMetricsAction$1.buildResponse(RestPrometheusMetricsAction.java:87)...
Sure, thanks: ``` curl 'ivory4:9200/_cluster/settings?include_defaults=true&filter_path=defaults.prometheus' \ 'ivory4:9200/_cluster/settings?include_defaults=true&filter_path=transient.prometheus' \ 'ivory4:9200/_cluster/settings?include_defaults=true&filter_path=persistent.prometheus' {"defaults":{"prometheus":{"cluster":{"settings":"true"},"indices":"true"}}} {} {} ``` FWIW it doesn't happen all the time, sometimes 5 times in a half hour, sometimes twice within...
Hi @ankon sorry to bug you but I would also like to use maven-s3-wagon with a S3-compatible system, so your endpoint enhancement is exactly what I need. Should `mvn package`...
Nevermind @ankon, got `mvn install` to work with below pom.xml changes. I guess if I knew maven I'd understand why the `` element has to be removed when building someone...
FYI @ankon added support for a `maven.wagon.s3.endpoint` property in pull request https://github.com/jcaddel/maven-s3-wagon/pull/28/. Follow there, it does work but you need to build and host it.
I was also having this problem when using an S3 compatible system that has a certificate signed by a custom CA. I had already configured my `centos:7.5.1804` to trust that...
Also running into this... Is there any way to allow `DOCKER_BUILDKIT=1 docker build .` with below Dockerfile to succeed, so a legacy package installation does not have to be rewritten?...
This is also breaking builds installing fpm on centos 7. I know it's EOL in a couple of years but still need to build packages on it. What I don't...