-
Bug
-
Resolution: Fixed
-
Major
-
jenkins v2.108
swarm v3.12
JDK 1.8.0
Windows 7 / CentOS 7.4 host OSes
-
-
3.17
When launching the Jenkins swarm client, I see the following warning message in the console output:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"
SLF4J: Defaulting to no-operation (NOP) loger implementation
Consequently, I am unable to generate log files for the service, making it impossible to debug errors and connection issues and such in production. This seems like a silly issue but it is debilitating and it would be great if someone could fix it or tell me how to work around the issue.
I've looked up the slf4j.org website where it describes some workarounds to this error by placing one of the slf4j jars in the Java class path. I downloaded several different versions of slf4j, and copied different jar files contained therein to the default class path, all with no success. Even explicitly setting the java class path to a folder containing all the jars for slf4j didn't work. What am I doing wrong?
Any help would be greatly appreciated.
[JENKINS-50970] SLF4J logging not working in Swarm client
Kevin Phillips
created issue -
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
| Labels | New: newbie-friendly |
Basil Crow
made changes -
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Basil Crow
made changes -
| Summary | Original: SLF4J logging not working in Jenkins Swarm plugin | New: SLF4J logging not working in Swarm client |
Basil Crow
made changes -
| Assignee | New: Basil Crow [ basil ] |
Basil Crow
made changes -
| Released As | New: 3.17 | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Basil Crow
made changes -
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |
