{{tag>jenkins troubleshooting}}

====== Jenkins troubleshooting ======
===== Too much logging =====

Issue with a certain java library causes writes of hundreds of GBs in logs
Solution is to run jenkins without DNS function

In ///etc/default/jenkins// add these 2 options in JAVA_ARGS line:

''-Dhudson.DNSMultiCast.disabled=true -Dhudson.udp=-1''

Restart jenkins:

  service jenkins restart

===== average-duration-exceeded =====
If Jenkins is integrating with rundeck you might get this error on triggering rundeck job:

<code>
Waiting for Rundeck execution to finish...
Rundeck execution #31579 finished in null, with status : average-duration-exceeded
FATAL: Unexpected executions status: average-duration-exceeded
java.lang.IllegalStateException: Unexpected executions status: average-duration-exceeded
	at org.jenkinsci.plugins.rundeck.RundeckNotifier.notifyRundeck(RundeckNotifier.java:299)
	at org.jenkinsci.plugins.rundeck.RundeckNotifier.perform(RundeckNotifier.java:165)
	at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:80)
	at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:468)
	at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:405)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
	at hudson.model.Run.execute(Run.java:1900)
	at hudson.model.Run.run(Run.java:1854)
	at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:317)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:442)
Finished: FAILURE
</code>

To fix this go to the rundeck job, to notifications and under "Average Duration Exceeded" try raising the threshold.
==== Tested on ====
  * Rundeck 4.16.0
  * Version 2.414.1

====== See also ======

====== References ======
  * https://docs.rundeck.com/docs/manual/jobs/job-notifications.html#configuring-average-duration-exceeded