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

1.12.2 Server keeps crashing

Zewy2660

By Zewy2660
in Support & Bug Reports

 Share

Recommended Posts

Zewy2660 Tree Puncher

Zewy2660

Posted
Posted

I have made a 1.12.2 server with the following mods:

Baubles
Backpack
Damage Indicators
Voxelmap
Battle towers
Portal gun
Ender Storage
Mo Creatures
Iron chest
Buildcraft
Buildcraft compat
Treecap
Thaumicenergistics
Morph
Libraries
Ichunutil
Biomes O Plenty
Bibliocraft
Tinkers Construct
Mantle
Optifine
Ic2
Extreme Reactors
Ae2
Ae2 stuff
Bdlib
Galacticraft Core
Galacticraft Planets
Micdoodle Core
Twilight Forest
Better FPS
Pam's Harvest Craft
AppleCore
Spice Of Life
Thermal Dynamics
Thermal Expansion
Thermal Foundation
Chicken Chunks
CoFHCore
CoFH World
Code Chicken Lib
Vanilla fix
Hwyla
Biomes you'll go
Zero Core
Thaumcraft
Thaumic JEI
JEI
Just Enough Resources
Just Enough Energisticd
Just Enough Harvest Craft
Tinkers JEI
Just Enough Reactors
Familiar fauna
Aether
Gravestone
Iron tanks
Deconstruction Table

 

As the forge server jar file starts up it runs for a few seconds and then proceeds to crash

Here is the crash report and log files generated after the crash,

Crash Report: https://pastebin.com/TGp6PHsg

"latest" file from log folder: https://pastebin.com/Ah1JidVN

"debug" file from log folder: https://pastebin.com/GSxGFjmr

 

 

Link to comment
Share on other sites
Ruchia Stone Miner

Ruchia

Posted
Posted (edited)

The official source for VoxelMap (and exact version) is https://minecraft.curseforge.com/projects/voxelmap/files/2727117
(just posting this in between)
The other error indicates your forge version is too low.

Edit: to be exact. It says: requires forge 14.23.5.2781,
And you're using forge 14.23.5.2768
Diesieben suggests updating with that message.

Edited by Ruchia
Link to comment
Share on other sites
Zewy2660 Tree Puncher

Zewy2660

Posted
  • Author
Posted
21 minutes ago, Ruchia said:

The official source for VoxelMap (and exact version) is https://minecraft.curseforge.com/projects/voxelmap/files/2727117
(just posting this in between)
The other error indicates your forge version is too low.

Edit: to be exact. It says: requires forge 14.23.5.2781,
And you're using forge 14.23.5.2768
Diesieben suggests updating with that message.

so i used that exact forge build and get the following reports

 

crash-2019-06-26_14.13.19-server.txt debug.log latest.log

Link to comment
Share on other sites
Zewy2660 Tree Puncher

Zewy2660

Posted
  • Author
Posted
5 hours ago, diesieben07 said:

Remove VoxelMap, it's apparently broken. Also report this to the author. 

java -Xmx8096M -Xms8096M -jar forge-1.12.2-14.23.5.2781-universal.jar nogui
PAUSE

So i started running the forge file through a run.bat file using the text above and it proceeds to crash. I removed voxelmap from the mods and the console seems to freeze.

 

crash-2019-06-26_19.50.02-server.txt debug.log latest.log

Link to comment
Share on other sites
Zewy2660 Tree Puncher

Zewy2660

Posted
  • Author
Posted (edited)
23 minutes ago, Zewy2660 said: 

java -Xmx8096M -Xms8096M -jar forge-1.12.2-14.23.5.2781-universal.jar nogui
PAUSE

So i started running the forge file through a run.bat file using the text above and it proceeds to crash. I removed voxelmap from the mods and the console seems to freeze.

 

crash-2019-06-26_19.50.02-server.txt 21.2 kB · 0 downloads debug.log 849.34 kB · 0 downloads latest.log 89.57 kB · 0 downloads

So i found at that the problem was with the damage indicator mod so i removed it but now the server console seems to stop on its own after running a few a commands.There is also no new crash reports being generated

latest(1).log

Edited by Zewy2660
Forgot some information
Link to comment
Share on other sites
Ruchia Stone Miner

Ruchia

Posted
Posted

That happens when you close the server manually, not a command.
There is no indication in your latest log of you ordering it to stop running.
When you use nogui as you did, the server is run only in your terminal (cmd), If you close the terminal (cmd), the server will also stop running. (Actually, since you use a batch to launch the server, you will always get a terminal window that processes the server, so keeping this open is a must to keep the server running.)

If you didn't close the server yourself, make sure you have that much RAM available for anything. Maybe you OS closed the application as a security measure due to lack of available RAM.
For the little amount of mods you run, your server doesn't need 8G. The client generally needs more RAM than the server and I can run All The Mods 3 Remix on the client with 6.5G, which has 330 mods. I suggest lowering your RAM allocation, on both your server and client. (especially xms, since that is the minimum you make available.)

