# Impact, Validation and Repair Action if pf9-nodeletd and pf9-comms Services are Down

## Problem

Impact, validation and repair action if `pf9-nodeletd` and `pf9-comms` services are down.

## Environment

* Platform9 Managed Kubernetes - All Versions
* Nodeletd
* Comms

## Answer

* If `pf9-nodelet` service goes down on it’s own, then the `pf9-hostagent` service will start it back up.

Example:

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

```bash
# systemctl stop pf9-nodeletd
```

{% endtab %}
{% endtabs %}

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

```bash
# tail -f hostagent.log
2022-02-14 22:47:58,035 - session.py INFO - Already converged. Idling...
2022-02-14 22:49:04,208 - session.py INFO - --- Converging ---
2022-02-14 22:49:07,696 - pf9_app.py INFO - Setting the desired service state
2022-02-14 22:49:07,697 - pf9_app.py INFO - Setting service state pf9-nodeletd.1.20.11-pmk.2038. Command: sudo systemctl start pf9-nodeletd
2022-02-14 22:49:10,246 - session.py INFO - Converge succeeded
```

{% endtab %}
{% endtabs %}

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

```bash
# systemctl status pf9-nodeletd
● pf9-nodeletd.service - Platform9 Kubernetes Management Agent Service
   Loaded: loaded (/usr/lib/systemd/system/pf9-nodeletd.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2022-02-14 22:49:07 UTC; 17s ago
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
**Info**

If `pf9-nodelet` & `pf9-hostagent` services both go down OR are stopped, even then the PMK stack will continue to run, but operations of managing the stack on that node, status checks on nodeletd phases etc. will not occur.
{% endhint %}

* For `pf9-comms` service, if it is stopped, the `pf9-hostagent` service will start it back up.

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

```bash
# systemctl stop pf9-comms
```

{% endtab %}
{% endtabs %}

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

```bash
# less comms.log
[2022-02-14 22:52:56.848] [INFO] comms - Caught SIGTERM ... exiting cleanly now.

[2022-02-14 22:53:11.330] [INFO] sniMapWatcher - IPv6 settings found on host. Will listen on IPv4 & IPv6
[2022-02-14 22:53:11.389] [INFO] comms - pf9-comms started at Mon Feb 14 2022 22:53:11 GMT+0000 (Coordinated Universal Time)
```

{% endtab %}
{% endtabs %}

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

```bash
# tail -f hostagent.log
2022-02-14 22:53:10,056 - session.py WARNING - Not sending status message because channel is closed
2022-02-14 22:53:10,056 - pf9_app.py INFO - Setting the desired service state
2022-02-14 22:53:10,056 - pf9_app.py INFO - Setting service state pf9-comms.5.3.0-975.046bd33. Command: sudo systemctl start pf9-comms
2022-02-14 22:53:12,546 - session.py INFO - Converge succeeded
2022-02-14 22:53:12,546 - session.py WARNING - Not sending status message because channel is closed
```

{% endtab %}
{% endtabs %}

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

```bash
# systemctl status pf9-comms
● pf9-comms.service - Platform9 Communications Service
   Loaded: loaded (/usr/lib/systemd/system/pf9-comms.service; disabled; vendor preset: disabled)
   Active: active (running) since Mon 2022-02-14 22:53:10 UTC; 2 min ago
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
**Info**

If `pf9-comms` & `pf9-hostagent` services both go down or are stopped, even then the PMK stack will continue to run, but the node itself will report as offline to the management plane.
{% endhint %}

Additional Information

[Platform9 Host Components](https://platform9.com/docs/PEC/host-components)


---

# 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/pmk/frequently-asked-questions/impact-validation-and-repair-pf9-nodeletd-and-pf9-comms.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.