Nilushan Costa

@zasgar unfortunately I won't be able to commit to this at this time. I will try to contribute if possible

I looked into this and came across https://docs.nats.io/legacy/stan/changes/configuring/persistence/file_store#recovery-errors. It had the following ``` With the -file_truncate_bad_eof parameter, the server will still print those bad records but truncate each file at...

Since Pixie uses a config map for NATS Streaming, I referred https://docs.nats.io/legacy/stan/changes/configuring/cfgfile#file-options-configuration to add the config. However the `-file_truncate_bad_eof` option is not available in the above documentation link. So I...

As per the discussion in the Pixie Slack channel, deleted the existing `vizier-metadata` pod and let the newly created one sync with the K8s API. However pods are still missing...

@aimichelle thanks for looking into this. The `Failed to get update version for topic` error has been printed from time to time even after the pod started. Also when I...

I deleted the PV along with the vizier-metadata pod and created a new PV. However this did not resolve the issue

I upgraded the Pixie deployment to the latest version. However the issue still exists. Please find some more findings regarding the nature of this problem. 1. When pods were missing...

I was debugging one of the issues ("No data available error" explained in the issue description) and noticed the following. 1. I selected a "Running" pod from the cluster for...

> Hi @nilushancosta ! Thanks sending that debug information over. To confirm, for the pods in "Running" state in your cluster, but for which the Pixie UI had "No data...

I am also facing the issue with Helm chart version 3.1.9 with Cluster Agent 7.39.2. Part of the debug logs from the cluster-agent ``` 2022-10-13 10:05:01 UTC | CLUSTER |...