Getenforce error at JVM startup

[jeremietisserand]

Error description:
At JVM startup I get an error log in datadaog with getenforce label.

Since:
https://github.com/DataDog/dd-trace-java/releases/tag/v1.28.0

Error details:
Error stacktrace

error=2, No such file or directory
java.io.IOException: error=2, No such file or directory
	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at com.datadog.profiling.controller.ProfilerSettingsSupport.getSELinuxStatus(ProfilerSettingsSupport.java:121)
	at com.datadog.profiling.controller.ProfilerSettingsSupport.<init>(ProfilerSettingsSupport.java:113)
	at com.datadog.profiling.controller.openjdk.JfrProfilerSettings.<init>(JfrProfilerSettings.java:22)
	at com.datadog.profiling.controller.openjdk.JfrProfilerSettings$SingletonHolder.<clinit>(JfrProfilerSettings.java:18)
	at com.datadog.profiling.controller.openjdk.JfrProfilerSettings.instance(JfrProfilerSettings.java:30)
	at com.datadog.profiling.controller.openjdk.OpenJdkController.<init>(OpenJdkController.java:97)
	at com.datadog.profiling.controller.openjdk.OpenJdkController.instance(OpenJdkController.java:77)
	at com.datadog.profiling.agent.ControllerFactory$Implementation.instance(ControllerFactory.java:62)
	at com.datadog.profiling.agent.ControllerFactory.createController(ControllerFactory.java:126)
	at com.datadog.profiling.agent.ProfilingAgent.run(ProfilingAgent.java:119)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at datadog.trace.bootstrap.Agent.startProfilingAgent(Agent.java:906)
	at datadog.trace.bootstrap.Agent.start(Agent.java:314)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at datadog.trace.bootstrap.AgentBootstrap.agentmain(AgentBootstrap.java:71)
	at datadog.trace.bootstrap.AgentBootstrap.premain(AgentBootstrap.java:55)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:491)
	at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:503)

[smola]

@jeremietisserand Thank you for reporting this. This was an unexpected interaction between tracing of subprocess, and the usage of the getenforce command by the profiler. It will be fixed in v1.29.0 (PR). These traces can be safely ignored.

[github-actions]

🤖 This issue has been addressed in the latest release. See full details in the Release Notes.