[Bug] 1.3.6服务运行突然configNode从Runing变成了disabled 没有原因日志

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Version

1.3.6

### Describe the bug and provide the minimal reproduce step

1.3.6服务运行突然configNode从Runing变成了disabled 没有原因日志

### What did you expect to see?

正常运行，或者能看到dataNode由Runing变成了disabled的原因

### What did you see instead?

突然dataNode从Runing变成了disabled

### Anything else?

_No response_

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start by reproducing the ConfigNode or DataNode transition from Running to disabled on IoTDB 1.3.6 and inspect the surrounding state-change and logging paths. Trace the transition far enough to identify why the service becomes disabled; done means the cause is recorded clearly in logs and the behavior is covered by a reproducible verification.

Written by the indexing model from the issue text.