Ch11 jenkins won't start

Question

Ch11 jenkins won't start

vasily-kartashov opened this issue 4 years ago · comments

Exercise
Chapter 11

Problem
Jenkins container stuck in "Please wait while Jenkins is getting ready to work..."

Docker version
Client: Docker Engine - Community
Cloud integration: 1.0.1
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 16:58:31 2020
OS/Arch: darwin/amd64
Experimental: false

Code version
19a8d04

Additional context
Running on MacOS

vka · Answer 1 · Fri Nov 13 2020 15:51:38 GMT+0800 (China Standard Time)

From the logs:

SEVERE	h.model.UpdateCenter$DownloadJob#run: Failed to install bouncycastle-api

which maybe related to jenkinsci/docker#787

Jason Salas · Answer 2 · Sat Feb 13 2021 15:56:54 GMT+0800 (China Standard Time)

Hi @vasily-kartashov, I was able to get Jenkins to start on Ubuntu 20.x and launch the UI, but it doesn't auto-load the diamol job as illustrated in Ch11.

Elton Stoneman · Answer 3 · Wed Mar 03 2021 19:11:33 GMT+0800 (China Standard Time)

HI @vasily-kartashov - this is usually a temporary network issue where Jenkins can't load the plugins. I've updated the Jenkins version, you can pull the updated images like this:

cd ch11/exercises/infrastructure

docker-compose pull

Can you try again with the new version and LMK if it still fails? Thanks.

Jeff Urlwin · Answer 4 · Tue Jul 05 2022 01:02:54 GMT+0800 (China Standard Time)

I am currently having an issue, even with the pull. it appears a newer version of Jenkins is required? Not sure...as i'm not yet an expert. I see sprinklings of issues in the logs, such as:
2022-07-04 16:53:37.949+0000 [id=63] SEVERE h.model.UpdateCenter$DownloadJob#run: Failed to install command-launcher
java.io.IOException: Failed to load: Command Agent Launcher Plugin (81.v9c2cb_cb_db_392)

Jenkins (2.277.1) or higher required

Also, note, that on MacOS port 5000 is now used by the OS for AirPlay support...sigh
But I don't think i've reached that problem yet...other than starting the registry on 5001, but as I indicated, I don't think Jenkins is yet fully operational...

Jeff Urlwin · Answer 5 · Tue Jul 05 2022 01:03:31 GMT+0800 (China Standard Time)

(and P.S. Jenkins does start, just no jobs preloaded...)

Jeff Urlwin · Answer 6 · Tue Jul 05 2022 06:33:29 GMT+0800 (China Standard Time)

sorry for 'spamming' but bumping Jenkins version to 2.277.4 in the image build seems to get me past the initial error after grepping through the logs. .4 was the "highest" version reported as the min and things at least are starting / configured.

On MacOS, port 5000 now being used, so I locally changed port to 5001 - Jenkins file (for build) and docker-compose.yml. Once I pushed those to GOG, the build ran perfectly.