Apparent Symlink issue
Closed this issue · 5 comments
PRESET INFO
Names not accurate
All users (read: servers), this scenario (HUB) is connected to one root user (ROOT) through symlinks
All users share the same group (MC) to have full read-write permissions
Used command is sudo ln -s /home/ROOT/plugins/LuckPerms/yaml-storage /home/HUB/plugins/LuckPerms/yaml-storage: Fake folder at HUB location on entry sends to ROOT
Setup works without issues on 4.0.98
Configurations for 4.1.83 has been wiped and updated properly - Works when NOT symlinked breaks upon symlink of "yaml-storage"
As noted in preset, I'm using symlinks between my servers so as to assimilate MySQL but with the perks of YAML which I rely on relatively often, ontop of the perks of the web-editor and ingame changes.
Upon updating it appears as if the plugin can no longer access the database, regardless of my attempts.
Symbolic links should be followed, but LP doesn't implement any specific handling for it. It's all handled by Java's filesystem APIs
Has there been any major changes in how it's handled/stored since then though? I've attempted various things but it appears that 4.1.83 just doesn't like symlinks.
Bungee bootup and shutdown paste: https://paste.md-5.net/tafaqeweka.avrasm