# Unable to Start pf9-comms Service on the Node.

## Problem

* ***pf9-comms*** fails to start on the node.
* The following errors are reported in *journalctl* logs:

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

```none
test-cluster-master systemd[1]: Starting Platform9 Communications Service...
test-cluster-master systemd[32426]: Failed at step USER spawning /bin/mkdir: No such process
test-cluster-master systemd[1]: pf9-comms.service: control process exited, code=exited status=217
test-cluster-master systemd[1]: Failed to start Platform9 Communications Service.
test-cluster-master systemd[1]: Unit pf9-comms.service entered failed state.
test-cluster-master systemd[1]: pf9-comms.service failed.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All versions
* Platform9 Managed Kubernetes - All versions
* pf9-comms

## Cause

The ownership for directory */var/log/pf9/comms* is incorrect. The directory should be owned by the **pf9** user and **pf9group**.

## Resolution

1. Change the ownership of */var/log/pf9/comms* to **pf9** user and **pf9group**.

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

```none
# chown -R pf9:pf9group /var/log/pf9/comms/
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/generic/solution/unable-to-start-pf9-comms-service-on-the-node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.