Thursday, June 7, 2018

Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for details

Question Details:
When I was running the gradle clean command, I got the following message
Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for details
For the investigation, I run the following command.
$ gradle --status
   PID STATUS   INFO
 11506 BUSY     4.3.1
  8027 STOPPED  (stop command received)
  9347 STOPPED  (stop command received)
 11727 STOPPED  (by user or operating system)
  4786 STOPPED  (by user or operating system)
 14569 STOPPED  (by user or operating system)
 31237 STOPPED  (by user or operating system)

Only Daemons for the current Gradle version are displayed. See https://docs.gradle.org/4.3.1/userguide/gradle_daemon.html#sec:status
So, some questions have arisen in my mind.
  1. How can I stop an existing daemon?
  2. How to kill daemon process?
Answer:
Stopping an existing Daemon:
If you want to explicitly stop running Daemon processes for any reason, just use the command gradle --stop.
But gradle --stop won’t stop daemons running with a different version of Gradle.
How to kill all Daemon process on my machine?
Gradle will kill any Daemon that has been idle for 3 hours or more, so you don’t have to worry about cleaning them up manually.
So the command and output are given below:
$ gradle --stop
Stopping Daemon(s)
2 Daemons stopped
After stopping daemons, status will be look like below:
$ gradle --status
No Gradle daemons are running.
   PID STATUS   INFO
  8027 STOPPED  (stop command received)
  9347 STOPPED  (stop command received)
 12448 STOPPED  (stop command received)
 11506 STOPPED  (stop command received)
 11727 STOPPED  (by user or operating system)
  4786 STOPPED  (by user or operating system)
 14569 STOPPED  (by user or operating system)
 31237 STOPPED  (by user or operating system)
If you are stuck with gradle build running, you can to through this post: Stuck with Gradle Build Running

No comments:

Post a Comment