Log file size explodes until server runs out of allocated disk space.

I'm getting on that

be patient bot

there are hundreds of lines that just look like this

[14:59:07] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:07] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:07] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:07] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:08] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:08] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:08] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:08] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:09] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:09] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:09] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:09] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)
[14:59:10] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] pragma busy_timeout=3000
[14:59:10] [Thread-21/TRACE]: [org.sqlite.core.NativeDB] DriverManager [Thread-21] [SQLite EXEC] PRAGMA wal_checkpoint(TRUNCATE)

ngl this post doesn’t make too much sense

latest.log

What are you running
What’s filling up
Who’s your host
What’s your max storage
Etc

answer these please

got it

paper 1.21.4
latest.log
Ethera
140gb (most of this will be emptied once I convert the coreprotect db to another database not on the disk)

the main thing i'm asking about is why latest.log gets so big

I was gone for 1 week

probably because of all of the spam happening inside the file

do you do daily restarts

yes

well tie something todo with SQLITE
if you use anything that has database usage check their systems as one of them might’ve corrupted

Advanced-Portals-Spigot-2.3.3.jar
armorstandeditor-1.21.4-48.1.jar
AxiomPaper-4.0.3-for-MC1.21.4.jar
BannerMaker.jar
CleanroomGenerator-1.2.1.jar
Clearlag.jar
CommandPanels.jar
"CoreProtect-23.2 self-compiled.jar"
DiscordSRV-1.30.0-SNAPSHOT-b0689b0.jar
Dynmap-3.7-beta-8-spigot.jar
Dynmap-WorldGuard-HEAD.jar
EssentialsX-2.21.1-dev+5-dabe687.jar
EssentialsXChat-2.21.1-dev+1-46ba679.jar
floodgate-spigot.jar
FreedomChat-Paper-1.7.2.jar
GEmote-1.0.1.jar
Geyser-Spigot.jar
GSit-2.2.1.jar
HeadDatabase-4.20.4.jar
Leather-Colorizer-1.3.jar
LuckPerms-Bukkit-5.4.153.jar
multiverse-core-4.3.14.jar
multiverse-portals-4.2.3.jar
MyCommand.jar
PlaceholderAPI-2.11.6.jar
PlugManX-2.4.1.jar
ProtocolLib.jar
"TAB v5.0.7.jar"
Vault.jar
ViaBackwards-5.2.1.jar
ViaVersion-5.3.0.jar
VoidGen-2.2.1.jar
worldedit-bukkit-7.3.10.jar
WorldEditSelectionVisualizer-2.1.7.jar
worldguard-bukkit-7.0.13-beta-2-dist.jar
WorldGuardExtraFlags.jar
WorldGuardTabCompletion-1.20.jar

plugin list since i said i was going to send them

I'll fix the essentials mismatch i don't know why that's like that

coreprotect

Yep

makes sense. someone moved a whole city the other day without using -a

seems right

alr well purge the db
purge logs
and start

the

whole thing?