Anton Shishlin

Results 13 comments of Anton Shishlin

I have similar issue. superset version: apache/superset:2.0.0 and apache/superset:1.5.1 clickhouse-sqlalchemy 0.1.6 clickhouse-driver 0.2.0

clickhouse-driver==0.2.1 and clickhouse-sqlalchemy==0.1.9 fixed it

same issue v0.7.10 add logs and strace [process_exporter_high_cpu_load.zip](https://github.com/ncabatoff/process-exporter/files/12870711/process_exporter_high_cpu_load.zip)

> same issue v0.7.10 add logs and strace [process_exporter_high_cpu_load.zip](https://github.com/ncabatoff/process-exporter/files/12870711/process_exporter_high_cpu_load.zip) I set config: ```yml process_names: - comm: - postgres ``` but it didn't help. High cpu load presents only when process_exporter...

`multi-vcenter-csi-topology` option absent in `internal-feature-states.csi.vsphere.vmware.com` configmap. ```yaml kind: ConfigMap apiVersion: v1 metadata: annotations: meta.helm.sh/release-name: vsphere-csi meta.helm.sh/release-namespace: kube-system labels: app.kubernetes.io/managed-by: Helm name: internal-feature-states.csi.vsphere.vmware.com namespace: kube-system data: async-query-volume: 'false' block-volume-snapshot: 'false' cnsmgr-suspend-create-volume:...

I use rancher's helm chart: https://artifacthub.io/packages/helm/rke2-charts/rancher-vsphere-csi In this `topology` option is disabled by default. https://artifacthub.io/packages/helm/rke2-charts/rancher-vsphere-csi?modal=template&template=controller/deployment.yaml (212 line)

I added `multi-vcenter-csi-topology: true` to configmap, but it didn't help. Also I tried `multi-vcenter-csi-topology: false`. vsphere-csi-controller again crashed after creating PVC.

``` {"level":"info","time":"2024-01-30T06:39:53.042383033Z","caller":"vanilla/controller.go:1805","msg":"CreateVolume: called with args {Name:pvc-13e4061b-61d6-4f6a-ad6a-ef7d1425dc4e CapacityRange:required_bytes:10485760 VolumeCapabilities:[mount: access_mode: ] Parameters:map[] Secrets:map[] VolumeContentSource: AccessibilityRequirements: XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}","TraceId":"2177c87f-8ff3-406f-8ffa-b366a1d14a12"} panic: runtime error: invalid memory address or nil pointer dereference 2024-01-30T06:39:53.059969372Z [signal SIGSEGV:...

I have same issue. Cluster is green, but one node has repeated errorss. ``` [2023-08-09T16:12:01,601][ERROR][o.o.s.s.h.n.SecuritySSLNettyHttpServerTransport] [elastic2] Exception during establishing a SSL connection: ... [2023-08-09T16:12:21,603][ERROR][o.o.s.s.h.n.SecuritySSLNettyHttpServerTransport] [elastic2] Exception during establishing a SSL...