AuthmeReload cannot contact sql database #2180
Labels
Status: can't reproduce
Marks issues that can't be reproduced by the development team.
Status: no answer
Type: bug
Comments
|
Same problem here, running fresh BungeeCord-Spigot server, i have a forum running on the background with the same connection info, but AuthMeReloaded fails to connect to the database. `
Spigot Version: 1.16.2 |
|
I've found out the problem, AuthMeReloaded does not work with mysql versions higher than 5.7. |
This is not the complete server log |
this is probably a different issue, please take a look at #1779 |
sgdc3
added
the
Status: awaiting answer
Can you reproduce the issue with the latest Spigot/Paper build and latest AuthMe build (no other plugins)? |
|
Currently server is running MariaDB 10, spigot, no other plugins, and i spent 2h reconfiguring my mysql and trying ~100 diffrent methods to get it to work, but it will not connect. Then i discovered, that i need to downgrade my database from the forums. I'm waiting on my host provider to downgrade my OS first from Debian 9 to Debian 8 due to another server issue with debian 9. But yeah, Debian 9 with MariaDB 10 will not let you connect to the mysql database. |
|
Here, since Debian 9 has MariaDB 10 as default now, you should consider adding mariadb support to the plugin. |
|
I use MariaDB 10.4 myself without any issue, this is so strange |
|
Hmm, I have same or at least very similar issue on MariaDB 10.4. Connection worked about ok before update to 5.6.0-beta1 but with the update I got: I would also like to point out that at the end of the log systemd reports that execution was successful. But it "crashed" or at least the authme component did. This was caused by having the process end with exit code 0. But it should by no means never ever exit with 0 when AuthMeReloaded kills the server because then I do not have a running server. I have a dead server. Full logs: But as you can see I run there quite a bit of plugins so I took latest paper server number 261 and recreated minimal environment with only |
|
Cklosing due to inactivity, unable to reproduce, also update asap to the latest dev-build if you are using the beta1 pre-release |
sgdc3
added
Status: can't reproduce
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before reporting an issue make sure you are running the latest build of the plugin and checked for duplicate issues!
What behaviour is observed:
Plugin shut down the server and does not work properly if I set stopServer to false.
What behaviour is expected:
AuthMeReload works and ask player to login.
Steps/models to reproduce:
I just upgrade my server from 1.12.2 to 1.16.2 and reset config.yml then this happens.
Plugin list:
AdvancedBan AdvancedCleaner AuthMeReload BossShoopPro Essentials HolographicDisplays PermissionPlus PlaceholderAPI PlayerControl ProteocolLib QuickShop Residence SimpleAntiMobLag SuperVanish TimeMessage Vault WorldEdit WorldMobLimiter MySkin OpenInv
Environment description
Standalone sipgot 1.16.2, SQLite
AuthMe build number:
I tried both AuthMe-5.4.0 and AuthMe-5.6.0-beta1
Error Log:
[AuthMe] Enabling AuthMe v5.6.0-beta1-b2226
[17:18:43] [Server thread/INFO]: [AuthMe] SQLite Setup finished
[17:18:43] [Server thread/INFO]: [AuthMe] Hooked into Vault!
[17:18:43] [Server thread/INFO]: [AuthMe] Hooked successfully into Essentials
[17:18:43] [Server thread/INFO]: [AuthMe] Hooked successfully into Multiverse-Core
[17:18:43] [Server thread/WARN]: [AuthMe] Aborting initialization of AuthMe: [InjectorReflectionException]: Could not invoke constructor of class 'class fr.xephi.authme.command.CommandHandler'
[17:18:43] [Server thread/WARN]: [AuthMe] THE SERVER IS GOING TO SHUT DOWN AS DEFINED IN THE CONFIGURATION!
Configuration:
Default config
The text was updated successfully, but these errors were encountered: