topic Re: dynatracegateway.service: Deactivated successfully. in Open Q&A

dynatracegateway.service: Deactivated successfully.

dyn98007 — Sat, 14 Sep 2024 04:23:02 GMT

I'm trying to setup an Activegate in a RHEL 9.2 EC2 host for the purpose of monitoring remote technologies using extensions.

The activegate has to connect to a managed cluster.

The issue that is being faced is that the service is not starting.

Details below.....

$ systemctl status dynatracegateway

○ dynatracegateway.service - Dynatrace ActiveGate service
Loaded: loaded (/etc/systemd/system/dynatracegateway.service; disabled; preset: disabled)
Active: inactive (dead)

Sep 14 04:05:24 ip-xyz.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Deactivated successfully.
Sep 14 04:05:24 ip-xyz.us.us-west-2.compute.internal systemd[1]: Started Dynatrace ActiveGate service.
Sep 14 04:05:24 ip-1 xyz.us.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Consumed 1.092s CPU time.
Sep 14 04:07:52 ip-xyz.us.us-west-2.compute.internal systemd[1]: Starting Dynatrace ActiveGate service...
Sep 14 04:07:52 ip-xyz.us.us-west-2.compute.internal dynatracegateway[2021491]: 14/09 04:07:52 (1.295.27.20240715-230200) Dynatrace ActiveGate started.
Sep 14 04:07:53 ip-xyz.us.us-west-2.compute.internal dynatracegateway[2021491]: 14/09 04:07:53 (1.295.27.20240715-230200)
Sep 14 04:07:53 ip-xyz.us.us-west-2.compute.internal dynatracegateway[2021527]: 14/09 04:07:53 (1.295.27.20240715-230200)
Sep 14 04:07:53 ip-xyz.us.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Deactivated successfully.
Sep 14 04:07:53 ip-xyz.us.us-west-2.compute.internal systemd[1]: Started Dynatrace ActiveGate service.
Sep 14 04:07:53 ip-xyz.us.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Consumed 1.193s CPU time.

----------

$ cat dynatracegateway-start_20240914-040752.log

/opt/dynatrace/gateway/dynatracegateway: line 194: /opt/dynatrace/gateway/launcher/dynatracegateway: Operation not permitted

------

Please advise..

Re: dynatracegateway.service: Deactivated successfully.

AntonPineiro — Sat, 14 Sep 2024 15:49:30 GMT

Hi,

Missing permissions? I would raise a support ticket in that situation.

Best regards

Re: dynatracegateway.service: Deactivated successfully.

SivaP — Mon, 16 Sep 2024 14:15:45 GMT

Check permissions and SELinux status once.

and ACL as mentioned in document.

The ActiveGate Linux installer doesn't support ACL (Access Control List). ACL rules may prohibit access to installer-created directories and files, making the ActiveGate fail to start. If you use the ACL, rules related to the installation directories defined in the following parameters should be disabled:

INSTALL=
CONFIG=
LOG=
TEMP=
PACKAGES_DIR=

https://docs.dynatrace.com/docs/setup-and-configuration/dynatrace-activegate/installation/linux/linux-activegate-hardware-and-system-requirements

Re: dynatracegateway.service: Deactivated successfully.

Peter_Youssef — Mon, 16 Sep 2024 11:34:53 GMT

First of all:

Validate the user permissions granted to install and operate DT activegate.
for activegate services stop and restart visit the following URL: Start/stop/restart ActiveGate - Dynatrace Managed Docs
validate against the supported HW and SW requirements: https://docs.dynatrace.com/managed/shortlink/activegate-landing#system-and-hardware-requirements
if you have custom configurations, validate it through: Customize ActiveGate installation on Linux - Dynatrace Managed Docs

Thanks.

Re: dynatracegateway.service: Deactivated successfully.

Peter_Youssef — Mon, 16 Sep 2024 19:17:42 GMT

@dyn98007 validate the configured parameters in custom.properties file for safe upadate, copy and paste the original file and use the copied for checking.

Refer to the configurable parameters of Dynatrace activegate: Configuration properties and parameters of ActiveGate - Dynatrace Managed Docs

Re: dynatracegateway.service: Deactivated successfully.

dyn98007 — Mon, 16 Sep 2024 20:06:11 GMT

@SivaP -In the above mentioned Installation directories (INSTALL=, CONFIG=, LOG=, TEMP=, PACKAGES_DIR=) , the user ownership was changed to - chown -R dtuserag:dtuserag dynatrace .

Also, in the same EC2 host, as seen below, dynatraceautoupdater.service is in running status.

[root@ip-10-xxx gateway]# systemctl status dynatraceautoupdater
● dynatraceautoupdater.service - Dynatrace ActiveGate AutoUpdater service
Loaded: loaded (/etc/systemd/system/dynatraceautoupdater.service; disabled; preset: disabled)
Active: active (running) since Sat 2024-09-14 02:56:50 UTC; 2 days ago
Main PID: 1948798 (autoupdater.sh)
Tasks: 2 (limit: 100662)
Memory: 1.4M
CPU: 5min 58.326s
CGroup: /system.slice/dynatraceautoupdater.service
├─1792410 sleep 30
└─1948798 /bin/bash /opt/dynatrace/autoupdater/autoupdater.sh --wait

