MilkBowl / Vault

Vault of common APIs for Bukkit Plugins
GNU Lesser General Public License v3.0
493 stars 350 forks source link

No SLF4J providers were found #875

Closed AngelDeaD closed 2 years ago

AngelDeaD commented 2 years ago

Hi,

I have random server stoppings (soft crashes), so I decided to clear all my errors from log. I'm using PaperSpigot 1.18.1 #103 build I'm hosting server on i7 6700k with 32GB RAM. This server have Xmx5G. Next error is showing on server start:


[16:45:20] [Server thread/ERROR]: [Vault] [STDERR] SLF4J: No SLF4J providers were found.
[16:45:20] [Server thread/WARN]: Nag author(s): '[cereal, Sleaker, mung3r]' of 'Vault' about their usage of System.out/err.print. Please use your plugin's logger instead (JavaPlugin#getLogger).
[16:45:20] [Server thread/ERROR]: [Vault] [STDERR] SLF4J: Defaulting to no-operation (NOP) logger implementation
[16:45:20] [Server thread/ERROR]: [Vault] [STDERR] SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
[16:45:20] [Server thread/WARN]: [Vault] Loaded class com.earth2me.essentials.api.Economy from Essentials v2.19.3-dev+4-84326cf which is not a depend, softdepend or loadbefore of this plugin.
[16:45:20] [Server thread/INFO]: [Vault] [Economy] Essentials Economy found: Waiting
[16:45:20] [Server thread/INFO]: [Vault] [Permission] SuperPermissions loaded as backup permission system.
[16:45:20] [Server thread/INFO]: [Vault] Enabled Version 1.7.3-b131
Geolykt commented 2 years ago

What the hell is going on in there

AngelDeaD commented 2 years ago

@Geolykt I would like to know that too. Before reporting this problem I tried on clean server with PaperSpigot 1.18.1 build 103, with only Vault plugin, same error. I am no java expert, but I think it has something with log4j fixes.

Sleaker commented 2 years ago

@AngelDeaD this means that the logging provider was removed from the server. We don't bundle a logging plugin with Vault that's why it's complaining about not being able to find one. It's possible that Minecraft/PaperSpigot, in their haste to fix the log4j2 issue broke logging for mods. I don't think there's a good way to fix this error message right now other than by making sure there's an slf4j provider in the server.