Dynatrace / dynatrace-oneagent-operator

Kubernetes/Openshift Operator for managing Dynatrace OneAgent deployments
Apache License 2.0
88 stars 48 forks source link

Oneagent crashing with Unrecognized parameter: PROCESSHOOKING=0 #375

Closed Fabian-K closed 3 years ago

Fabian-K commented 3 years ago

Hi,

we are facing the following issue for the oneagent pods after updating from 0.8.2 to 0.9.4. I´m not sure why this happens, also rolling back to 0.8.2 shows the same issue. Do you have a suggestion where to look at?

Thanks!

11:35:19 Warning: ONEAGENT_INSTALLER_SCRIPT_URL does not match expected pattern, please verify its correctness. If installer download succeeded then this message may safely be ignored. Example URL: https://abc123.live.dynatrace.com/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=ABCDEFGabcdefg0123456&arch=x86
11:35:43 Started agent deployment as a Docker container, PID 812959.
11:35:43 Downloading agent to /tmp/Dynatrace-OneAgent-Linux.sh via https://***/e/***/api/v1/deployment/installer/agent/unix/default/latest?Api-Token=***&arch=x86&flavor=default
11:35:44 Download was skipped as the agent version did not change
11:35:44 Validating downloaded agent installer
11:35:52 Verification successful
11:35:52 Deploying to: /mnt/host_root
11:35:52 Starting installer...
11:35:55 Error: Unrecognized parameter: PROCESSHOOKING=0
Usage: Dynatrace-OneAgent-Linux.sh [-h] [-v] [--set-server=https://server_address:server_port] [--set-tenant=tenant] [--set-tenant-token=tenant_token] [--set-proxy=proxy_address:proxy_port|no_proxy] [--set-host-group=host_group] [--set-infra-only=false|true] [INSTALL_PATH=absolute_path] [--set-app-log-content-access=false|true] [USER=username] [GROUP=groupname] [NON_ROOT_MODE=0|1] [DISABLE_ROOT_FALLBACK=0|1]
-h, --help                           Display this help and exit.
-v, --version                        Print version and exit.
SERVER (deprecated)                  The server that OneAgent connects to.
TENANT (deprecated)                  Environment ID.
TENANT_TOKEN (deprecated)            Environment authorization token.
PROXY (deprecated)                   The proxy through which OneAgent connects to SERVER. Set to 'no_proxy' to clear the proxy.
HOST_GROUP (deprecated)              (Early adopter) This parameter can only contain: alphanumeric characters, hyphen, underscore and dot. It must not start with 'dt.' and maximum allowed length is 100.
INFRA_ONLY (deprecated)              Enables Infrastructure-Only Monitoring mode. Provides virtual-infrastructure monitoring only (no application-performance or user-experience data). For details, see https://www.dynatrace.com/support/help/shortlink/infrastructure#anchor-infrastructure-only
APP_LOG_CONTENT_ACCESS (deprecated)  Allow the agent to access log files stored on the machine. See what insights can log analytics provide: https://www.dynatrace.com/support/help/shortlink/log-analytics-insights
INSTALL_PATH                         Installation path to be used, must be absolute and not contain any spaces.
USER                                 The name of the unprivileged user for OneAgent processes. Must contain 3-32 alphanumeric characters. Defaults to 'dtuser'
GROUP                                The name of the primary group for OneAgent processes, defaults to the value of USER. May only be used in conjunction with USER.
NON_ROOT_MODE                        Enables non-privileged mode. For details, see: https://www.dynatrace.com/support/help/shortlink/root-privileges#linux-non-root-mode
DISABLE_ROOT_FALLBACK                Disables temporary elevation of the privileges in environments where ambient capabilities are unavailable.
For details, see: https://www.dynatrace.com/support/help/shortlink/linux-custom-installation
You can pass the host-level configuration parameters starting with '--set-'. For details, see https://www.dynatrace.com/support/help/shortlink/oneagentctl
lrgar commented 3 years ago

Hello @Fabian-K - which OneAgent version are you using?

Fabian-K commented 3 years ago

Thanks for the quick reply! The OneAgent CR shows 1.209.169.20210219-191956 in the status

lrgar commented 3 years ago

I believe you are using a very old OneAgent image version, could you please update to the latest? It's configured on the .spec.image field from the OneAgent object.

Available images: https://hub.docker.com/r/dynatrace/oneagent

Fabian-K commented 3 years ago

You are right, thanks! I was running image digest sha256:a48e2da2d2e76575176f71acc89fe9774d3f4f732b8aa9f47aadf19949e4a1f5, no idea how old that is/was. dynatrace/oneagent:1.48.1000 is working fine.