Starting a Gradle Daemon, 1 busy and 6 stopped Daemons could not be reused, use --status for details
GradleBuildAndroid Gradle-Pluginbuild.gradleGradle Problem Overview
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.
-
How can I stop an existing daemon?
-
How to kill daemon process?
Gradle Solutions
Solution 1 - Gradle
> Stopping an existing Daemon:
If you want to explicitly stop running Daemon processes for any reason, just use the command gradle --stop
.
Note: for your consideration the gradle --stop
command 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.
Resource Link: Gradle Daemon Issue Details
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: https://stackoverflow.com/questions/37063217/stuck-with-gradle-build-running
Solution 2 - Gradle
I solve it with another method in other post.
By removing folders like 4.4 4.6 5.4.1 5.5
in directory as below
> /users/[username]/.gradle/daemon
Solution 3 - Gradle
My problem solved only by changing gradle version from:
>App\android\gradle\wrapper\gradle-wrapper.properties
>>old: distributionUrl=https://services.gradle.org/distributions/gradle-6.7-all.zip
>>new: distributionUrl=https://services.gradle.org/distributions/gradle-6.9-all.zip
Solution 4 - Gradle
just reboot ur computer then go to .gradle folder and delete the daemon folder
Solution 5 - Gradle
Just add two lines in your app -> Gradle Scripts -> gradle properties
org.gradle.daemon=true
org.gradle.parallel=true
Solution 6 - Gradle
For linux users
step 1 : cd ~ && rm -rf .gradle
step 2 : cd <to flutter working project directory>
step 3 : flutter run -v
then kill process with ctrl+c
.gradle dir will be created in /home/<user>/.gradle/wrapper/dists/gradle-<version>-all/9uukhhbclvbegdvsww0j0cr3p
step 4 : download gradle zip version on official website
step 5 : copy and paste the downloaded gradle inside /home/<user>/.gradle/wrapper/dists/gradle-<version>-all/9uukhhbclvbegdvsww0j0cr3p
step 6 : run flutter run -v
step 7 : everything is ok
Solution 7 - Gradle
Aku mencoba cara ini .
1. dari App kamu => masuk folder android
2. .gradle folder hapus
3. gradle folder buka dan pilih file gradle-wrapper-properties dan isinya ganti dengan ini ==>
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
Solution 8 - Gradle
Beleive it or not
npm cache clean --force
solved this for me