Reply
Highlighted
Explorer
Posts: 24
Registered: ‎04-17-2017
Accepted Solution

Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

 

getting the below error in the /var/log/cloudera-manager-installer/5.install-cloudera-manager-server-db-2.log: 

Problem: nothing provides postgresql-server >= 8.4 needed by cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 1: do not install cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 2: break cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64 by ignoring some of its dependencies.

Cloudera Employee
Posts: 105
Registered: ‎04-12-2016

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

Add the postgresql repo to all your hosts and the install should work.

 

These commands work for me:

 

zypper addrepo http://download.opensuse.org/repositories/server:database:postgresql/SLE_11_SP4/server:database:post...

zypper refresh
        MUST ANSWER ' a ' TO ALWAYS TRUST KEY QUESTION

ls -l /etc/zypp/repos.d/ | grep postgres

zypper clean --all

 

Tina

 

 

Cloudera Employee
Posts: 105
Registered: ‎04-12-2016

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

[ Edited ]

http://download.opensuse.org/repositories/server:database:postgresql/SLE_11_SP4/server:database:post...

 

Click on this link to go to repo and copy from there, full name is getting cut off in my reply and my copy did not copy the full name.

Explorer
Posts: 24
Registered: ‎04-17-2017

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

Did the same as you mentioned, but still the same error is popping up:

hostname:~ # zypper addrepo http://download.opensuse.org/repositories/server:database:postgresql/SLE_11_SP4/server:database:post...
Adding repository 'PostgreSQL and related packages (SLE_11_SP4)' [done]
Repository 'PostgreSQL and related packages (SLE_11_SP4)' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://download.opensuse.org/repositories/server:/database:/postgresql/SLE_11_SP4/

zypper refresh

hostname:~ # zypper refresh
Retrieving repository 'PostgreSQL and related packages (SLE_11_SP4)' metadata [\]

New repository or package signing key received:
Key ID: 562111AC05905EA8
Key Name: server:database OBS Project <server:database@build.opensuse.org>
Key Fingerprint: 116EB86331583E47E63CDF4D562111AC05905EA8
Key Created: Thu 02 Feb 2017 08:09:57 AM EST
Key Expires: Sat 13 Apr 2019 09:09:57 AM EDT
Repository: PostgreSQL and related packages (SLE_11_SP4)

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a
Retrieving repository 'PostgreSQL and related packages (SLE_11_SP4)' metadata [done]
Building repository 'PostgreSQL and related packages (SLE_11_SP4)' cache [done]
All repositories have been refreshed.

hostname:~ # ls -l /etc/zypp/repos.d/ | grep postgres
-rw-r--r-- 1 root root 330 Feb 5 11:51 server_database_postgresql.repo

hostname:~ # zypper clean --all
All repositories have been cleaned up.

 

Still getting the same error:

 

hostname:/var/log/cloudera-manager-installer # ll
total 28
-rw-r--r-- 1 root root 56 Feb 5 11:53 0.check-selinux.log
-rw-r--r-- 1 root root 0 Feb 5 11:54 1.install-repo-pkg.log
-rw-r--r-- 1 root root 784 Feb 5 11:54 2.install-oracle-j2sdk1.7.log
-rw-r--r-- 1 root root 1368 Feb 5 11:56 3.install-cloudera-manager-server.log
-rw-r--r-- 1 root root 33 Feb 5 11:56 4.check-for-systemd.log
-rw-r--r-- 1 root root 496 Feb 5 11:56 5.install-cloudera-manager-server-db-2.log
-rw-r--r-- 1 root root 51 Feb 5 11:56 6.remove-cloudera-manager-server.log
-rw-r--r-- 1 root root 0 Feb 5 11:56 7.remove-cloudera-manager-daemons.log
-rw-r--r-- 1 root root 106 Feb 5 11:56 8.remove-cloudera-manager-repository.log
hostname:/var/log/cloudera-manager-installer # pwd
/var/log/cloudera-manager-installer
hostname:/var/log/cloudera-manager-installer # cat 5.install-cloudera-manager-server-db-2.log
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides postgresql-server >= 8.4 needed by cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 1: do not install cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 2: break cloudera-manager-server-db-2-5.14.0-1.cm5140.p0.25.sles11.x86_64 by ignoring some of its dependencies


Choose from above solutions by number or cancel [1/2/c] (c): c

Cloudera Employee
Posts: 105
Registered: ‎04-12-2016

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

It looks like the PostgreSQL version 8.4 was removed from that repo recently.   The page does indicate it was updated on Jan 25, 2018.

 

