> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/how-to-guides/collector-management/collector-linux-username-migration.md).

# Linux Username Migration Guide for Linux Collector v1.82

Deprecated: Linux collectors that run as the observiq-otel-collector user through a hand-written systemd override

Bindplane OTEL Collector v1.82 renamed the Linux system user `observiq-otel-collector` to `bdot`. The package does this automatically, with `usermod`, the first time it installs v1.82 or later. This guide is for Linux collectors that run as the `observiq-otel-collector` user through a systemd override written by hand. macOS and Windows users don't need to take any action.

### Check Whether This Affects You

The Bindplane OTEL Collector runs as `root` by default. Collectors that run as `root`, and collectors installed with `BDOT_UNPRIVILEGED=true` in the [package configuration file](https://docs.bindplane.com/configuration/bindplane-otel-collector/linux-package-configuration.md), need no action.

This guide applies if you followed an earlier version of the [Downgrade Collector Privileges](https://docs.bindplane.com/how-to-guides/collector-management/downgrade-collector-privileges.md) guide, which ran the collector as the `observiq-otel-collector` user with a hand-written override. To check, read the service's unit and drop-ins:

```bash
sudo systemctl cat observiq-otel-collector
```

The main unit file always shows `User=root`. If a drop-in near the bottom of the output, usually `/etc/systemd/system/observiq-otel-collector.service.d/override.conf`, sets `User=observiq-otel-collector`, this guide applies to you.

### Hand-Written Overrides Are Deprecated

Earlier versions of this guide had you edit the override to `User=bdot` after upgrading. Running the collector as non-root with a hand-written systemd override is deprecated, and these docs no longer describe how to set it up or maintain it.

The package doesn't see a hand-written override. It doesn't write the sudoers rule that upgrades from Bindplane need on a non-root collector, so those upgrades fail.

For new non-root collectors, set `BDOT_UNPRIVILEGED=true` in the package configuration file before the first install. See [Downgrade Collector Privileges](https://docs.bindplane.com/how-to-guides/collector-management/downgrade-collector-privileges.md#install-a-collector-as-non-root).


---

# 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://docs.bindplane.com/how-to-guides/collector-management/collector-linux-username-migration.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.
