> 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/generic/solution/unable-to-install-pf9-hostagent-package-on-the-node.md).

# Unable to Install pf9-hostagent Package on the node

## Problem

* Unable to install pf9-hostagent package on the node
* We see below errors in the */var/log/pf9/hostagent.log.*

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

```none
Unable to install pf9-hostagent package on the node

pf9_app_db.py ERROR - Install command failed: sudo /opt/pf9/hostagent/bin/pf9-apt install /var/cache/pf9apps/pf9-hostagent/4.4.0-3252.9717c06/pf9-hostagent-4.4.0-3252.9717c06.x86_64.deb. Return code: 1, stdout: Setting up initramfs-tools (0.122ub
untu8.14) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-4.4.0-194-generic (4.4.0-194.226) ...
Processing triggers for initramfs-tools (0.122ubuntu8.14) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-193-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.


gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-193-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for linux-image-4.4.0-194-generic (4.4.0-194.226) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.4.0-194-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions
* Platform9 Managed OpenStack - All Versions

## Cause

There is no space on the /boot partition.

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

```none
$ df -h
Filesystem                      Size  Used Avail Use% Mounted on
udev                              20G    0  20G  0% /dev
tmpfs                            4.0G  394M  3.6G  10% /run
/dev/mapper/cluster2--vg-root    218G  12G  195G  6% /
tmpfs                            20G    0  20G  0% /dev/shm
tmpfs                            5.0M    0  5.0M  0% /run/lock
tmpfs                            20G    0  20G  0% /sys/fs/cgroup
/dev/sda2                        721M  681M  3.0M 100% /boot
/dev/sdb1                        1.8T  68M  1.7T  1% /mnt/raid
/dev/sda1                        511M  3.6M  508M  1% /boot/efi
10.10.0.203:/volume1/kubernetes  32T  18T  14T  57% /nfs/kubernetes
tmpfs                            4.0G    0  4.0G  0% /run/user/1001
```

{% endtab %}
{% endtabs %}

## Resolution

Free the disk space in the */boot* partition. The */boot* directory contains all of your kernel images, so the likely cause of this issue is that you have too many previous kernels installed.


---

# 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 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/generic/solution/unable-to-install-pf9-hostagent-package-on-the-node.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 `automate deployments from our CI pipeline` 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.