Doing a quick internet search, I cannot find a repo that could be pointed to on SLES 11, so the cloudera-manager-installer.bin can find one to install.

 

You can try to manually install with directions here https://www.cloudera.com/documentation/enterprise/5-11-x/topics/cm_ig_install_path_b.html

 

Or

Install on another platform beside SLES

 

Sorry for the inconvience, this did work in January.

Explorer
Posts: 24
Registered: ‎04-17-2017

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

Manually installed mysql and tried to do path B install, getting the below error:

 

BEGIN zypper --gpg-auto-import-keys -n se -i --match-exact -t package cloudera-manager-agent | grep -E '^i[[:space:]]*\|[[:space:]]*cloudera-manager-agent'
END (1)
BEGIN zypper --gpg-auto-import-keys -n se --match-exact -t package cloudera-manager-agent
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
--+------------------------+----------------------------+--------
| cloudera-manager-agent | The Cloudera Manager Agent | package
END (0)
BEGIN zypper info cloudera-manager-agent | grep -E 'Version[[:space:]]*:[[:space:]]5.14.0-.*\.25'
Version: 5.14.0-1.cm5140.p0.25.sles11
END (0)
BEGIN zypper --gpg-auto-import-keys -n in cloudera-manager-agent
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides apache2 needed by cloudera-manager-agent-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 1: do not install cloudera-manager-agent-5.14.0-1.cm5140.p0.25.sles11.x86_64
Solution 2: break cloudera-manager-agent-5.14.0-1.cm5140.p0.25.sles11.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): c
END (4)
remote package cloudera-manager-agent could not be installed, giving up
waiting for rollback request

 

Please suggest any fix.

Posts: 749
Topics: 1
Kudos: 175
Solutions: 95
Registered: ‎04-22-2014

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

@nehanirmal,

 

The agent package includes dependencies for any packages required for CDH to run.  In this case, it apepars the apache2 http server is not found anywhere. It is used for Hue's Load Balancer.

 

You could either:

 

(1) install it manually

(2) add a repository that contains the package

(3) try skipping it and see what happens.  You would not be able to use the Load Balancer included with the Hue service, though.

 

Here is a list of third party packages that are required:

 

https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_package_dependencies.html

Explorer
Posts: 24
Registered: ‎04-17-2017

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

Thanks,

Chose the last option and went ahead, installation happened successfully.

Not sure of any drawbacks it will lead to.

Posts: 749
Topics: 1
Kudos: 175
Solutions: 95
Registered: ‎04-22-2014

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

@nehanirmal,

 

There isn't much risk here since the apache2 package isn't necessary for hadoop itself.

When you upgrade packages, you may need to skip again, but other than that, as long as you don't use the Hue Load Balancer, you shouldn't notice a problem related to skipping the package.

 

Ben

Explorer
Posts: 24
Registered: ‎04-17-2017

Re: Unable to install Cloudera Manager on SUSE Linux Enterprise Server 11 (x86_64)

[ Edited ]

Suddenly my cloudera-scm-server has gone dead, when i restart it it again goes to being dead in 3 secs.

 

Getting the below  cloudera-scm-server.log output:

 

JAVA_HOME=/usr/java/jdk1.7.0_67-cloudera_backup
Exception in thread "main" org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.cloudera.server.cmf.TrialState': Cannot resolve reference to bean 'entityManagerFactoryBean' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean threw exception on object creation; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not open connection
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
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(AbstractAutowireCapableBeanFactory.java:1003)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.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.java:585)
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:393)
at com.cloudera.server.cmf.Main.<init>(Main.java:243)
at com.cloudera.server.cmf.Main.main(Main.java:216)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean threw exception on object creation; nested exception is javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not open connection
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:149)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:102)
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:322)
... 17 more
Caused by: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not open connection
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1387)
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1310)
at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:1397)
at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:62)
at com.cloudera.enterprise.AbstractWrappedEntityManager.beginForRollbackAndReadonly(AbstractWrappedEntityManager.java:89)
at com.cloudera.enterprise.dbutil.DbUtil.isInnoDbEnabled(DbUtil.java:549)
at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.checkMysqlTableEngineType(EntityManagerFactoryBean.java:139)
at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:122)
at com.cloudera.server.cmf.bootstrap.EntityManagerFactoryBean.getObject(EntityManagerFactoryBean.java:65)

at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142)
... 22 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.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:67)
at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160)
at org.hibernate.internal.SessionImpl.beginTransaction(SessionImpl.java:1426)
at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:59)
... 28 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:292)
at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:214)
... 33 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)
... 37 more

Announcements