Sam Ware

Is this bug present in 5.5 and/or 5/6?

I'm not using the CLI but helm. Chart Version is 0.7.0

``` apiVersion: v1 kind: Service metadata: annotations: meta.helm.sh/release-name: tobs meta.helm.sh/release-namespace: default creationTimestamp: "2021-12-01T15:03:50Z" labels: app: tobs-timescaledb app.kubernetes.io/managed-by: Helm chart: timescaledb-single-0.8.2 cluster-name: tobs component: patroni heritage: Helm release: tobs name: tobs-config...

Here is the describe: Name: tobs-config Namespace: default Labels: app=tobs-timescaledb app.kubernetes.io/managed-by=Helm chart=timescaledb-single-0.8.2 cluster-name=tobs component=patroni heritage=Helm release=tobs Annotations: meta.helm.sh/release-name: tobs meta.helm.sh/release-namespace: default Selector: app=tobs-timescaledb,cluster-name=tobs Type: ClusterIP IP Family Policy: SingleStack IP...

@cmanaha are there any comments or needs to get this pull request accepted?

Has anyone heard from the project leader?

Sure

Reopened after decision with Adrian

I have been running into this as well. ```Error in MetricServer: System.Net.HttpListenerException (0x80131620): Unable to write data to the transport connection: Broken pipe. at System.Net.HttpResponseStream.EndWriteCore(IAsyncResult asyncResult) at System.Net.HttpResponseStream.EndWrite(IAsyncResult asyncResult) at...

I added this to my SystemD service definition and it seems to help the service recover but it is still happening and sometimes doesn't recover. ``` After=network-online.target Wants=network-online.target ```