Skip to content
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

Open
DSLZL opened this issue Mar 7, 2024 · 4 comments
Open

Misconfiguration issues #241

DSLZL opened this issue Mar 7, 2024 · 4 comments

Comments

@DSLZL
Copy link

DSLZL commented Mar 7, 2024

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?

@oddlama
Copy link
Owner

oddlama commented Mar 7, 2024

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.

@DSLZL
Copy link
Author

DSLZL commented Mar 7, 2024

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.这是一种我不想禁用的安全机制。如果某些插件在运行时出现配置问题,则可能导致内部数据同步不匹配和状态文件损坏。我不想造成任何损坏,这就是为什么立即停止服务器以防止这种情况发生的原因。Vane 必须能够假设所有已安装的插件实际上都在运行才能正常工作。

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.如果因为配置错误而想暂时禁用插件,请将相应的插件文件移出 plugins 文件夹,以便 vane 知道它当前未在使用中。

I see, can there be any eye-catching hints when vane shuts down the server, otherwise no one will know what turned it off

@oddlama
Copy link
Owner

oddlama commented Mar 7, 2024

The error message is quite extensive already. What do you find is unclear exactly?

@DSLZL
Copy link
Author

DSLZL commented Mar 8, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants