What can I do when OneAgent blocks a port I need?

adham_sabry · ‎02 Nov 2022

OneAgent consists of different processes that communicate via a TCP port with a watchdog. At startup, OneAgent watchdog attempts to open the first available port between port 50000 and 50100. In some cases you may need this port for your own applications that are started after OneAgent. In such cases, you can change the port range that the OneAgent watchdog uses by calling OneAgent command-line interface.

You can change the watchdog listening port by using

set-watchdog-portrange

via oneagentctl command-line tool:

For example, to change port range to 50005:50105, go to the oneagentctl directory and run the following command:
- On Linux or AIX:
```
./oneagentctl --set-watchdog-portrange 50005:50105
```
- On Windows:
```
.\oneagentctl.exe --set-watchdog-portrange 50005:50105
```
  Restart OneAgent service to apply changes.

See Which network ports does Dynatrace Server use? for information on the ports used by Dynatrace.

OneAgent version 1.183 and earlier

Change the port range that the OneAgent watchdog uses by modifying the file watchdoguserconfig.conf.

The file watchdoguserconfig.conf is located in /var/lib/dynatrace/oneagent/agent/config on Linux AIX and %PROGRAMDATA%\dynatrace\oneagent\agent\config on Windows.
You can change the watchdog listening port by modifying the following line in the file:
- From, for example:
```
-portrange=50000:50100
```
  To:
```
-portrange=50005:50105
```
- Restart OneAgent service to apply changes.

kalle_lahtinen · ‎02 Nov 2022

Managing the watchdog port range is easy, but when it comes to the other OneAgent processes like oneagentos, things get more tricky. Some discussion on that topic can be found here:

https://community.dynatrace.com/t5/Dynatrace-product-ideas/RFE-OneAgent-Ability-to-change-default-po...