Junk output appear in task logs

[fviale]

The unexpected following outputs appear systematically in tasks logs, on a clean scheduler 7.33 installation (Windows):

[email protected];18:51:48] log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies). [[email protected];18:51:48] log4j:WARN Please initialize the log4j system properly. [[email protected];18:51:48] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

[email protected];18:51:55] log4j:WARN No appenders could be found for logger (jsr223.cpython.utils.PythonVersionGetter). [[email protected];18:51:55] log4j:WARN Please initialize the log4j system properly. [[email protected];18:51:55] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Until we find a workaround or fix it, it is a critical issue

[fviale]

The only workaround I see is to add a fork environment script which contains the following code: forkEnvironment.addJVMArgument("-Dlog4j.configuration=file:" + System.getProperty("proactive.home") + "/config/log/node.properties")

The problem is that the log4j configuration defined in the node is not forwarded to the forked JVM process, or rather that no specific configuration is set for the forked JVM.

[fviale]

The problem persists even if python is installed on the machine.