Sep 14 02:56:45 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: Starting Dynatrace ActiveGate AutoUpdater service...
Sep 14 02:56:45 ip-10-x-x-xx.us-west-2.compute.internal dynatraceautoupdater[1948770]: 14/09 02:56:45 Dynatrace ActiveGate AutoUpdater 1.295.27.20240715-230200 started.
Sep 14 02:56:50 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: Started Dynatrace ActiveGate AutoUpdater service.
Sep 14 03:07:54 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: /etc/systemd/system/dynatraceautoupdater.service:8: PIDFile= references a path below legacy directory /var/run/, updat>
Sep 16 19:38:01 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: /etc/systemd/system/dynatraceautoupdater.service:8: PIDFile= references a path below legacy directory /var/run/, updat>
Sep 16 19:44:24 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: /etc/systemd/system/dynatraceautoupdater.service:8: PIDFile= references a path below legacy directory /var/run/, updat>
Sep 16 19:46:34 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: /etc/systemd/system/dynatraceautoupdater.service:8: PIDFile= references a path below legacy directory /var/run/, updat>
lines 1-18/18 (END)

[root@ip-10-x-x-xx gateway]# systemctl status dynatracegateway
○ dynatracegateway.service - Dynatrace ActiveGate service
Loaded: loaded (/etc/systemd/system/dynatracegateway.service; enabled; preset: disabled)
Active: inactive (dead) since Mon 2024-09-16 19:46:41 UTC; 10min ago
Process: 1783928 ExecStart=/opt/dynatrace/gateway/dynatracegateway start (code=exited, status=0/SUCCESS)
Process: 1783984 ExecStop=/opt/dynatrace/gateway/dynatracegateway stop (code=exited, status=0/SUCCESS)
CPU: 1.263s

Sep 16 19:46:39 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: Starting Dynatrace ActiveGate service...
Sep 16 19:46:40 ip-10-x-x-xx.us-west-2.compute.internal dynatracegateway[1783928]: 16/09 19:46:40 (1.295.27.20240715-230200) Dynatrace ActiveGate started.
Sep 16 19:46:40 ip-10-x-x-xx.us-west-2.compute.internal dynatracegateway[1783928]: 16/09 19:46:40 (1.295.27.20240715-230200)
Sep 16 19:46:41 ip-10-x-x-xx.us-west-2.compute.internal dynatracegateway[1783984]: 16/09 19:46:41 (1.295.27.20240715-230200)
Sep 16 19:46:41 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Deactivated successfully.
Sep 16 19:46:41 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: Started Dynatrace ActiveGate service.
Sep 16 19:46:41 ip-10-x-x-xx.us-west-2.compute.internal systemd[1]: dynatracegateway.service: Consumed 1.263s CPU time.

[root@ip-10-x-x-xx gateway]#

Re: dynatracegateway.service: Deactivated successfully.

dyn98007 — Mon, 16 Sep 2024 23:26:36 GMT

Update: Issue has been resolved.

# cat dynatracegateway-start_20240914-025712.log
/opt/dynatrace/gateway/dynatracegateway: line 194: /opt/dynatrace/gateway/launcher/dynatracegateway: Operation not permitted

"Operation not permitted" error was fixed by adding the uid of dtuserag to the allow rules in fapolicyd (Details in the screenshot).

[root@ip-100-x-x-xx ssm-user]# systemctl status dynatracegateway
● dynatracegateway.service - Dynatrace ActiveGate service
Loaded: loaded (/etc/systemd/system/dynatracegateway.service; enabled; preset: disabled)
Active: active (running) since Mon 2024-09-16 20:54:52 UTC; 56min ago
Process: 1853423 ExecStart=/opt/dynatrace/gateway/dynatracegateway start (code=exited, status=0/SUCCESS)
Main PID: 1853677 (dynatracegatewa)
Tasks: 169 (limit: 20000)
Memory: 979.9M
CPU: 1min 44.385s
CGroup: /system.slice/dynatracegateway.service
├─1853677 /opt/dynatrace/gateway/launcher/dynatracegateway -bg -config /var/lib/dynatrace/gateway/config/dynatracegateway.ini
└─1853681 /opt/dynatrace/gateway/jre/bin/java -Dcom.compuware.apm.WatchDogTimeout=180 -classpath "./lib/*" --add-opens=java.base/java.lang=ALL-UNNAMED -Xms1024M -XX:ErrorFile>

Sep 16 20:54:51 ip-100-x-x-xx.us-west-2.compute.internal systemd[1]: Starting Dynatrace ActiveGate service...
Sep 16 20:54:51 ip-100-x-x-xx.us-west-2.compute.internal dynatracegateway[1853423]: 16/09 20:54:51 (1.295.27.20240715-230200) Dynatrace ActiveGate started.
Sep 16 20:54:52 ip-100-x-x-xx.us-west-2.compute.internal dynatracegateway[1853423]: 16/09 20:54:52 (1.295.27.20240715-230200)
Sep 16 20:54:52 ip-100-x-x-xx.us-west-2.compute.internal systemd[1]: Started Dynatrace ActiveGate service.
lines 1-16/16 (END)

More on RHEL fapolicyd can be read here