Jump to content

1.18.2 -- Seeing a lot of "FATAL" errors in my logs?


sendHalp

Recommended Posts

Hi all,

I am seeing a significant amount of "FATAL" messages in my server logs.   I have no idea what mod or conflict could be causing this, and not sure how to decipher the logs well enough to figure that out.

https://pastebin.com/i0rEiKmd

 

Would anyone be able to look at my latest.log for my Forge server and see if they are able to determine what the heck is going on, and if there is a potential way for me to resolve the issue? Is it even an actual problem, or is it just a scary looking message??

 

Thank you!

Link to comment
Share on other sites

Looks like an issue with Kubejs/Rhino trying to load client classes on the server.

The only one that shows a stracktrace is:

Quote

[03Nov2022 20:28:42.431] [modloading-worker-0/ERROR] [net.minecraftforge.eventbus.EventSubclassTransformer/EVENTBUS]: An error occurred building event handler

java.lang.ClassNotFoundException: com.mojang.blaze3d.vertex.DefaultedVertexConsumer

at cpw.mods.cl.ModuleClassLoader.loadClass(ModuleClassLoader.java:138) ~[securejarhandler-1.0.3.jar:?]

at java.lang.ClassLoader.loadClass(ClassLoader.java:520) ~[?:?]

-- snip --

at dev.latvian.mods.rhino.mod.util.RemappingHelper.getMinecraftRemapper(RemappingHelper.java:98) ~[rhino-forge-1802.2.1-build.248.jar%23140!/:1802.2.1-build.248]

at dev.latvian.mods.kubejs.script.ScriptManager.load(ScriptManager.java:114) ~[kubejs-forge-1802.5.5-build.554.jar%23110!/:1802.5.5-build.554]

at dev.latvian.mods.kubejs.KubeJS.<init>(KubeJS.java:115) ~[kubejs-forge-1802.5.5-build.554.jar%23110!/:1802.5.5-build.554]

at dev.latvian.mods.kubejs.forge.KubeJSForge.<init>(KubeJSForge.java:40) ~[kubejs-forge-1802.5.5-build.554.jar%23110!/:1802.5.5-build.554]

 

I would guess it is just a lot of noise. With Rhino catching and ignoring the errors.

It looks like it loaded the game properly.

 

You can report the log spam to the mod author if you want.

 

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Link to comment
Share on other sites

The fatal errors were definitely scary, but yeah -- the game loaded just fine and I flew around a bit in creative mode mass loading chunks to see if anything would happen.

 

Thanks, that's a big relief that it appears to just be some general log spam. Hopefully the server holds up!

Link to comment
Share on other sites

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.

Announcements



×
×
  • Create New...

Important Information

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