> 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/solution/nodelet-fails-at--configure-and-start-pf9-bouncer--phase.md).

# Nodelet Fails at "Configure and start pf9-bouncer" Phase

## Problem

Platform9 nodelet phase fails at "*Configure and start pf9-bouncer*" phase with "*bind address already in use*" on bouncer logs.

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

```bash
{"log":"2024/04/10 05:35:40 serve http:listen tcp 127.0.0.1:9977: bind: address already in use<br>","stream":"stderr","time":"2024-04-10T05:35:40.02933616Z"}
```

{% endtab %}
{% endtabs %}

Nodelet logs keep showing "*Waiting for "authn\_webhook\_listening" to evaluate to true*" message.

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

```bash
{"L":"INFO","T":"2024-04-10T05:35:39.781Z","C":"command/command.go:120","M":"[2024-04-10 05:35:39] Stopping containers 'bouncer'"}
{"L":"INFO","T":"2024-04-10T05:35:39.807Z","C":"command/command.go:120","M":"[2024-04-10 05:35:39] No such container: bouncer"}
{"L":"INFO","T":"2024-04-10T05:35:39.810Z","C":"command/command.go:120","M":"[2024-04-10 05:35:39] Destroying containers 'bouncer'"}
{"L":"INFO","T":"2024-04-10T05:35:39.836Z","C":"command/command.go:120","M":"[2024-04-10 05:35:39] bouncer"}
{"L":"INFO","T":"2024-04-10T05:35:40.030Z","C":"command/command.go:120","M":"[2024-04-10 05:35:40] 90907c098a9b96c6c3ce40605f7d2f869fb4e67d55f86f9b6ddf279a56aba7a4"}
{"L":"INFO","T":"2024-04-10T05:35:40.053Z","C":"command/command.go:120","M":"[2024-04-10 05:35:40] Waiting for \"authn_webhook_listening\" to evaluate to true ..."}
{"L":"INFO","T":"2024-04-10T05:35:45.073Z","C":"command/command.go:120","M":"[2024-04-10 05:35:45] Waiting for \"authn_webhook_listening\" to evaluate to true ..."}
{"L":"INFO","T":"2024-04-10T05:35:50.094Z","C":"command/command.go:120","M":"[2024-04-10 05:35:50] Waiting for \"authn_webhook_listening\" to evaluate to true ..."}
```

{% endtab %}
{% endtabs %}

## Environment

* SMCP version 5.9.1.

## Cause

On the underlying node stale bouncer process keeps holding port 9977.

## Resolution

Verify the stale process by running the below command:

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

```bash
# ps -aux | grep -i "9977"
# netstat -tunlp | grep -i "9977"
```

{% endtab %}
{% endtabs %}

Once we get the process ID follow the procedure given below:

1. Stop the pf9-nodeletd and pf9-hostagent service - `systemctl stop pf9-hostagent pf9-nodeletd`.
2. Force stop the nodelet phases using `$ /opt/pf9/nodelet/nodeletd phases stop --force` .
3. Kill the stale bouncerd process using `$ kill -9 <bouncerd-process-id>` .
4. Start nodelet phase using - `systemctl start pf9-hostagent`.
5. Verify the nodelet phase status using `$ /opt/pf9/nodelet/nodeletd phases status` .

## Additional Information

The above procedure helps to recover the nodelet phase issue due to the bouncer bind address already in use error.


---

# 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/solution/nodelet-fails-at--configure-and-start-pf9-bouncer--phase.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.