[BUG] <The startup process should not have to read all files under define>

[Mr-zhou315]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

我碰到一个事件如下：
我的目录权限是非root，但是在进行自定义监控时候，在define目录下面创建了一个root权限的.yml监控示例文件，导致软件无法启动，报错

我删除了这个文件之后，依然无法启动，然后发现还有个隐藏的.yml.swp文件存在，也是root权限，导致无法启动，删除之后软件恢复正常。

建议软件启动可以跳过权限不正确、配置不正确的文件，然后日志中能提示。

Expected Behavior

应该是跳过权限不正确的文件。

Steps To Reproduce

我碰到一个事件如下：
我的目录权限是非root，但是在进行自定义监控时候，在define目录下面创建了一个root权限的.yml监控示例文件，导致软件无法启动，报错

我删除了这个文件之后，依然无法启动，然后发现还有个隐藏的.yml.swp文件存在，也是root权限，导致无法启动，删除之后软件恢复正常。

建议软件启动可以跳过权限不正确、配置不正确的文件，然后日志中能提示。

Environment

HertzBeat version(s):v1.3.1

Debug logs

我碰到一个事件如下：
我的目录权限是非root，但是在进行自定义监控时候，在define目录下面创建了一个root权限的.yml监控示例文件，导致软件无法启动，报错

我删除了这个文件之后，依然无法启动，然后发现还有个隐藏的.yml.swp文件存在，也是root权限，导致无法启动，删除之后软件恢复正常。

建议软件启动可以跳过权限不正确、配置不正确的文件，然后日志中能提示。

Anything else?

无

[hertzbeat]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I come across an event as follows:
My directory permission is non-root, but when performing custom monitoring, a .yml monitoring sample file with root permission was created under the define directory, which caused the software to fail to start and an error was reported

After I deleted this file, it still failed to start, and then I found that there was a hidden .yml.swp file, which was also rooted, which made it impossible to start. After deleting, the software returned to normal.

It is recommended that the software can skip files with incorrect permissions and incorrect configurations when starting the software, and then there will be prompts in the log.

Expected Behavior

It should be skipping files with incorrect permissions.

Steps To Reproduce

I come across an event as follows:
My directory permission is non-root, but when performing custom monitoring, a .yml monitoring sample file with root permission was created under the define directory, which caused the software to fail to start and an error was reported

After I deleted this file, it still failed to start, and then I found that there was a hidden .yml.swp file, which was also rooted, which made it impossible to start. After deleting, the software returned to normal.

It is recommended that the software can skip files with incorrect permissions and incorrect configurations when starting the software, and then there will be prompts in the log.

Environment

Hertz Beat version(s):v1.3.1

Debug logs

I come across an event as follows:
My directory permission is non-root, but when performing custom monitoring, a .yml monitoring sample file with root permission was created under the define directory, which caused the software to fail to start and an error was reported

After I deleted this file, it still failed to start, and then I found that there was a hidden .yml.swp file, which was also rooted, which made it impossible to start. After deleting, the software returned to normal.

It is recommended that the software can skip files with incorrect permissions and incorrect configurations when starting the software, and then there will be prompts in the log.

Anything else?

None

[luoxuanzao]

I want help

[l646505418]

I want help

feel free to start

[luoxuanzao]

Is it to be modified to only record logs, and any exceptions are not thrown

[l646505418]

Is it to be modified to only record logs, and any exceptions are not thrown

From my perspective, you can add logs in your local to track and debug but not push such changes to remote.

[luoxuanzao]

Is it to be modified to only record logs, and any exceptions are not thrown

From my perspective, you can add logs in your local to track and debug but not push such changes to remote.

So is it unnecessary to fix this bug?

[l646505418]

Is it to be modified to only record logs, and any exceptions are not thrown

From my perspective, you can add logs in your local to track and debug but not push such changes to remote.

So is it unnecessary to fix this bug?

I mistake your original meaning, you can do what you want to fix