-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on Server Start after updating. [1.12.2] #41
Comments
Hi Jophire, thanks for reporting this. I have a few questions to help investigating this:
Thanks! (Also anyone reading this, if you experienced the same issue in your own servers please let me know.) |
Just updated to Forge 14.23.4.2705 and got the crash on server startup Was using 14.23.3.266x (don't remember precisely, maybe 2665) and got no crash |
Hi Insane-96, I don't think this one is from Farseek - it seems your version of Forge (2668 according to your crashlog) isn't compatible with your version of WearableBackpacks. (This is the line that's crashing). Can you try again with the latest Forge? |
Seems like that I've got the error only one time, and I've sent you the wrong crash log. I'll report if happens again. |
There it is https://pastebin.com/7YcBq2Jx crashed again |
It looks like it can't find the Scala libraries normally included with Forge. Are you using a custom launcher? Do you have a complete log files including your list of mods etc.? |
That seemed really strange, I was using a server hosting and 2 days after
it worked again. Maybe they had something nog working on their end
…On Sat, Jul 14, 2018, 23:03 delvr ***@***.***> wrote:
It looks like it can't find the Scala libraries normally included with
Forge. Are you using a custom launcher? Do you have a complete log files
including your list of mods etc.?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#41 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AG2i0EQM5kX1V0alNpJyg17cQ3hK2lVsks5uGly7gaJpZM4UX8oS>
.
|
Thanks for the update Insane-96. If this re-occurs could you please open a separate issue? (The original crash reported by @Jophire is different from yours.) Thanks! |
Sure sorry, I thought it was the same error. |
I recently upgraded to the new Farseek update, as well as streams update.
However, after doing so, launching the server would result in this error:
`Time: 6/3/18 4:59 AM
Description: Exception in server tick loop
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437)
at java.util.HashMap$KeyIterator.next(HashMap.java:1461)
at net.minecraft.entity.EntityTracker.func_72788_a(EntityTracker.java:290)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:779)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:396)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:668)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526)
at java.lang.Thread.run(Thread.java:745)
`
After a bit of sleuthing I pinned the error to this mod.
Some thing to note.
I have only experienced this error when upgrading to the newest version on a server that has ran the previous version. Starting a new world does not cause the crash to occur.
The text was updated successfully, but these errors were encountered: