search

ow2-proactive / scheduling

Multi-platform Scheduling and Workflows Engine
http://www.activeeon.com/workflows-scheduling
GNU Affero General Public License v3.0
61 stars 54 forks source link

Junk output appear in task logs #3052

Open fviale opened 6 years ago

fviale commented 6 years ago

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

1t2@00LFISAEON03.groupe-ufg.com;18:51:48] log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies). [1t2@00LFISAEON03.groupe-ufg.com;18:51:48] log4j:WARN Please initialize the log4j system properly. [1t2@00LFISAEON03.groupe-ufg.com;18:51:48] log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

1t3@00LFISAEON03.groupe-ufg.com;18:51:55] log4j:WARN No appenders could be found for logger (jsr223.cpython.utils.PythonVersionGetter). [1t3@00LFISAEON03.groupe-ufg.com;18:51:55] log4j:WARN Please initialize the log4j system properly. [1t3@00LFISAEON03.groupe-ufg.com;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 commented 6 years ago

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 commented 6 years ago

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