Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

gradle DaemonDisappearedException with 1.15.2

Truffacious

By Truffacious
in Support & Bug Reports

 Share

Recommended Posts

Truffacious Tree Puncher

Truffacious

Posted
Posted

environment:

Mac OS X Sierra

forge-1.15.2-31.2.0

jdk1.8.0_251

----------------------------------

gradle.properties:

 Sets default memory used for gradle commands. Can be overridden by user or command line properties.
# This is required to provide enough memory for the Minecraft decompilation process.
org.gradle.jvmargs=-Xmx3G
org.gradle.daemon=true
org.gradle.java.home=/Library/Java/JavaVirtualMachines/jdk1.8.0_251.jdk/Contents/Home

------------------------------------

excerpts from standard out (./gradlew --stacktrace --info --scan --debug runserver):

2:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientInputForwarder] Dispatching close input message: org.gradle.launcher.daemon.protocol.CloseInput@58f485eb
22:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 28: dispatching class org.gradle.launcher.daemon.protocol.CloseInput
22:13:45.081 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClientConnection] thread 1: connection stop
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception.
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong:
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

2:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Try:
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]  Run with --scan to get full insights.
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]
22:13:45.089 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Exception is:
22:13:45.090 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] org.gradle.launcher.daemon.client.DaemonDisappearedException: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

--------------------------------

 

Any clue as to how to resolve this?  I'm new to forge (and to minecraft, for that matter).   I've tried switching org.gradle.daemon to false, and specifying --no-daemon, but neither seems to have any effect.  Nor does removing ~/.gradle.  Running runServer in IDEA also doesn't help.  Interestingly, runclient seems to work fine (I do get the DaemonDisappearedException if I exit the game, however, which I suppose is expected?)

 

Here is the full daemon log: https://www.dropbox.com/s/t30bsi37e7f8j12/daemon-27049.out.log?dl=0

 

 

 

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

You should be setting it to not use the daemon

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Truffacious Tree Puncher

Truffacious

Posted
  • Author
Posted
4 minutes ago, DaemonUmbra said:

You should be setting it to not use the daemon

Thanks for the reply.  Like I mentioned, this doesn't have any effect.  The same thing happens with  

./gradlew --stacktrace --info --scan --debug --no-daemon runserver

and 

org.gradle.daemon=false

My limited understanding is that this flag just controls whether or not the daemon should persist after the build step

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Is there a reason you're running the task instead of using a generated runconfig?

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Truffacious Tree Puncher

Truffacious

Posted
  • Author
Posted
30 minutes ago, DaemonUmbra said:

Is there a reason you're running the task instead of using a generated runconfig?

I typically try to get things working on the command-line before setting up the project in an IDE, and it seemed reasonable based on https://mcforge.readthedocs.io/en/latest/gettingstarted/#building-and-testing-your-mod.  

 

I just now did the following:

1) delete ~/.gradle

2) delete the forge-mdk directory & download it again

3) run ./gradlew genIntellijRuns

4) import the project into Intellij

5) click 'Yes' on the 'Import as Gradle project' question

6) run 'runServer' in intellij.  I get the logs below (this is just the last few lines) - if it'd be helpful I can figure out where the whole thing is stored and upload it

 

[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.ja.FMLJavaModLanguageProvider/SCAN]: Found @Mod class net.minecraftforge.common.ForgeMod with id forge
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Scanning exploded directory /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Scanning exploded target /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning Mod File: /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main path /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main/com/example/examplemod/ExampleMod$RegistryEvents.class
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning Mod File: /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main path /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/classes/java/main/com/example/examplemod/ExampleMod.class
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.ExplodedDirectoryLocator/SCAN]: Exploded directory scan complete /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.lo.mo.Scanner/SCAN]: Scanning /Users/sam/mc1/forge-1.15.2-31.2.0-mdk-2/build/resources/main with language loader javafml
[00:41:19] [pool-2-thread-1/DEBUG] [ne.mi.fm.ja.FMLJavaModLanguageProvider/SCAN]: Found @Mod class com.example.examplemod.ExampleMod with id examplemod

Process finished with exit code 0

 

I'm not sure what "After this has finished edit your Configurations to fix the “module not specified” error by changing selecting your “main” module" means - I don't see that error anywhere.  The main module in runServer is still LaunchTesting

 

Thanks for your help!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept