question Re: Cloudera manager does not start in Archives of Support Questions (Read Only)

Cloudera manager does not start

Nishan — Fri, 16 Sep 2022 08:55:43 GMT

I just configured my db(oracle) and started cloudera manager.It says started but could not see any thing in the logs and I could not find port 7180 being used.I had succesfully installed cm on this very machine pointing to postgres a few days ago and it worked fine.

Then I un installed and trying to install to an oracle db.All steps until this went fine.Any ideas?

I tried checking cloudera-scm-server.log but it has log info of old installation(with postgres).I do not see any information about the new installation.It is obvious that cm did not start because the port was never being used.

Re: Cloudera manager does not start

Clint — Wed, 19 Mar 2014 16:09:10 GMT

It is possible that the file /etc/cloudera-scm-server/db.properties still has the old information about postgres, but I'm not sure.

Are you saying there is no error in either of the following files after you attempted to start the service?

/var/log/cloudera-scm-server/cloudera-scm-server.log

/var/log/cloudera-scm-server/cloudera-scm-server.out

Re: Cloudera manager does not start

Darren — Wed, 19 Mar 2014 16:12:16 GMT

Hi Nishan,

Did /var/log/cloudera-scm-server/cloudera-scm-server.log include the a line with "Started Jetty Server" with a time stamp matching when you tried to start the server?

Is there anything in /var/log/cloudera-scm-server/cloudera-scm-server.out? Sometimes fatal errors are reported here rather than in the .log file.

Thanks,

Darren

Re: Cloudera manager does not start

Darren — Wed, 19 Mar 2014 16:13:24 GMT

Also, be sure that you remove /etc/cloudera-scm-server/db.mgmt.properties if it exists. It should only be used with the embedded postgresql db.

Re: Cloudera manager does not start

Nishan — Wed, 19 Mar 2014 16:14:35 GMT

The db.properties file has the correct oracle db information and teh database preparation step went well.

Yes .There is no error in those files.In fact the latest records in those files are from two days ago when I successfully did an installation.

Re: Cloudera manager does not start

Nishan — Wed, 19 Mar 2014 16:22:15 GMT

Hi Darren,

Here is the info from the files.

I do not see any errors in cloudera-scm-server.log.It does not have any information of my attempt to start .All that log has is the earlier installation details(2 days back).

The .out file could not find a log4j.properties.This is the only entry in .out file
: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.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at sun.net.www.protocol.file.FileURLConnection.getInputStream(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:134)
log4j:ERROR Ignoring configuration file [file:/etc/cloudera-scm-server/log4j.properties].
log4j:WARN No appenders could be found for logger (org.springframework.context.support.ClassPathXmlApplicationContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Re: Cloudera manager does not start

Darren — Wed, 19 Mar 2014 16:25:10 GMT

Hi Nishan,

It seems that you've accidentally deleted the log4j file and need to add it back. Here's what that /etc/cloudera-scm-server/log4j.properties should have as contents:
# Copyright (c) 2012 Cloudera, Inc. All rights reserved.
#
# !!!!! IMPORTANT !!!!!
# The Cloudera Manager server finds its log file by querying log4j. It
# assumes that the first file appender in this file is the server log.
# See LogUtil.getServerLogFile() for more details.
#
# Define some default values that can be overridden by system properties
cmf.root.logger=INFO,CONSOLE
cmf.log.dir=.
cmf.log.file=cmf-server.log

# Define the root logger to the system property "cmf.root.logger".
log4j.rootLogger=${cmf.root.logger}

# Logging Threshold
log4j.threshhold=ALL

# Disable most JDBC tracing by default.
log4j.logger.org.jdbcdslog=FATAL

# Disable overly loud Avro IPC logging
log4j.logger.org.apache.avro.ipc.NettyTransceiver=FATAL

# Disable overly loud Flume config validation logging
log4j.logger.org.apache.flume.conf.FlumeConfiguration=ERROR

log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.target=System.err
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d{ISO8601} %5p [%t:%c{2}@%L] %m%n

log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.MaxFileSize=10MB
log4j.appender.LOGFILE.MaxBackupIndex=10
log4j.appender.LOGFILE.File=${cmf.log.dir}/${cmf.log.file}
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%d{ISO8601} %5p [%t:%c{2}@%L] %m%n

Thanks,
Darren

Re: Cloudera manager does not start

Nishan — Wed, 19 Mar 2014 16:40:08 GMT

The db.properties had an old tns name.I changed that to the correct one and it works now.Thank you Clint and Darren.

Re: Cloudera manager does not start

YogeshSKulkarni — Wed, 30 Dec 2015 13:27:03 GMT

Hi Darren,

We had a similar problem while installing Cloudera Manager 5.5. The cloudera-scm-server process was failing after a few seconds. The scm-server.out file indicated that the log4j file was not available. We uninstalled CM and tried re-installing it again; however, the problem persisted.

As per your suggestion, we manually created a file log4j.properties and added the contents. We then

1) Stopped cloudera-scm-server-db

2) restarted postgresql

3) started cloudera-scm-server-db

4) started cloudera-scm-server

and it worked!! We were immediately able to access CM via the browser.

Thanks a lot for your help.

Regards,

Yogesh