ubuntu下vscode cpptools启动失败问题(Launching server using command cpptools failed.)

本文指导用户检查并确保Visual Studio Code中cpptools及其服务程序cpptools-srv具有正确的执行权限,这对于C/C++代码编辑器插件的正常运行至关重要。

去cpptools的安装目录下,确认cpptools和cpptools-srv这两个程序有可执行权限。

root@ubuntu-virtual-machine:/opt# $ZOOKEEPER_HOME/bin/zkServer.sh status ZooKeeper JMX enabled by default Using config: /app/apache-zookeeper-3.5.8-bin/bin/../conf/zoo.cfg Client port found: 2181. Client address: localhost. Mode: follower root@ubuntu-virtual-machine:/opt# jps 8532 Jps 2759 QuorumPeerMain 3001 NameNode 3403 SecondaryNameNode 3167 DataNode root@ubuntu-virtual-machine:/opt# start-hbase.sh start-hbase.sh:未找到命令 root@ubuntu-virtual-machine:/opt# vim /etc/profile root@ubuntu-virtual-machine:/opt# scp /etc/profile root@slave1:/etc/ profile 100% 1003 213.4KB/s 00:00 root@ubuntu-virtual-machine:/opt# scp /etc/profile root@slave2:/etc/ profile 100% 1003 157.7KB/s 00:00 root@ubuntu-virtual-machine:/opt# source /etc/profile root@ubuntu-virtual-machine:/opt# start-hbase.sh SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/app/hbase-2.4.11/lib/client-facing-thirdparty/slf4j-reload4j-1.7.33.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/app/hadoop3.3/share/hadoop/common/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory] running master, logging to /app/hbase-2.4.11/logs/hbase-root-master-ubuntu-virtual-machine.out slave2: running regionserver, logging to /app/hbase-2.4.11/bin/../logs/hbase-root-regionserver-ubuntu-virtual-machine.out slave1: running regionserver, logging to /app/hbase-2.4.11/bin/../logs/hbase-root-regionserver-ubuntu-virtual-machine.out master: running regionserver, logging to /app/hbase-2.4.11/bin/../logs/hbase-root-regionserver-ubuntu-virtual-machine.out root@ubuntu-virtual-machine:/opt# jps 28180 HRegionServer 2759 QuorumPeerMain 27959 HMaster 3001 NameNode 3403 SecondaryNameNode 28301 Jps 3167 DataNode root@ubuntu-virtual-machine:/opt# jps 28324 Jps 28180 HRegionServer 2759 QuorumPeerMain 27959 HMaster 3001 NameNode 3403 SecondaryNameNode 3167 DataNode root@ubuntu-virtual-machine:/opt# jps 28180 HRegionServer 2759 QuorumPeerMain 27959 HMaster 3001 NameNode 28969 Jps 3403 SecondaryNameNode 3167 DataNode root@ubuntu-virtual-machine:/opt# jps 28180 HRegionServer 2759 QuorumPeerMain 3001 NameNode 3403 SecondaryNameNode 29405 Jps 3167 DataNode root@ubuntu-virtual-machine:/opt# jps 29555 Jps 28180 HRegionServer 2759 QuorumPeerMain 3001 NameNode 3403 SecondaryNameNode 3167 DataNode root@ubuntu-virtual-machine:/opt# $ ZOOKEEPER_HOME/bin/zkServer.sh status $:未找到命令 root@ubuntu-virtual-machine:/opt# $ZOOKEEPER_HOME/bin/zkServer.sh status ZooKeeper JMX enabled by default Using config: /app/apache-zookeeper-3.5.8-bin/bin/../conf/zoo.cfg Client port found: 2181. Client address: localhost. Mode: follower root@ubuntu-virtual-machine:/opt# hbase hbck SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/app/hbase-2.4.11/lib/client-facing-thirdparty/slf4j-reload4j-1.7.33.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/app/hadoop3.3/share/hadoop/common/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Reload4jLoggerFactory] 2025-06-20 09:03:53,022 INFO [main] zookeeper.RecoverableZooKeeper: Process identifier=hbase Fsck connecting to ZooKeeper ensemble=master:2181,slave1:2181,slave2:2181 2025-06-20 09:03:53,091 INFO [main] zookeeper.ZooKeeper: Client environment:zookeeper.version=3.5.7-f0fdd52973d373ffd9c86b81d99842dc2c7f660e, built on 02/10/2020 11:30 GMT 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:host.name=ubuntu-virtual-machine 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.version=1.8.0_202 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.vendor=Oracle Corporation 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.home=/app/jdk1.8.0_202/jre 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: nt-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-common-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-common-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-timeline-pluginstorage-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-web-proxy-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-services-core-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-router-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-resourcemanager-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-sharedcachemanager-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-registry-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-tests-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-applications-mawo-core-3.3.6.jar:/app/hadoop3.3/share/hadoop/yarn/hadoop-yarn-server-applicationhistoryservice-3.3.6.jar:/app/hadoop3.3/conf 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.library.path=/app/hadoop3.3/lib/native 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.io.tmpdir=/tmp 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:java.compiler=<NA> 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:os.name=Linux 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:os.arch=amd64 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:os.version=5.4.0-84-generic 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:user.name=root 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:user.home=/root 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:user.dir=/opt 2025-06-20 09:03:53,092 INFO [main] zookeeper.ZooKeeper: Client environment:os.memory.free=48MB 2025-06-20 09:03:53,094 INFO [main] zookeeper.ZooKeeper: Client environment:os.memory.max=961MB 2025-06-20 09:03:53,094 INFO [main] zookeeper.ZooKeeper: Client environment:os.memory.total=59MB 2025-06-20 09:03:53,112 INFO [main] zookeeper.ZooKeeper: Initiating client connection, connectString=master:2181,slave1:2181,slave2:2181 sessionTimeout=90000 watcher=org.apache.hadoop.hbase.zookeeper.PendingWatcher@3d246ea3 2025-06-20 09:03:53,188 INFO [main] common.X509Util: Setting -D jdk.tls.rejectClientInitiatedRenegotiation=true to disable client-initiated TLS renegotiation 2025-06-20 09:03:53,234 INFO [main] zookeeper.ClientCnxnSocket: jute.maxbuffer value is 4194304 Bytes 2025-06-20 09:03:53,268 INFO [main] zookeeper.ClientCnxn: zookeeper.request.timeout value is 0. feature enabled= HBaseFsck command line options: 2025-06-20 09:03:53,324 INFO [main] util.HBaseFsck: Launching hbck 2025-06-20 09:03:53,410 INFO [main-SendThread(master:2181)] zookeeper.ClientCnxn: Opening socket connection to server master/192.168.60.136:2181. Will not attempt to authenticate using SASL (unknown error) 2025-06-20 09:03:53,533 INFO [main-SendThread(master:2181)] zookeeper.ClientCnxn: Socket connection established, initiating session, client: /192.168.60.136:43364, server: master/192.168.60.136:2181 2025-06-20 09:03:53,629 INFO [main-SendThread(master:2181)] zookeeper.ClientCnxn: Session establishment complete on server master/192.168.60.136:2181, sessionid = 0x1000012ace40001, negotiated timeout = 40000 2025-06-20 09:03:54,207 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22] zookeeper.ZooKeeper: Initiating client connection, connectString=master:2181,slave1:2181,slave2:2181 sessionTimeout=90000 watcher=org.apache.hadoop.hbase.zookeeper.ReadOnlyZKClient$$Lambda$18/649052050@6792b5a9 2025-06-20 09:03:54,210 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22] zookeeper.ClientCnxnSocket: jute.maxbuffer value is 4194304 Bytes 2025-06-20 09:03:54,219 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22] zookeeper.ClientCnxn: zookeeper.request.timeout value is 0. feature enabled= 2025-06-20 09:03:54,233 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22-SendThread(slave2:2181)] zookeeper.ClientCnxn: Opening socket connection to server slave2/192.168.60.140:2181. Will not attempt to authenticate using SASL (unknown error) 2025-06-20 09:03:54,240 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22-SendThread(slave2:2181)] zookeeper.ClientCnxn: Socket connection established, initiating session, client: /192.168.60.136:47330, server: slave2/192.168.60.140:2181 2025-06-20 09:03:54,520 INFO [ReadOnlyZKClient-master:2181,slave1:2181,slave2:2181@0x1fde5d22-SendThread(slave2:2181)] zookeeper.ClientCnxn: Session establishment complete on server slave2/192.168.60.140:2181, sessionid = 0x300003130b30000, negotiated timeout = 40000 2025-06-20 09:03:54,642 WARN [main] client.ConnectionImplementation: Retrieve cluster id failed java.util.concurrent.ExecutionException: org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /hbase/hbaseid at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895) at org.apache.hadoop.hbase.client.ConnectionImplementation.retrieveClusterId(ConnectionImplementation.java:600) at org.apache.hadoop.hbase.client.ConnectionImplementation.<init>(ConnectionImplementation.java:313) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.apache.hadoop.hbase.client.ConnectionFactory.lambda$createConnection$0(ConnectionFactory.java:230) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1899) at org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:347) at org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:228) at org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:128) at org.apache.hadoop.hbase.util.HBaseFsck.connect(HBaseFsck.java:578) at org.apache.hadoop.hbase.util.HBaseFsck.exec(HBaseFsck.java:3800) at org.apache.hadoop.hbase.util.HBaseFsck$HBaseFsckTool.run(HBaseFsck.java:3624) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:82) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:97) at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3612) Caused by: org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /hbase/hbaseid at org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException.create(KeeperException.java:118) at org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException.create(KeeperException.java:54) at org.apache.hadoop.hbase.zookeeper.ReadOnlyZKClient$ZKTask$1.exec(ReadOnlyZKClient.java:174) at org.apache.hadoop.hbase.zookeeper.ReadOnlyZKClient.run(ReadOnlyZKClient.java:339) at java.lang.Thread.run(Thread.java:748) 2025-06-20 09:03:59,991 INFO [main] client.RpcRetryingCallerImpl: Call exception, tries=6, retries=16, started=4330 ms ago, cancelled=false, msg=java.io.IOException: org.apache.hadoop.hbase.shaded.org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /hbase/master, details=, see https://s.apache.org/timeout
06-21
### Clang Language Server 连接问题分析 Clang Language Server 是基于 clangd 的语言服务器协议实现,用于提供代码补全、跳转定义等功能。如果遇到 `spawn EACCES` 错误,则通常表示权限不足或者文件路径存在问题。 以下是可能的原因及解决方案: #### 1. 权限不足 当尝试运行 `clangd` 命令时,如果没有足够的权限访问某些资源(如日志目录或缓存),可能会触发此错误。可以通过以下方式解决: - 确保当前用户具有执行 `clangd` 的权限。 - 如果安装的是全局版本的 `clangd`,可以尝试通过 `sudo chmod +x /path/to/clangd` 修改可执行权限[^3]。 #### 2. 文件路径问题 `EACCES` 可能是因为指定的工作目录或配置文件不可访问。检查以下几点: - 验证工作目录是否存在并可读写。 - 使用绝对路径调用 `clangd` 并确认其位置正确。 ```bash which clangd ``` 如果返回为空,则说明未正确安装或 PATH 中缺少该工具。 #### 3. 编辑器插件配置不匹配 有时编辑器中的 LSP 插件未能正确定位到 `clangd` 或者传递参数有误。建议重新验证插件设置: - 对于 VSCode 用户,打开 settings.json 并确保如下字段存在且指向正确的二进制文件: ```json { "clangd.path": "/usr/bin/clangd" } ``` #### 4. 日志调试 启用更详细的日志可以帮助定位具体原因。增加 `-log=verbose` 参数来获取更多信息: ```bash clangd --background-index -j=4 --compile-commands-dir=. --query-driver="*" -log=verbose ``` 查看输出的日志以进一步排查是否有其他潜在依赖缺失等问题[^4]。 --- ### 解决方案总结 综合以上情况,推荐按照下列顺序操作: 1. 检查系统中是否已成功安装 `clangd`; 2. 调整相关文件夹和程序本身的访问控制列表ACLs; 3. 更新IDE内部关于如何调用外部服务的具体选项; 4. 利用内置开关功能记录更多细节以便后续深入研究根本诱因所在之处; ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值