当前位置: 首页 > news >正文

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窗口,就不会出现这个问题了。


http://www.mrgr.cn/news/99066.html

相关文章:

  • leetcode 674. Longest Continuous Increasing Subsequence
  • Unity webgl 获取图片或视频数据
  • leetcode 300. Longest Increasing Subsequence
  • AI分析师
  • 爬虫入门学习
  • 计算机网络八股——HTTP协议与HTTPS协议
  • 杨校老师课堂之C++入门练习题梳理
  • 【刷题Day20】TCP和UDP(浅)
  • Ubuntu20.04下Docker方案实现多平台SDK编译
  • 信创开发:开启信息自主创新、国产替代新时代
  • pgsql中使用jsonb的mybatis-plus和Spring Data JPA的配置
  • MLA(多头潜在注意力)原理概述
  • js day3
  • Redis命令——list
  • 将 DeepSeek 集成到 Spring Boot 项目实现通过 AI 对话方式操作后台数据
  • ospf实验
  • 山东科技大学人工智能原理考试回忆复习资料
  • [密码学实战]基于Python的国密算法与通用密码学工具箱
  • 命令update-alternatives
  • 剑指Offer(数据结构与算法面试题精讲)C++版——day15