查看: 9506|回复: 2
【求助】cloudera-scm-server启动后就吊死
主题帖子积分
新手上路, 积分 12, 距离下一级还需 38 积分
新手上路, 积分 12, 距离下一级还需 38 积分
问题现象：
CM-WEB页面打开失败，
初步定为是： 怀疑/etc/cloudera-scm-server 目录被误删，导致日志中无法找到 Could not find or parse database configuration file: 'db.properties'.
[root@cloud0 /]# service cloudera-scm-server status
cloudera-scm-server dead but pid file exists
查看日志：
[root@cloud0 log]# cd cloudera-scm-server
[root@cloud0 cloudera-scm-server]# ls -rta
db.log&&cloudera-scm-server.log.1&&cloudera-scm-server.log&&.&&..&&cloudera-scm-server.out
[root@cloud0 cloudera-scm-server]# ls
cloudera-scm-server.log&&cloudera-scm-server.log.1&&cloudera-scm-server.out&&db.log
[root@cloud0 cloudera-scm-server]# more cloudera-scm-server.out
JAVA_HOME=/usr/java/jdk1.7.0_67-cloudera
log4j:ERROR Could not read configuration file from URL [file:/etc/cloudera-scm-server/log4j.properties].
java.io.FileNotFoundException: /etc/cloudera-scm-server/log4j.properties (No such file or directory)
& && &&&at java.io.FileInputStream.open(Native Method)
& && &&&at java.io.FileInputStream.&init&(FileInputStream.java:146)
& && &&&at java.io.FileInputStream.&init&(FileInputStream.java:101)
& && &&&at sun.net.(FileURLConnection.java:90)
& && &&&at sun.net.(FileURLConnection.java:188)
& && &&&at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:524)
& && &&&at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:483)
& && &&&at org.apache.log4j.LogManager.&clinit&(LogManager.java:127)
& && &&&at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:73)
& && &&&at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:242)
& && &&&at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254)
& && &&&at com.cloudera.server.cmf.Main.&clinit&(Main.java:144)
log4j:ERROR Ignoring configuration file [file:/etc/cloudera-scm-server/log4j.properties].
log4j:WARN No appenders could be found for logger (com.cloudera.server.cmf.Main).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See
for more info.
Exception in thread &main& org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.cloudera.serv
er.cmf.TrialState': Cannot resolve reference to bean 'entityManagerFactoryBean' while setting
nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean t
hrew exceptio nested exception is java.lang.RuntimeException: Could not find or parse database configuration fi
le: 'db.properties'.
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:3
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver
.java:106)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableB
eanFactory.java:1003)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBe
anFactory.java:907)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFact
ory.java:485)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactor
y.java:456)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
& && &&&at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.
& && &&&at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext
.java:895)
& && &&&at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
& && &&&at com.cloudera.server.cmf.Main.bootstrapSpringContext(Main.java:344)
& && &&&at com.cloudera.server.cmf.Main.&init&(Main.java:220)
& && &&&at com.cloudera.server.cmf.Main.main(Main.java:194)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': Factor
yBean threw exceptio nested exception is java.lang.RuntimeException: Could not find or parse database configura
tion file: 'db.properties'.
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySuppor
t.java:149)
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1440)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:247)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:3
& && &&&... 17 more
Caused by: java.lang.RuntimeException: Could not find or parse database configuration file: 'db.properties'.
& && &&&at com.monMain.setupHibernate(CommonMain.java:159)
& && &&&at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:107)
& && &&&at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:60)
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySuppor
t.java:142)
& && &&&... 22 more
Caused by: java.io.FileNotFoundException: /etc/cloudera-scm-server/db.properties (No such file or directory)
& && &&&at java.io.FileInputStream.open(Native Method)
& && &&&at java.io.FileInputStream.&init&(FileInputStream.java:146)
& && &&&at com.monMain.setupHibernate(CommonMain.java:102)
& && &&&... 25 more
解决过程：
1、从别的省的服务器上要了 db.properties文件，并按正确的权限和用户创建；
2、启动cloudera-scm-server成功了，但没有几秒就吊死
部署过程：
[root@cloud0 etc]# ls -lrta |grep cloudera
drwxr-xr-x& & 2 root& && && &root& && && &&&4096 Jun 11 17:41 cloudera-scm-agent
drwxr-xr-x& & 2 cloudera-scm cloudera-scm& &4096 Jun 12 12:54 cloudera-scm-server
[root@cloud0 etc]# cd&&cloudera-scm-server
[root@cloud0 cloudera-scm-server]# ls -lrta
drwxr-xr-x. 144 root& && && &root& && && &12288 Jun 12 10:51 ..
-rw-r--r--& & 1 root& && && &root& && && & 1424 Jun 12 11:36 log4j.properties
-rw-r--r--& & 1 root& && && &root& && && & 8041 Jun 12 12:03 db.propertiesbak
-rw-r--r--& & 1 root& && && &root& && && & 8210 Jun 12 12:54 db.propertiesbak2
-rw-r--r--& & 1 cloudera-scm cloudera-scm& &163 Jun 12 12:54 db.properties
drwxr-xr-x& & 2 cloudera-scm cloudera-scm&&4096 Jun 12 12:54 .
[root@cloud0 cloudera-scm-server]# more db.properties&&从河南要的结果
com.cloudera.cmf.db.type=postgresql
oudera.cmf.db.host=localhost:7432
oudera.cmf.db.name=scm
com.cloudera.cmf.db.user=scm
com.cloudera.cmf.db.password=2QWXonIxdf
[root@cloud0 cloudera-scm-server]#
重启cm后没有几秒就挂了，如下图
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server restart
cloudera-scm-server is already stopped
Starting cloudera-scm-server: [&&OK&&]
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server (pid&&10255) is running...
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server dead but pid file exists
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server dead but pid file exists
[root@cloud0 cloudera-scm-server]# service cloudera-scm-server status
cloudera-scm-server dead but pid file exists
[root@cloud0 cloudera-scm-server]#
具体日志：
[root@cloud0 cloudera-scm-server]# more cloudera-scm-server.out
JAVA_HOME=/usr/java/jdk1.7.0_67-cloudera
Exception in thread &main& org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.cloudera.serv
er.cmf.TrialState': Cannot resolve reference to bean 'entityManagerFactoryBean' while setting
nested exception
is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean t
hrew exceptio nested exception is org.hibernate.exception.GenericJDBCException: Could not open connection
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:3
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver
.java:106)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableB
eanFactory.java:1003)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBe
anFactory.java:907)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFact
ory.java:485)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactor
y.java:456)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
& && &&&at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.
& && &&&at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext
.java:895)
& && &&&at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
& && &&&at com.cloudera.server.cmf.Main.bootstrapSpringContext(Main.java:344)
& && &&&at com.cloudera.server.cmf.Main.&init&(Main.java:220)
& && &&&at com.cloudera.server.cmf.Main.main(Main.java:194)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': Factor
yBean threw exceptio nested exception is org.hibernate.exception.GenericJDBCException: Could not open connectio
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySuppor
t.java:149)
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1440)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:247)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:3
& && &&&... 17 more
Caused by: org.hibernate.exception.GenericJDBCException: Could not open connection
& && &&&at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:54)
& && &&&at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
& && &&&at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
& && &&&at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:221)
& && &&&at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:157)
& && &&&at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.coordinateWork(JdbcCoordinatorImpl.java:282)
& && &&&at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:2000)
& && &&&at org.hibernate.internal.SessionImpl.doWork(SessionImpl.java:1986)
& && &&&at com.cloudera.enterprise.dbutil.DbUtil.getSchemaVersion(DbUtil.java:190)
& && &&&at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.checkVersionDoFail(EntityManagerFactoryBean.java:258)
& && &&&at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:120)
& && &&&at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:60)
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySuppor
t.java:142)
& && &&&... 22 more
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
& && &&&at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
& && &&&at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)
& && &&&at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
& && &&&at org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:84)
& && &&&at org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:29
& && &&&at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:214)
& && &&&... 31 more
Caused by: com.mchange.v2.resourcepool.CannotAcquireResourceException: A ResourcePool could not acquire a resource from its primary
factory or source.
& && &&&at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1319)
& && &&&at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
& && &&&at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
& && &&&at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
& && &&&... 35 more
目前不知道要怎么再去处理了，请各位大神救救我
主题帖子积分
高级会员, 积分 1597, 距离下一级还需 3403 积分
高级会员, 积分 1597, 距离下一级还需 3403 积分
错误比较多，
log4j:ERROR Could not read configuration file from URL [file:/etc/cloudera-scm-server/log4j.properties].
java.io.FileNotFoundException: /etc/cloudera-scm-server/log4j.properties (No such file or directory)
Caused by: java.lang.RuntimeException: Could not find or parse database configuration file: 'db.properties'.
oudera.cmf.db.host=localhost:7432
Caused by: java.sql.SQLException: Connections could not be acquired from the underlying database!
上面的host，最好换成是hostname，不一定是localhost
首先楼主是否启动
start cloudera-scm-server-db 进程，上面文件是找不到，楼主可以找找。或则补一个文件，如果有的话，可能是权限的问题。
根据楼主的描述，好像都是缺失的文件，是否在安装过程中发生了异常。建议重新安装下。
主题帖子积分
新手上路, 积分 17, 距离下一级还需 33 积分
新手上路, 积分 17, 距离下一级还需 33 积分
关键问题在于
[root@cloud0 cloudera-scm-server]# more db.properties&&从河南要的结果
com.cloudera.cmf.db.type=postgresql
oudera.cmf.db.host=localhost:7432
oudera.cmf.db.name=scm
com.cloudera.cmf.db.user=scm
com.cloudera.cmf.db.password=2QWXonIxdf
楼主写错了配置信息oudera.cmf应该是com.cloudera，还有每个机器的密码不一样2QWXonIxdf并不是你的机器密码吧
站长推荐 /4
云计算hadoop视频大全(新增 yarn、flume|storm、hadoop一套视频
等待验证会员请验证邮箱
新手获取积分方法
技术类问答，解决学习openstack，hadoop生态系统中遇到的问题
Powered by前段时间安装好了CDH4.1后，运行了一段时间，后来，把主机IP地址改掉了，但是发现服务都启动不了，怎么办呢？想到的解决方式如下：
把主机IP地址改回来
CDH4.1上的IP地址改成和主机IP地址一样。
　　如下图，是我安装的CDH4.1的主机情况。
&ignore_js_op&&
　　第一种方法改回主机IP地址后，重启Cloudera相关服务后，能正常运行。当我试第二种方法却发现，没地方改IP地址，因为，这台机器是Cloudera Manager的管理节点，无法直接修改IP地址。既然无法直接修改IP地址，那么只能重装，把现有的主机删掉，然后重新把所有服务装到主机目前的IP地址上。
　　删除主机，重新配置主机服务的过程如下：
　　一、删除主机
　　点击&&ignore_js_op&&，选择删除主机，却出现&无法删除以下 1 个主机因为它（们）具有角色实例或未完全被取消配置。&如下图所示。
&ignore_js_op&
　　当前主机下有服务还在运行或者是当前主机配置了服务未完全删除都会导致这个问题。
在这里只可能是当前主机配置的服务未删除，因为，我们改过了IP，服务本身就没办法启动。点击页面上的服务链接。查看下，我们以前安装了什么服务，我配置的服务如下图。
&ignore_js_op&&
　　点击操作，把服务一个个删除完，删完之后，再删除主机，这样就能成功地把主机删除。
　　二、重新配置主机服务
　　点击页面上的主机，然后选添加主机，一步步继续，到了为CDH群集安装指定主机页面（下图），输入我们改过的主机IP地址，然后搜索，之后直接继续。
&ignore_js_op&
　　这个过程会很快的，因为我们的机器本来就是已经装过了CDH4.1的，但是后来出现了个错误，如下图所示。
&ignore_js_op&&
& && && &这个问题看起来摸不着头脑，蹦进我脑子里的第一个念头是在控制台查看cloudera-scm-agent这个服务的状态，查了网上的资料，却发现关于Cloudera Manager的中文资料是如此的少，根本没资料可以参考，很幸运，问题终于让我解决了，下面是我解决这个问题的步骤。
查看cloudera-scm-agent服务的状态。
service cloudera-scm-agent status
显示：cloudera-scm-agent服务已死，但pid文件还存在。因此，我猜想，是不是以前直接把IP地址改过之后，服务未正常关闭，导致pid文件还存在。因此把pid文件删除。
[root@client ~]# cd /var/run
[root@client ~]# rm &f cloudera-scm-agent.pid
我们配置CDH的时候，就默认把进程文件都放在/var/run这个目录下，如果不知道这个pid文件在哪，用locate *.pid这样模糊查询，也能找到pid文件。可是删了之后，CDH还是不能正常启动。于是，只能去查看日志文件了。查询日志文件。
[root@client ~]# cd /var/log/cloudera-scm-agent
[root@client ~]# vim cloudera-scm-agent.log
在日志中发现这样一条错误信息：ERROR ENGINE Error in HTTP server: shutting down Traceback (most recent call last)这下问题找到了，是因为httpd服务有问题。
[root@client ~]# service httpd restart
显示：&，using 192.168.10.188 for ServerName，这就是问题的根源了，我现在主机的IP地址已经不是188了，CDH4.1本来配置服务用的188地址，因此肯定是某个地方这个IP地址没有修改。最后发现原来问题出在/etc/hosts底下，因为CDH4.1会读取/etc/hosts下的主机名和主机地址，以前配过的，却没改过来，导致http服务无法通信，cloudera-scm-agent无法启动。修改了host文件后，CDH4.1正常启动了。
阅读(...) 评论() &}