-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misconfiguration issues #241
Comments
It's a safety mechanism that I don't want to disable. If there's a configuration issue with some plugins while others are running, it can lead to internal data synchronization mismatches and corrupted state files. I don't want to cause any corruption and that's why the server is immediately stopped to prevent that from happening. Vane must be able to assume that all of the installed plugins are actually running to work correctly. If you want to temporarily disable a plugin because you have configuration errors, please move the corresponding plugin file out of the plugins folder so that vane knows that it isn't currently in use. |
I see, can there be any eye-catching hints when vane shuts down the server, otherwise no one will know what turned it off |
The error message is quite extensive already. What do you find is unclear exactly? |
Because my server will output a lot of logs when starting, and I used to occasionally encounter errors at startup, but it does not affect normal use, and vane has shut down the server after the error this time, can you not only remind that there is an error at startup, but when performing the shutdown, output a message prompt about whether the shutdown is performed by vane? |
When there is a problem with the configuration file, there will be an error reminder, but after the server starts, the server will be stopped immediately, or it will crash directly, I checked for two days to know that it is a problem, can you change this?
The text was updated successfully, but these errors were encountered: