欢迎来到尧图网

客户服务 关于我们

您的位置:首页 > 教育 > 幼教 > Windows使用SonarQube时启动脚本自动关闭

Windows使用SonarQube时启动脚本自动关闭

2025/9/22 17:57:51 来源:https://blog.csdn.net/Inori_333/article/details/147355830  浏览:    关键词:Windows使用SonarQube时启动脚本自动关闭

一、解决的问题

Windows使用SonarQube时启动脚本自动关闭,并发生报错:

```

ERROR: Elasticsearch did not exit normally - check the logs at E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\logs\sonarqube.log ERROR: Elasticsearch died while starting up, with exit code 1 2025.04.19 20:49:39 WARN app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1 2025.04.19 20:49:39 INFO app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped

```

ERROR: Elasticsearch did not exit normally - check the logs at E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\logs\sonarqube.log
ERROR: Elasticsearch died while starting up, with exit code 1
2025.04.19 20:49:39 WARN  app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 1
2025.04.19 20:49:39 INFO  app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped

二、问题产生的原因

查看./logs/es.log,内容如下:

2025.04.19 20:55:00 ERROR es[][o.e.b.Elasticsearch] fatal exception while booting Elasticsearch
java.lang.IllegalStateException: failed to obtain node locks, tried [E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\data\es8]; maybe these locations are not writable or multiple nodes were started on the same data path?at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:294) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.node.NodeConstruction.validateSettings(NodeConstruction.java:533) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.node.NodeConstruction.prepareConstruction(NodeConstruction.java:277) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.node.Node.<init>(Node.java:200) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:240) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:240) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:75) ~[elasticsearch-8.16.3.jar:?]
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock held by another program: E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\data\es8\node.lockat org.apache.lucene.store.NativeFSLockFactory.obtainFSLock(NativeFSLockFactory.java:117) ~[lucene-core-9.12.0.jar:?]at org.apache.lucene.store.FSLockFactory.obtainLock(FSLockFactory.java:43) ~[lucene-core-9.12.0.jar:?]at org.apache.lucene.store.BaseDirectory.obtainLock(BaseDirectory.java:44) ~[lucene-core-9.12.0.jar:?]at org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:232) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.env.NodeEnvironment$NodeLock.<init>(NodeEnvironment.java:207) ~[elasticsearch-8.16.3.jar:?]at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:286) ~[elasticsearch-8.16.3.jar:?]... 6 more

发现ElasticSearch无法启动,直接原因是数据目录的锁文件(node.lock)被占用或权限不足

三、解决方案

删除发生占用的锁文件和数据,需要去./data目录下找,还有./temp文件夹

# 删除锁文件和数据
E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\data\es8
# 清理临时文件(可选)
E:\Inori_Code\Year3\SE\sonarqube-25.2.0.102705\sonarqube-25.2.0.102705\temp

之后每次想结束SonarQube服务时,先在cmd里Ctrl+C结束进程,等待进程有序关闭后再关闭cmd窗口,就不会出现这个问题了。

版权声明:

本网仅为发布的内容提供存储空间,不对发表、转载的内容提供任何形式的保证。凡本网注明“来源:XXX网络”的作品,均转载自其它媒体,著作权归作者所有,商业转载请联系作者获得授权,非商业转载请注明出处。

我们尊重并感谢每一位作者,均已注明文章来源和作者。如因作品内容、版权或其它问题,请及时与我们联系,联系邮箱:809451989@qq.com,投稿邮箱:809451989@qq.com

热搜词