Member since
12-29-2014
5
Posts
0
Kudos Received
0
Solutions
01-02-2015
04:19 AM
I'm having the same problem while deploying services within my cluster. when it comes to the creation of the DB, it fails. here is the content of the config log: 2015-01-02 11:48:18,428 INFO org.apache.sqoop.core.PropertiesConfigurationProvider: Shutting down configuration poller thread
2015-01-02 11:54:26,291 INFO org.apache.sqoop.core.PropertiesConfigurationProvider: Starting config file poller thread
2015-01-02 11:54:26,293 INFO org.apache.sqoop.tools.tool.UpgradeTool: Initializing the RepositoryManager with immutable option turned off.
2015-01-02 11:54:26,296 INFO org.apache.sqoop.repository.RepositoryManager: Setting system properties: {derby.stream.error.file=/var/log/sqoop2/derbyrepo.log}
2015-01-02 11:54:26,307 INFO org.apache.sqoop.repository.JdbcRepositoryContext: [repo-ctx] handler=org.apache.sqoop.repository.derby.DerbyRepositoryHandler, conn-url=jdbc:derby:/var/lib/sqoop2/repository/db;create=true, driver=org.apache.derby.jdbc.EmbeddedDriver, user=null, password=*****, jdbc-props={}, tx-isolation=READ_COMMITTED, max-conn=10
2015-01-02 11:54:26,707 INFO org.apache.sqoop.repository.derby.DerbyRepositoryHandler: DerbyRepositoryHandler initialized.
2015-01-02 11:54:26,711 INFO org.apache.sqoop.repository.JdbcRepositoryProvider: JdbcRepositoryProvider initialized
2015-01-02 11:54:26,712 INFO org.apache.sqoop.repository.JdbcRepositoryProvider: JdbcRepository initialized.
2015-01-02 11:54:26,712 INFO org.apache.sqoop.repository.RepositoryManager: Creating or updating respository at bootup
2015-01-02 11:54:26,718 ERROR org.apache.sqoop.tools.tool.UpgradeTool: Can't finish upgrading RepositoryManager, Driver and ConnectionManager:
org.apache.sqoop.common.SqoopException: JDBCREPO_0007:Unable to lease link
at org.apache.sqoop.repository.JdbcRepositoryTransaction.begin(JdbcRepositoryTransaction.java:63)
at org.apache.sqoop.repository.JdbcRepository.doWithConnection(JdbcRepository.java:85)
at org.apache.sqoop.repository.JdbcRepository.doWithConnection(JdbcRepository.java:61)
at org.apache.sqoop.repository.JdbcRepository.createOrUpgradeRepository(JdbcRepository.java:127)
at org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:123)
at org.apache.sqoop.tools.tool.UpgradeTool.runToolWithConfiguration(UpgradeTool.java:39)
at org.apache.sqoop.tools.ConfiguredTool.runTool(ConfiguredTool.java:35)
at org.apache.sqoop.tools.ToolRunner.main(ToolRunner.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.sqoop.tomcat.TomcatToolRunner.main(TomcatToolRunner.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.catalina.startup.Tool.main(Tool.java:225)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:derby:/var/lib/sqoop2/repository/db;create=true
at java.sql.DriverManager.getConnection(DriverManager.java:596)
at java.sql.DriverManager.getConnection(DriverManager.java:187)
at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:51)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:840)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
at org.apache.sqoop.repository.JdbcRepositoryTransaction.begin(JdbcRepositoryTransaction.java:61)
... 17 more
2015-01-02 11:54:26,722 INFO org.apache.sqoop.core.PropertiesConfigurationProvider: Shutting down configuration poller thread I checked different directories and can't find any problem. I can even see the file "postgresql-9.0-801.jdbc4.jar" in /var/lib/sqoop2. Any solution is welcomed!!! Regards
... View more
01-02-2015
01:37 AM
Hi GautamG, unfortunately i've already made a cleanup when i found the solution of this issue. I did'nt backup the logs prior to this cleanup. Therefore i can't provide these logs. But as i said, changing language to en_US solved the problem. Thanks.....
... View more
12-31-2014
07:46 AM
Thank you very much Ive. This solution worked fine when i switched language from fr_FR.UTF-8 to fen_US.UTF-8 on each host of the cluster. My next question is how to make it comply with french language?
... View more
12-29-2014
12:49 AM
Hello, i'm installing CDH5.3.0 using Automated Installation by Cloudera Manager on a cluster of 10 machines. While configuring the agents, it fails to install on the machine where scm-server was installed. This machine is also in the cluster and OS is RHEL 6. There no error reported on the deployment GUI. The only message i ca see is: cloudera-manager-agent must have Version=5.3.0 and Build=166, exiting. I need a help!!
... View more
Labels:
- Labels:
-
Cloudera Manager