# OneAgent Uninstallation in Infrastructure Monitoring Mode – Processes Requiring Restart

**URL:** <https://community.dynatrace.com/t/oneagent-uninstallation-in-infrastructure-monitoring-mode-processes-requiring-restart/57473>\
**Category:** Open Q&A\
**Tags:** installation, oneagent\
**Created:** [November 4, 2026, 1:03am UTC](https://community.dynatrace.com/t/oneagent-uninstallation-in-infrastructure-monitoring-mode-processes-requiring-restart/57473 "2026-11-04T01:03:23Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nakazato\_IIM](https://avatars.discourse-cdn.com/v4/letter/n/b5ac83/32.png) [@Nakazato\_IIM](https://community.dynatrace.com/u/Nakazato_IIM)\
**Post date:** [November 4, 2026, 1:03am UTC](https://community.dynatrace.com/t/oneagent-uninstallation-in-infrastructure-monitoring-mode-processes-requiring-restart/57473/1 "2026-11-04T01:03:23Z")

</div>

I am planning to uninstall OneAgent that is running in Infrastructure Monitoring Mode (`infra-only`).

How can I identify which processes require a restart after uninstalling OneAgent?

Also, for processes that belong to the **“Linux System”** process group in Dynatrace, is it necessary to restart them individually as well?

For reference, I ran the following command on the host and found that the OneAgent library appears to be loaded into many processes:

```bash
sudo grep -l liboneagentproc.so /proc/*/maps

```

The results included processes such as `systemd`, `sshd`, `crond`, `chronyd`, and `httpd`, so I’m unsure which processes should be considered restart targets.

I would appreciate any guidance or best practices regarding this.

Thank you.