cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Permissions to read the ruxitagent_pluginagent log file

Ben_Harvey
Contributor

Hi, Im in the process of debugging a custom plugin on a linux server.
I'm having issues accessing the ruxitagent_pluginagent logs. For some reason the log files are written without read permission for anyone but the owner or root. Other files in the directory get the read permission. Is this something to do with our install or is it intentional? 
I could log in as root and read them, seems excessive to lock down a log file, when i can view the other log files in the same directory. 

 

 

 

 

 

-rw-r--r-- 1 dtuser dtuser  6960361 Oct  6 14:35 pluginDevLoggerPluginEngineDefault.log
-rw-r--r-- 1 root   root    1022764 Oct  6 14:35 pluginDevLoggerOsAgentDefault.log
-rw------- 1 dtuser dtuser  1373988 Oct  6 14:35 ruxitagent_pluginagent_26650.0.log
-rw-r--r-- 1 dtuser dtuser 10232274 Oct  6 14:29 pluginDevLoggerPluginEngineDefault.log.1
-rw-r--r-- 1 root   root   10488498 Oct  6 12:43 pluginDevLoggerOsAgentDefault.1.log
-rw-r--r-- 1 dtuser dtuser        0 Oct  6 08:05 ruxitagent_pluginagent_fault_info_26650.log
-rw------- 1 root   root       1742 Oct  6 08:04 ruxitagent_plugin_bootstrap_26650.0.log
-rw------- 1 dtuser dtuser  3429551 Oct  6 08:04 ruxitagent_pluginagent_21227.0.log
-rw------- 1 root   root       1742 Oct  5 14:48 ruxitagent_plugin_bootstrap_21227.0.log
-rw------- 1 dtuser dtuser   381362 Oct  5 14:48 ruxitagent_pluginagent_1219.0.log
-rw------- 1 root   root       1742 Oct  5 13:30 ruxitagent_plugin_bootstrap_1219.0.log
-rw------- 1 dtuser dtuser   464088 Oct  5 13:26 ruxitagent_pluginagent_16435.0.log
-rw------- 1 root   root       1742 Oct  5 11:42 ruxitagent_plugin_bootstrap_16435.0.log
-rw------- 1 dtuser dtuser   135819 Oct  5 11:42 ruxitagent_pluginagent_15260.0.log
-rw------- 1 root   root       1742 Oct  5 11:41 ruxitagent_plugin_bootstrap_15260.0.log
-rw------- 1 dtuser dtuser  4192493 Oct  5 11:41 ruxitagent_pluginagent_13062.1.log
-rw------- 1 dtuser dtuser 10486073 Oct  4 10:10 ruxitagent_pluginagent_13062.0.log
-rw------- 1 root   root       1742 Oct  1 11:06 ruxitagent_plugin_bootstrap_13062.0.log
-rw------- 1 dtuser dtuser  1641682 Oct  1 11:05 ruxitagent_pluginagent_21972.0.log
-rw------- 1 root   root       1742 Oct  1 02:12 ruxitagent_plugin_bootstrap_21972.0.log
-rw------- 1 dtuser dtuser  4842545 Oct  1 02:12 ruxitagent_pluginagent_3220.4.log
-rw------- 1 dtuser dtuser 10486157 Sep 29 21:56 ruxitagent_pluginagent_3220.3.log
-rw------- 1 dtuser dtuser 10486137 Sep 27 08:42 ruxitagent_pluginagent_3220.2.log
-rw------- 1 dtuser dtuser 10486096 Sep 24 19:27 ruxitagent_pluginagent_3220.1.log

 

 

 

 

 

2 REPLIES 2

larry_roberts
DynaMight Champion
DynaMight Champion

I ran into the same issue when we first started using Dynatrace. The only people with root access are the Unix Admins so we just created a script that can be executed through sudo for the dtuser which updates all the permissions with a single command when needed. I am then able to login to a server, sudo to the dtuser account and by using an alias setup for the dtuser profile, execute the alias which fires the script that changes all the permissions on the logs. That way I don't need to get a Unix Admin each time. Since they are the only ones that have edit rights to the script - it works out nicely. 👍

Thanks Larry, nice idea, ill put it to our admins.