[BUG] Server won't start
alexvermaning0 opened this issue ยท 12 comments
What happened?
- server crashed after starting.
What should happen?
- starting the server
Steps to reproduce
- start server
- crash
Version
- [check] 1.12
Mod version 1.1.18
Config file
- none
REMOVE YOUR BOT TOKEN BEFORE UPLOADING!!!
Crash report if available (use https://paste.dimdev.org)
-https://pastebin.com/R07dSWww
Additional info
Enigmatica 2 Lite modpack
this solved my same issue, may I ask please that some instructions on how to fix this please be put on the main page for the mod on curse. I am not a newbie but am not a genius either and I did not realize how to fix this until I got to this page.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
+1ing this issue -- dcintegration sporadically bombs on start silently and hangs the FML process, never returns.
This log looks like some other mod still loads an old version of mixin, which is not compatible with this mod.
Try removing 'phosphor' (this mod loads mixin before discord integtation does) and then start the server.
But I might also want to link to #128 if it still doesn't start then
I just updated to your 1.1.19 for 1.12.2 to see if that resolved the issue with modded bots no longer connecting to Discord because of their changed api.
It hung and would not advance. I thought enabling web hooks might help, tried it, still hung.
bot has full perms on the discord too. manage channel, manage web hooks, send/read text.
excerpt from latest.log
https://gist.github.com/kreezxil/0118b9f005a88a1bc52b93c042d09c8c
note it hangs, so there is no crash report
full log (latest) https://gist.github.com/437e8793e8e459ecdd9bbb6534bf5d21
my config:
https://gist.github.com/ef0657dd840450269235bc61229572fe
Server members intent enabled? That is an new requirement. Also webhook mode seems to be broken in 1.1.19
removing the inferior mod didn't change anything, disabling webhook didn't help either.
[07:58:13] [Server thread/INFO] [STDOUT]: [de.erdbeerbaerlp.dcintegration.DiscordIntegration:preInit:412]: Loading mod
[07:58:13] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[07:58:13] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Defaulting to no-operation (NOP) logger implementation
[07:58:13] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[07:58:15] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
[07:58:15] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Defaulting to no-operation MDCAdapter implementation.
[07:58:15] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.
[07:58:15] [Server thread/INFO] [STDERR]: [net.dv8tion.jda.internal.utils.SimpleLogger:write:277]: [Server thread] INFO JDA - Login Successful!
[07:58:15] [JDA MainWS-ReadThread/INFO] [STDERR]: [net.dv8tion.jda.internal.utils.SimpleLogger:write:277]: [JDA MainWS-ReadThread] INFO WebSocketClient - Connected to WebSocket
> list
>
mod list: https://gist.github.com/9dc18ad23f349da6d88f2a87072b38c4
full log: https://gist.github.com/8fdbb0a3e332e06b1cf7996076b6dddd
debug.log: https://gist.github.com/657996540be190cfa1675323fbe393f5
You still did not check if you enabled the server members intent on your bot. It has to be enabled in order for the mod to work
If you still don't know where to change that, open https://discord.com/developers/applications and then open your bot there, go to the bot tab and enable "Server members intent"
If you still don't know where to change that, open https://discord.com/developers/applications and then open your bot there, go to the bot tab and enable "Server members intent"
Thanks, it solved my case of freezing server on startup.