If you have 16GB RAM installled, you need to keep in mind that Windows needs 4GB RAM. Your browser also needs RAM. If you set both client and server to use at least 8GB RAM, your Windows will close those. (there is a way to work around this, with virtual RAM, but that isn't a very healthy way to use your hard drives.)

example for client: 

-Xmx6144M -Xms2048M

example for server: 

java -Xmx4096M -Xms1024M -jar forge-1.12.2-14.23.5.2781-universal.jar nogui

(You can adjust the RAM based on the number you actually need. In case it lags too much, you can bring xms closer to xmx. This lowers the time needed for garbage collection and therefore reduces latency (due to processing) issues.)

In these examples I assigned 4GB to your server (at max) and 6GB (at max) to your client, but with that little mods, you likely require less RAM.

About Toro's Damage Indicators. It's known to cause problems. The mod hasn't been updated (for the public) since 2017. It is a client sided mod, but even when people know this it sometimes causes issues anyway.

Link to comment
Share on other sites
Zewy2660 Tree Puncher

Zewy2660

Posted
  • Author
Posted
16 minutes ago, Ruchia said:

That happens when you close the server manually, not a command.
There is no indication in your latest log of you ordering it to stop running.
When you use nogui as you did, the server is run only in your terminal (cmd), If you close the terminal (cmd), the server will also stop running. (Actually, since you use a batch to launch the server, you will always get a terminal window that processes the server, so keeping this open is a must to keep the server running.)

If you didn't close the server yourself, make sure you have that much RAM available for anything. Maybe you OS closed the application as a security measure due to lack of available RAM.
For the little amount of mods you run, your server doesn't need 8G. The client generally needs more RAM than the server and I can run All The Mods 3 Remix on the client with 6.5G, which has 330 mods. I suggest lowering your RAM allocation, on both your server and client. (especially xms, since that is the minimum you make available.)

If you have 16GB RAM installled, you need to keep in mind that Windows needs 4GB RAM. Your browser also needs RAM. If you set both client and server to use at least 8GB RAM, your Windows will close those. (there is a way to work around this, with virtual RAM, but that isn't a very healthy way to use your hard drives.)

example for client: 


-Xmx6144M -Xms2048M

example for server: 


java -Xmx4096M -Xms1024M -jar forge-1.12.2-14.23.5.2781-universal.jar nogui

(You can adjust the RAM based on the number you actually need. In case it lags too much, you can bring xms closer to xmx. This lowers the time needed for garbage collection and therefore reduces latency (due to processing) issues.)

In these examples I assigned 4GB to your server (at max) and 6GB (at max) to your client, but with that little mods, you likely require less RAM.

About Toro's Damage Indicators. It's known to cause problems. The mod hasn't been updated (for the public) since 2017. It is a client sided mod, but even when people know this it sometimes causes issues anyway.

SO we decreased the ram of the .bat file  but it seems to stop at [Thread-18/INFO] [THAUMCRAFT]: Stopping aura thread for dim 7 and doesnt load anything

Link to comment
Share on other sites
Ruchia Stone Miner

Ruchia

Posted
Posted
1 minute ago, Zewy2660 said:

SO we decreased the ram of the .bat file  but it seems to stop at [Thread-18/INFO] [THAUMCRAFT]: Stopping aura thread for dim 7 and doesnt load anything

If it is not closing the server, it's probably normal. Try and see if you can execute commands, if you want to be certain. example: say test
If there is no one running in the server, it usually unloads dims. The same goes for when people are not present in a certain dim, it usually unloads that dim. It will load the dim up again when someone enters, so no need to worry about that.

Link to comment
Share on other sites
Zewy2660 Tree Puncher

Zewy2660

Posted
  • Author
Posted
14 minutes ago, Ruchia said:

If it is not closing the server, it's probably normal. Try and see if you can execute commands, if you want to be certain. example: say test
If there is no one running in the server, it usually unloads dims. The same goes for when people are not present in a certain dim, it usually unloads that dim. It will load the dim up again when someone enters, so no need to worry about that.

Thanksss it worked

 

Link to comment
Share on other sites
  • 3 months later...
McBlockz91 Newbie

McBlockz91

Posted
Posted

Sorry to drudge up an old thread, but was looking for a fix for server crash related to installing Voxelmap on bisect server with forge modpack installed. I added Voxelmap and Effortless Building to my 1.12.2 client and server, but upon restarting the server it would crash and abort restart attempts. Removed Voxelmap from server, but not client, and everything is running smoothly. Seems like it's running with full function without the need to install in bisect at all.

Link to comment
Share on other sites
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

Please do not necro old threads, if you have an issue make your own and provide logs.

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]

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing


×
×
  • Create New...

Important Information

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

  I accept