Citadel

Citadel

129M Downloads

Citadel's Checking Update Makes Server Starting Up Really Time-costing.

Subilan opened this issue ยท 1 comments

commented

Currently I'm running a server with over a hundred mods installed, and Citadel is among them, installed as a dependency. Due to some reason the server cannot reach many remote websites including GitHub, CurseForge, and more. This is not the point as connection issues arise all the time, but there is no reason for some update check to block the process of server starting.

image

Based on the screenshot above and many similar "10-minute time stops" followed by Citadel's "Connection Reset" error message presented in logs, I assume that Citadel is to blame.

It's disappointing to see the server taking 10 extra minutes (guess it's some kind of timeout s setting, which makes the duration between the two log lines in the screenshot strangely precise) to boot. This means whenever the server crashes and tries to start, it must first take 10 minutes to wait for something that is bound to fail to fail.

Why don't I just turn off the update check? I can't. There is no option for this.

It would be ideal if there's a switch for the update check.

Update:
This issue is fixed by the author not long after it's reported. I also made my own modification here in the same period. There are 4 versions available in the Releases which are compatible with 1.16.5, 1.18.2, 1.19.2 and 1.19.4 respectively.

commented

I managed to fix this on my own. Please check https://github.com/seatitanium/citadel-fix-conn if you find this kind of fix useful.