# Failed to Running Telemtry container

**URL:** <https://forums.portworx.com/t/failed-to-running-telemtry-container/1290>\
**Category:** Portworx Essentials\
**Created:** [April 6, 2022, 10:46am UTC](https://forums.portworx.com/t/failed-to-running-telemtry-container/1290 "2022-04-06T10:46:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aim\_Dian](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/aim_dian/32/552_2.png) [@Aim\_Dian](https://forums.portworx.com/u/Aim_Dian)\
**Post date:** [April 6, 2022, 10:46am UTC](https://forums.portworx.com/t/failed-to-running-telemtry-container/1290/1 "2022-04-06T10:46:19Z")

</div>

Hi team,  
I have some error when trying to running px-metric-collector container here’s the error:

> [2022-04-06 10:31:08.060][1][info][main] [source/server/server.cc:361] request trailer map: 136 bytes:  
> [2022-04-06 10:31:08.060][1][info][main] [source/server/server.cc:361] response header map: 432 bytes: :status,access-control-allow-credentials,access-control-allow-headers,access-control-allow-methods,access-control-allow-origin,access-control-expose-headers,access-control-max-age,age,cache-control,connection,content-encoding,content-length,content-type,date,etag,expires,grpc-message,grpc-status,keep-alive,last-modified,location,proxy-connection,server,transfer-encoding,upgrade,vary,via,x-envoy-attempt-count,x-envoy-decorator-operation,x-envoy-degraded,x-envoy-immediate-health-check-fail,x-envoy-ratelimited,x-envoy-upstream-canary,x-envoy-upstream-healthchecked-cluster,x-envoy-upstream-service-time,x-request-id  
> [2022-04-06 10:31:08.060][1][info][main] [source/server/server.cc:361] response trailer map: 160 bytes: grpc-message,grpc-status  
> [2022-04-06 10:31:08.061][1][info][admin] [source/server/admin/admin.cc:132] admin address: 127.0.0.1:9901  
> [2022-04-06 10:31:08.061][1][info][main] [source/server/server.cc:707] runtime: {}  
> [2022-04-06 10:31:08.064][1][info][config] [source/server/configuration\_impl.cc:127] loading tracing configuration  
> [2022-04-06 10:31:08.064][1][info][config] [source/server/configuration\_impl.cc:87] loading 0 static secret(s)  
> [2022-04-06 10:31:08.064][1][info][config] [source/server/configuration\_impl.cc:93] loading 1 cluster(s)  
> [2022-04-06 10:31:08.069][1][critical][main] [source/server/server.cc:112] error initializing configuration ‘/config/envoy-config.yaml’: Invalid path: /appliance-cert/cert  
> [2022-04-06 10:31:08.069][1][info][main] [source/server/server.cc:855] exiting  
> Invalid path: /appliance-cert/cert

When the container creating from the event i noticed some error

> MountVolume.SetUp failed for volume “pure-telemetry-certs” : secret “pure-telemetry-certs” not found

Any clue for this error?  
Thanks

---

<div class="post-metadata">

**Author:** ![snowman](https://avatars.discourse-cdn.com/v4/letter/s/f17d59/32.png) [@snowman](https://forums.portworx.com/u/snowman)\
**Post date:** [August 25, 2024, 12:44am UTC](https://forums.portworx.com/t/failed-to-running-telemtry-container/1290/2 "2024-08-25T00:44:58Z")

</div>

having similar issue.  
This is for an OKD cluster that do not have direct internet access but does have outbound proxy