Major Hi,
When I use the /exit or /safeRestart, everything works as expected.
When I use the Manage Jenkins -> Prepare for Shutdown, I have the red headband saying Jenkins will shut down, but nothing is shown in the logs, and Jenkins never stops.
From a fresh installation, you can see the plugins install, and then when I ask for a shutdown, no further log can be seen.
h.m.DownloadService$Downloadable#load: Obtained the updated data file for hudson.tasks.Ant.AntInstaller 2022-05-11 14:34:52.108+0000 [id=133] INFO h.m.DownloadService$Downloadable#load: Obtained the updated data file for hudson.plugins.gradle.GradleInstaller 2022-05-11 14:34:52.989+0000 [id=133] INFO h.m.DownloadService$Downloadable#load: Obtained the updated data file for hudson.tools.JDKInstaller 2022-05-11 14:34:53.039+0000 [id=310] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 2022-05-11 14:34:53.043+0000 [id=319] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 2022-05-11 14:34:53.045+0000 [id=325] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 2022-05-11 14:34:53.097+0000 [id=334] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 2022-05-11 14:34:53.109+0000 [id=341] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 2022-05-11 14:34:53.114+0000 [id=346] INFO jenkins.InitReactorRunner$1#onAttained: System config loaded 2022-05-11 14:34:53.143+0000 [id=318] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted 2022-05-11 14:34:53.184+0000 [id=330] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 2022-05-11 14:34:53.185+0000 [id=333] INFO jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated 2022-05-11 14:34:53.487+0000 [id=331] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2022-05-11 14:34:53.491+0000 [id=133] INFO h.m.UpdateCenter$CompleteBatchJob#run: Completed installation of 83 plugins in 1 min 43 sec
Using --rm --restart=always --restart=on-failure makes no difference in behaviour.
![FireShot Capture 006 - Update shutdown preparation [Jenkins] - localhost.png](/secure/attachment/58030/FireShot%20Capture%20006%20-%20Update%20shutdown%20preparation%20%5BJenkins%5D%20-%20localhost.png)
[JENKINS-68500] Jenkins 2.34x (launched with Docker) does not quit when asking with Manage Jenkins -> Prepare for Shutdown
Bruno Verachten
created issue -
Feng-Yi Xue
made changes -
| Assignee | New: Feng-Yi Xue [ felix_416 ] |
Feng-Yi Xue
made changes -
| Assignee | Original: Feng-Yi Xue [ felix_416 ] |
I think this may be a misunderstanding of the purpose and intent of "Prepare for shutdown". The description of the action on www.jenkins.io says
Prevents new builds from starting so that the system can be shut down safely.
I believe the intent of that action is to prevent new builds so that the administrator can choose at a later time to restart the system or stop the system.
The /safeRestart action is "Prepare for shutdown" followed by "Restart".
The /restart action is "Restart" without any delay or preparation for the shutdown.
My bad, Mark, I should have better read the documentation.
Let's close that issue, sorry for that. 
Maybe I could just add a little something in the documentation linking to the description of /exit, /safeRestart and /restart.
Bruno Verachten
added a comment - - edited My bad, Mark, I should have better read the documentation.
Let's close that issue, sorry for that.
Maybe I could just add a little something in the documentation linking to the description of /exit , /safeRestart and /restart . Bruno Verachten
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Basil Crow
added a comment - There's also a /safeExit although I do not believe we expose it in the UI.
Basil Crow
added a comment - There's also a /safeExit although I do not believe we expose it in the UI. I think it would be great if you added a broader description of "Prepare for shutdown" and mentioned the "/restart" and "/safeRestart" end points.
When I use the "/exit" endpoint, it tells me that it needs to switch to POST. If others have that same experience, that leads me to think that we should not describe it.
I will definitely propose a modification to the documentation 
I am also experimenting the same behaviour with the /exit end point.
I will have a deeper look at the documentation, but are these end points linked to a button, an action, whatever within the UI?
Are we supposed to stop/restart Jenkins just by modifying the URL by hand, by a REST API request, or via the command line?
I'm a command line guy, but sometimes, it's easier to interact with Jenkins via the UI.
I guess the "Prepare for Shutdown" can also be done via an end point/REST/command, but... If we initiate it via the UI, why can't we "finish the job" within the UI too?
Maybe that only makes sense to me.
Where is the correct place to discuss that? Community?
Thanks for your feedback 
Bruno Verachten
added a comment - - edited I will definitely propose a modification to the documentation
I am also experimenting the same behaviour with the /exit end point.
I will have a deeper look at the documentation, but are these end points linked to a button, an action, whatever within the UI?
Are we supposed to stop/restart Jenkins just by modifying the URL by hand, by a REST API request, or via the command line?
I'm a command line guy, but sometimes, it's easier to interact with Jenkins via the UI.
I guess the "Prepare for Shutdown" can also be done via an end point/REST/command, but... If we initiate it via the UI, why can't we "finish the job" within the UI too?
Maybe that only makes sense to me.
Where is the correct place to discuss that? Community ?
Thanks for your feedback
No plans to investigate this. Pull requests are welcome.