Ambari Metrics Collector移动日志目录后启动报错

今天早上集群空间满了，移动Ambari Metrics Collector日志目录后服务启动不了，日志如下：

java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
2018-07-30 11:46:23,686 INFO org.apache.zookeeper.ClientCnxn: Opening socket connection to server node2.bigdata/192.168.0.129:61181. Will not attempt to authenticate using SASL (unknown error)
2018-07-30 11:46:23,686 WARN org.apache.zookeeper.ClientCnxn: Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:712)
        at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
        at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
2018-07-30 11:46:23,788 WARN org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: Possibly transient ZooKeeper, quorum=node2.bigdata:61181, exception=org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /ams-hbase-unsecure/meta-region-server
2018-07-30 11:46:23,788 ERROR org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper: ZooKeeper getData failed after 4 attempts
2018-07-30 11:46:23,788 WARN org.apache.hadoop.hbase.zookeeper.ZKUtil: hconnection-0x72cc7e6f0x0, quorum=node2.bigdata:61181, baseZNode=/ams-hbase-unsecure Unable to get data of znode /ams-hbase-unsecure/meta-region-server
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /ams-hbase-unsecure/meta-region-server
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1212)
        at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getData(RecoverableZooKeeper.java:354)
        at org.apache.hadoop.hbase.zookeeper.ZKUtil.getData(ZKUtil.java:624)
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionState(MetaTableLocator.java:491)
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.getMetaRegionLocation(MetaTableLocator.java:172)
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:611)
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:592)
        at org.apache.hadoop.hbase.zookeeper.MetaTableLocator.blockUntilAvailable(MetaTableLocator.java:565)
        at org.apache.hadoop.hbase.client.ZooKeeperRegistry.getMetaRegionLocation(ZooKeeperRegistry.java:61)
        at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateMeta(ConnectionManager.java:1209)
        at org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1176)
        at org.apache.hadoop.hbase.client.RpcRetryingCallerWithReadReplicas.getRegionLocations(RpcRetryingCallerWithReadReplicas.java:340)
        at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:159)
        at org.apache.hadoop.hbase.client.ScannerCallableWithReplicas.call(ScannerCallableWithReplicas.java:61)
        at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithoutRetries(RpcRetryingCaller.java:211)
        at org.apache.hadoop.hbase.client.ClientScanner.call(ClientScanner.java:327)
        at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:302)
        at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:167)
        at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:162)
        at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:799)
        at org.apache.hadoop.hbase.MetaTableAccessor.fullScan(MetaTableAccessor.java:602)
        at org.apache.hadoop.hbase.MetaTableAccessor.tableExists(MetaTableAccessor.java:366)
        at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:415)
        at org.apache.phoenix.query.ConnectionQueryServicesImpl$13.call(ConnectionQueryServicesImpl.java:2363)

最后找到解决办法：

https://blog.csdn.net/zhouyuanlinli/article/details/79552347

把保存监控数据的/var/lib/ambari-metrics-collector/目录下的三个文件夹checkpoint 、hbase和hbase-tmp删了（可以先备份），重启Metrics Collector就ok了。

rm -rf /var/lib/ambari-metrics-collector/*

原文地址：https://www.cnblogs.com/lianglianggege/p/9389871.html

时间： 2024-10-13 07:11:48

Ambari Metrics Collector移动日志目录后启动报错的相关文章

安装mongodb后启动报错libstdc++

安装mongo后启动报错如下图 显然说是libstdc++.so文件版本的问题,这种一般都是gcc版本太低了 接着查询gcc的版本    strings /usr/lib/libstdc++.so.6 | grep GLIBCXX 接着去找下libstdc++.so新点的版本,一定要根据自己的系统版本去找啊,由于我找错了版本报错系统位数不对 随后下载了一个64位的libstdc++.so.6.0.17的文件,然后软链成libstdc++.so.6 ln -s libstdc++.so.6.0.1

dialogic d300语音卡驱动重装后启动报错问题解决方法

dialogic d300 驱动重装后 dlstart  报错解决 问题描述:dlstart  后如下报错 [[email protected] data]#dlstop Stopping Dialogic Services... Stopping Clocking Daemon:[  纭畾  ] Stopping ClockingServer:[  纭畾  ] Stopping Telephony System Monitor:[  纭畾  ] Stopping Dialogic(R)

mysql故障：重启mysql后启动报错

昨天在试运行环境做系统升级,突然间SSH连接断开,尝试进行连接一直报错,后来重启我的电脑再次进行连接,依然报错,奇怪的测试人员访问公司的liferay界面可以正常访问,后来给部门同事打电话问他们今天有没有对试运行环境做过什么修改,两个同事都说是今天没有对试运行服务器做过任何操作,我自己也没有做过什么操作,后来跟机房的技术支持打电话咨询了一下,技术支持说机房今天也没有做什么操作更没有做什么限制,后来通过登录Xenserver来登录到试运行这台机器,发现没有异常,还特意看了一下SSH的连接数,查看l

mysql数据库迁移目录后slave报错

使用source /sql文件 导入数据库时,文件太大导致了超时. 后面使用scp -r 拷贝整个目录过去,启动slave报错.后来写了个脚本,批量修复: #!/bin/sh/usr/local/mysql/bin/myisamchk -of ./sundiszuzx/$1/usr/local/mysql/bin/myisamchk -r ./sundiszuzx/$1/usr/local/mysql/bin/myisamchk --safe-recover ./sundiszuzx/$1 原文

centos7 安装docker后启动报错

启动docker $ sudo systemctl start docker 报错. 查看状态: $ systemctl status docker.service -l 加 -l 有的行信息很长,打印的时候会省略,加此参数则全部显示. 报错信息: Error starting daemon: SELinux is not supported with the overlay2 graph driver on this kernel. Either boot into a newer kerne

maven引入dubbo包后启动报错

启动后报错内容为: Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [config/spring-context.xml]; nested exception is java.lang.IllegalStateException: Context namespace element 'compo

dbeaver解压后启动报错Could not resolve module: org.eclipse.compare

dbeaver工具对很多数据库都支持,但目前对oracle支持的不是特别好,mysql还行吧,其他的还没怎么使用.下载dbeaver解压版后,点击dbeaver.exe刚开始是会报错误的 在对应的目录下查看日志文件中有 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.compare [17] Unresolved req

RHEL安装rails后启动报错

[[email protected] demo]# rails server/usr/local/rvm/gems/ruby-2.4.1/gems/bundler-1.16.0.pre.2/lib/bundler/runtime.rb:86:in `rescue in block (2 levels) in require': There was an error while trying to load the gem 'uglifier'. (Bundler::GemRequireError

Redis启动报错 linux64目录 /libX11.so.6: undefined symbol: xcb_wait_for_reply64 解决

Redis-desktop-manager一次安装后启动报错经历 解决: 删除libxcb.so.1 删除 RedisDesktop安装目录\lib\libxcb.so.1  文件解决. 详细: 最近因为装黑苹果后固态硬盘分配不合理重装了 debian ,在下载Redis-desktop时发现在github上之前开放的deb版本陆陆续续关闭了,翻了历史版本好久才翻到一个64位的RedisManager(百度云备份以备不时之需:链接: [      https://pan.baidu.com/s/