oneagent vs DB2

[henk_stobbe]

Please take care when deploying oneagent on a DB2 database, the port 50000 is used by both!

DB2 wil not start, and nestat shows:

tcp 0 0
127.0.0.1:50000 0.0.0.0:* LISTEN
12188/oneagentwatch

tcp 0 0
127.0.0.1:50001 0.0.0.0:* LISTEN
12188/oneagentwatch

tcp 0 0 127.0.0.1:50002
0.0.0.0:* LISTEN 12188/oneagentwatch

tcp 0 0 127.0.0.1:50003
0.0.0.0:* LISTEN 12188/oneagentwatch

How to resolve:

https://help.dynatrace.com/get-started/setup-tips/...

[Julius_Loman]

Happened to me half a year ago. Defaulting to 50000/tcp is a bad idea, since oneagent typically starts first. Oneagent installer should check if the 50000/tcp is already taken at installation time and try other ports (for example 51000/tcp) and save that port range to configuration. By default it keeps the 50000/tcp even if it's not available at install time (on first startup it always takes first nonused port from the configuration).