#pluginManager crash when adding any plugin
1 messages · Page 1 of 1 (latest)
Caused by: java.io.FileNotFoundException: ./plugins/plugin-1.0.4.jar (Permission denied)
fix your permissions
I blame Docker
Lavalink creates the folder in the Docker container and then fails to write into said directory ¯_(ツ)_/¯
volumes:
# persist plugins between restarts, make sure to set the correct permissions (user: 322, group: 322)
- ./plugins/:/opt/Lavalink/plugins/
wonder if there's a way to set permissions automatically for local volumes...
since when the folder doesn't exist docker creates it (with 0:0)
eh no, prob not
the only thing we could do in theory is having a startup script call chown on it's own
and switch to a non root user after that
might be handy
I'd rather not chown some user provided directories
if you use a docker volume this issue does not exist
is there any way to show the currently loaded plugins in the console? I'm not sure but something's telling me stuff isn't working, can't search for anything at all using ytsearch: now
plugins do get printed when starting up
interestingly enough my plugins dir is completely empty and Lavalink is not telling me it's downloading anything
2024-04-19T21:01:26.106Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Found plugin 'lavasearch-plugin' version 1.0.0
2024-04-19T21:01:26.107Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Found plugin 'lavasrc-plugin' version ce4f7d9
2024-04-19T21:01:26.107Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Found plugin 'DuncteBot-plugin' version 1.6.3
2024-04-19T21:01:26.107Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Found plugin 'sponsorblock-plugin' version 3.0.0
2024-04-19T21:01:26.107Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Found plugin 'lavalyrics-plugin' version 01bf4e7
2024-04-19T21:01:26.139Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded lavasearch-plugin-1.0.0.jar (20 classes)
2024-04-19T21:01:26.254Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded lavasrc-plugin-ce4f7d9.jar (127 classes)
2024-04-19T21:01:26.259Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded skybot-lavalink-plugin-1.6.3.jar (4 classes)
2024-04-19T21:01:26.334Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded sponsorblock-plugin-3.0.0.jar (90 classes)
2024-04-19T21:01:26.353Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded lavalyrics-plugin-01bf4e7.jar (23 classes)
that's how it usually looks like
folder perms are set to 322 but it won't budge
uid & gid?
yes, that's what I did
o+rwx
ls -ln?
I remade the folder twice and now it decides to work, maybe it'd be nice if it tells you if it can't download? Currently it just does nothing and skips plugin downloading
Thanks for the pointers :)
I mean it did crash
No idea what the other thing was about
I don't know where the crash was coming from
Later on it stopped crashing
instead just did a clean run without plugin downloading at all
2024-04-23T20:39:19.452+02:00 INFO 104071 --- [ main] lavalink.server.Launcher : Starting Launcher v4.0.4 using Java 22 with PID 104071 (/home/alyxia/Documents/gitrepos/Phonograph/Lavalink.jar started by alyxia in /home/alyxia/Documents/gitrepos/Phonograph)
2024-04-23T20:39:19.488+02:00 INFO 104071 --- [ main] lavalink.server.Launcher : No active profile set, falling back to 1 default profile: "default"
2024-04-23T20:39:20.033+02:00 INFO 104071 --- [ main] lavalink.server.Launcher : Started Launcher in 0.858 seconds (process running for 1.129)
2024-04-23T20:39:20.067+02:00 INFO 104071 --- [ main] lavalink.server.Launcher :
compared to when it started working
lavalink | 2024-04-23T18:48:19.645Z INFO 1 --- [ main] lavalink.server.Launcher : Starting Launcher v4.0.4 using Java 18.0.2.1 with PID 1 (/opt/Lavalink/Lavalink.jar started by lavalink in /opt/Lavalink)
lavalink | 2024-04-23T18:48:19.646Z INFO 1 --- [ main] lavalink.server.Launcher : No active profile set, falling back to 1 default profile: "default"
lavalink | 2024-04-23T18:48:20.164Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Downloading [truncated]/plugin-1.0.4.jar
lavalink | 2024-04-23T18:48:20.610Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Downloading [truncated]/lavasearch-plugin-1.0.0.jar
lavalink | 2024-04-23T18:48:21.423Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Downloading [truncated]/lavasrc-plugin-4.0.1.jar
lavalink | 2024-04-23T18:48:22.208Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Downloading [truncated]/sponsorblock-plugin-3.0.0.jar
lavalink | 2024-04-23T18:48:22.840Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded lavasearch-plugin-1.0.0.jar (20 classes)
lavalink | 2024-04-23T18:48:22.899Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded lavasrc-plugin-4.0.1.jar (123 classes)
lavalink | 2024-04-23T18:48:22.934Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded sponsorblock-plugin-3.0.0.jar (90 classes)
lavalink | 2024-04-23T18:48:22.938Z INFO 1 --- [ main] l.server.bootstrap.PluginManager : Loaded plugin-1.0.4.jar (8 classes)
lavalink | 2024-04-23T18:48:23.012Z INFO 1 --- [ main] lavalink.server.Launcher : Started Launcher in 3.708 seconds (process running for 3.973)
oh well
i mean that is not in docker
so the environment is different
possibly your application.yml is different in those 2 setups
it is the same file
can you show more of this fist log?
that's the whole thing
also got an empty one on Docker right after
never mentioned anything about not being able to write to the folder or something, just continues as if nothing happened at all
i'm aware the issue isn't in the config file
.
no it's completely unrelated
Caused by: java.io.FileNotFoundException: https://jitpack.io/com/github/lavalink-devs/lavaplayer-youtube-source/plugin/VERSION/plugin-VERSION.jar
yeah i saw that
I mean. not sure what you expect @opal wing
but at least don't spam unrelated posts
and read errors
(and also comments)
# replace VERSION with the current version as shown by the Releases tab.
soory