> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/smcp/frequently-asked-questions/pf9-containerproxy-service-in-failed-state-on-platform9-mgmt-pla.md).

# pf9-containerproxy.service is in Failed State on Platform9 Management Plane?

## Problem

* Why systemd service `pf9-containerproxy.service` is in failed state on the Platform9 Management Plane Virtual Machine?

{% tabs %}
{% tab title="Bash" %}

```javascript
[root@airctl-support-lts.pf9.localnet ~(admin)]# systemctl status pf9-containerproxy.service
● pf9-containerproxy.service - Platform9 Container Proxy Service
   Loaded: loaded (/usr/lib/systemd/system/pf9-containerproxy.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Thu 2022-07-07 20:34:25 UTC; 2 weeks 4 days ago
 Main PID: 5025 (code=exited, status=1/FAILURE)
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Edge Cloud - All Versions

## Answer

* The systemd service `pf9-containerproxy.service` on Platform9 Management Plane was previously used for multiple purposes but mainly as a Certificate Authority (CA) server.
* In latter versions it was replaced with another Platform9 System Service i.e. `pf9-vault.service`

```javascript
[root@airctl-support-lts.pf9.localnet ~(admin)]# systemctl list-units --all | grep -i vault
pf9-vault.service                  loaded    active   running   "Platform9 Vault - Handling PMK secrets"
```

* The `pf9-containerproxy.service` is currently not in use but because it is integrated in the `qbert` package, it is not yet completely removed.

{% tabs %}
{% tab title="Bash" %}

```javascript
[root@airctl-support-lts.pf9.localnet ~(admin)]# rpm -q --whatprovides /usr/lib/systemd/system/pf9-containerproxy.service
pf9-qbert-5.3.0-15888.x86_64
```

{% endtab %}
{% endtabs %}

* The service failure status won't have any adverse effect on the management plane or the clusters and hence it can be safely ignored.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/smcp/frequently-asked-questions/pf9-containerproxy-service-in-failed-state-on-platform9-mgmt-pla.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.