I think I might have found the issue. I "think" I was trying to force run a job that was waiting for an executor on the master. The master had 2 hung jobs.
From: Ginga, Dick Sent: Monday, October 21, 2013 9:34 AM To: [email protected] Subject: CLI command failing since Friday 10/18/13 I have a job that runs one jenkins cli command. It was working before 12 PM EST 10/18/13. @echo # @echo # set the build display name @echo # java -jar \Jenkins\jenkins-cli.jar -s http://dilithium.perkinelmer.net:8082/ set-build-display-name %JOB_TO_LABEL% %BUILD_TO_LABEL% %DISPLAY_NAME% Now each invocation produces this: Description: Unable to locate the server named "wiki.jenkins-ci.org" --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again. I can ping the wiki server from the master where this job runs and I can browse to it. It appears that after attempting to run, it gets re-queued Dick Ginga, Informatics R&D PerkinElmer Inc. | For the Better HUMAN HEALTH | ENVIRONMENTAL HEALTH 940 Winter Street, Waltham MA 02451 [email protected]<mailto:[email protected]> Mobile - 508-847-1434 Office - 781-663-6947 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
