search

ChosenArchitect / Project-Architect-2

For issue regarding the Project Architect 2 Modpack
10 stars 1 forks source link

Latest.Log size growing due to Log Spamming #267

Open EbolaGaming opened 1 month ago

EbolaGaming commented 1 month ago

While running the forge server for the Project Architect 2 version 4.6 there is a file called "Latest.Log" which is growing to 10GB in size in +/- 1,5 up to 2 hours. Which makes using external server hosting almost impossible due to server crashing after filling it up. I'm unable to make the file read-only due to the hosting not letting me to. Editing and injecting the log4j2 file also doesn't help.

Steps to reproduce the behavior:

  1. Install the Project Architect 2 on the forge server.
  2. Launch the server.
  3. Open the location of the Latest.Log file. (server_folder/logs/latest.log)
  4. Observe the Latest.Log file growing in size.

Expected behavior I'm Expecting the latest.log file to clear itself or not generate 1mb of logs per second.

Screenshots If applicable, add screenshots to help explain your problem. (Use F2 to take a screenshot in-game)

Modpack version -> 4.6 Java Version -> 21 Modpack Launcher Used -> Curse Forge Ram Allocated -> 8192 or 12 288

Additional context Most of the logs compose of Query Listener and Entries that look like below: [09Oct2024 22:37:11.555] [Netty Epoll Server IO #8/DEBUG] [net.minecraft.network.PacketEncoder/PACKET_SENT]: OUT: [PLAY:44] net.minecraft.network.protocol.game.ClientboundMoveEntityPacket$PosRot [09Oct2024 22:37:11.555] [Netty Epoll Server IO #8/DEBUG] [net.minecraft.network.PacketEncoder/PACKET_SENT]: OUT: [PLAY:66] net.minecraft.network.protocol.game.ClientboundRotateHeadPacket

->

IRicTheCoder commented 1 month ago

If you could send me (you can upload it directly to the Github comment) that log file, or at least a part of it since 10GB is a lot, where you have the entries that are most common, I can make a quick fix for you and a fix for the next update. This should be less frequent in 4.7 though, but in any case, please do provide me one of the log files so I can look into what logs we can safely remove from appearing on the log itself.

EbolaGaming commented 1 month ago

#

If you could send me (you can upload it directly to the Github comment) that log file, or at least a part of it since 10GB is a lot, where you have the entries that are most common, I can make a quick fix for you and a fix for the next update. This should be less frequent in 4.7 though, but in any case, please do provide me one of the log files so I can look into what logs we can safely remove from appearing on the log itself.

Sure thing, that would save me from pulling all of my hair out trying to figure it out. I've run the server for some short period of time for it to be smaller. Latest.log provided on google drive because I didn't want to skip any important information inside. https://drive.google.com/file/d/1UZ0k-pXhTNRG3ecqY8r4irY78TsjqKzC/view?usp=sharing

EbolaGaming commented 1 month ago

I've noticed one more relation regarding the latest.log growing. The speed at which the logs are growing appears to depend on how many Users are on the server. When the server is running without anyone on it, the logs do not continue to generate after reaching about 150MB.