[BUG] Very long delay on server start / Cannot start server
DrewSin-4 opened this issue · 26 comments
What happened?
JDA is not updatedBot is missing Server Members Intent causing servers to be unable to startup
Steps to reproduce
- install dcintegration
- start server
- wonder why server isn't starting
Version
- 1.12
- 1.14
- 1.15
- 1.16
Mod version any
Solution:
Enable Server Members Intent on your bot configuration page (the one on https://discord.com/developers/applications )
@DrewSin-4 @ErdbeerbaerLP hi both, this is also affecting us too.
FTB Relevations 1.12.2 dedicated server with 1.1.18 dcintegration plugin.
Log snippet: https://pastebin.com/TqHasLnr
Server hangs at this point and does not continue after 5 minutes. Update check is set to false in the config.
Note: This has worked on a Windows server just fine yesterday, however I just migrated my server to a Linux host (with the Oracle Java Runtime environment jre1.8.0_271) and I can no longer start my server up.
@ErdbeerbaerLP wub woo! ♥
Interestingly, I just looked at that log and it looks like it works just fine.
Can confirm Enigmatica 2 Expert server with DC Integration hanging at the same point
This appears to still be occurring in DiscordIntegration-1.1.19 (MC 1.12) .
Log: https://gist.github.com/shikyo13/2c6ab7d386fb2390800ee862d2733850
Seems to still not be loading passed this:
https://i.imgur.com/X1gGKlZ.png
Log: https://gist.github.com/Yamza/e35a214ccc363c221d84f0caa8ae3041
🤔 Weird. Maybe discord has an bad time currently (even tho discord itself seems responsive)
Hey there! I seem to be experiencing this issue as well.
Im part of a community with 11 servers and all using DC-Integration seem to be having the issue,from 1.12.2 to 1.16.3
Also just tried with different modpacks on 1.12.2 and none seemed to boot with the 1.1.9 fix
From our perspective, more or less when this bug report was started, the servers couldnt launch properly for no reason at all,and all logs end with the JDA as well .
Images are :
-First : Proof of several servers
-Second : last debug lines of the "Revelations" server with 1.1.19 patch
Was any other material needed, im more than happy to provide it
Edit : missworded
🤔 Weird. Maybe discord has an bad time currently (even tho discord itself seems responsive)
Could be but status page reports no major issues https://discordstatus.com/ . Everyone in my community loves this mod, hoping this can be resolved <3 .
reopening this.
[1.16.3] Can you try if this version works (NOTE: Unreleased alpha version with NEW CONFIG (requires re-configuration). New config file is Discord-Integration.toml. I don't seem to have any issues with this one right now.
To install, drop the file into the mods folder and remove the .zip extension (don't unzip!)
dcintegration-2.0.0-1.16.jar.zip
when does github finally support uploading jars directly here?
reopening this.
[1.16.3] Can you try if this version works (NOTE: Unreleased alpha version with NEW CONFIG (requires re-configuration). New config file is Discord-Integration.toml. I don't seem to have any issues with this one right now.
To install, drop the file into the mods folder and remove the .zip extension (don't unzip!)
dcintegration-2.0.0-1.16.jar.zipwhen does github finally support uploading jars directly here?
Regarding this,the server seems to have booted ,is responsive, /say hello works etc... yet im getting this issue several times
Ill try to setup the bot token and channel now
Edit : I do a lot of typos
reopening this.
[1.16.3] Can you try if this version works (NOTE: Unreleased alpha version with NEW CONFIG (requires re-configuration). New config file is Discord-Integration.toml. I don't seem to have any issues with this one right now.
To install, drop the file into the mods folder and remove the .zip extension (don't unzip!)
dcintegration-2.0.0-1.16.jar.zip
when does github finally support uploading jars directly here?Regarding this,the server seems to have booted ,is responsive, /say hello works etc... yet im getting this issue several times
Ill try to setup the bot token and channel now
Edit : I do a lot of typos
ATM6 server running and working,most likely I didnt setup the commands properly,but it's running and chatting!
Update : Discord can see player chat but minecraft chat cant see discord chat,did I miss any configs? aside from commands and this detail everything is fine. And insane lagspikes, Ill keep investigating
This issue also appears to be occurring on version 1.15.2. I've had to remove the Discord Integration config so that my server can start without the mod attempting to connect to Discord. I don't know how much help this'll be, seeing as it's pretty much exactly what everyone else is experiencing, but here's my log: https://hastebin.com/coxubowiji.yaml
I can confirm this is also happening for me in 1.15.2. I'm assuming you're aware and a 1.15.2 release is coming soon.
Discord decided to start enforcing a new bot permission/feature today from the looks of it. I had 3 minecraft servers stop communicating with my bot. I had to go into the bot and enable "SERVER MEMBERS INTENT" in order to fix our issue.
Totally worked with the Server Members Intent. Thanks for adding that, all back to normal for 1.15.2.
Interesting 🤔 I just tried it after recompiling and it works for me there.
In case I changed anything that fixes it, here is another jar file
dcintegration-2.0.0-1.16.jar.zip
But I could confirm, that the commands (including help) are not working right now in that version
Unfortunately I can confirm this bug still works with 1.12.2's newest version you just uploaded.
[18:00:26] [Server thread/INFO] [STDOUT]: [de.erdbeerbaerlp.dcintegration.DiscordIntegration:preInit:412]: Loading mod
[18:00:26] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
[18:00:26] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Defaulting to no-operation (NOP) logger implementation
[18:00:26] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[18:00:27] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
[18:00:27] [Server thread/INFO] [STDERR]: [dcshadow.slf4j.helpers.Util:report:128]: SLF4J: Defaulting to no-operation MDCAdapter implementation.
[18:00:27] [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.
[18:00:28] [Server thread/INFO] [STDERR]: [net.dv8tion.jda.internal.utils.SimpleLogger:write:277]: [Server thread] INFO JDA - Login Successful!
[18:00:28] [JDA MainWS-ReadThread/INFO] [STDERR]: [net.dv8tion.jda.internal.utils.SimpleLogger:write:277]: [JDA MainWS-ReadThread] INFO WebSocketClient - Connected to WebSocket
Server gets stuck with that ^
Discord decided to start enforcing a new bot permission/feature today from the looks of it. I had 3 minecraft servers stop communicating with my bot. I had to go into the bot and enable "SERVER MEMBERS INTENT" in order to fix our issue.
how did you do this?
Discord decided to start enforcing a new bot permission/feature today from the looks of it. I had 3 minecraft servers stop communicating with my bot. I had to go into the bot and enable "SERVER MEMBERS INTENT" in order to fix our issue.
how did you do this?
Im no expert,but...
Edit : its the botom one, im still dumb to this day
Thanks for this fix I referenced to the other mod dev as we were having the same issue. Much appreciated again.
Hi all,
I can confirm after enabling the Presence Intent box the original dcintegration 1.12.2-1.1.18 plugin works again without upgrade. Thank you @AnodeCathode and @BodiwNz for instructions.
@ErdbeerbaerLP even though this ended up being Discords fault, we all really appreciate your fast response in attempting to fix this, you rock 👍
Moving forward, it may be worth putting a new page on the Wiki with the above instructions. I don't think Bodi will mind if you reuse his screenshot. I think then you can mark this issue as resolved.
