Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Sqoop >> mail # user >> Sqoop 2 Server 404


+
Kyle B 2013-05-02, 19:31
+
vasanth kumar 2013-05-02, 20:05
+
Kyle B 2013-05-02, 20:38
+
vasanth kumar 2013-05-02, 21:02
Copy link to this message
-
Re: Sqoop 2 Server 404
Vasanth kumar,

Thanks, that was it. It looks like the addtowar script didn't copy over all
of what was needed. I had to manually copy hadoop-common-2.0.2.1-alpha.jar
& a couple of the hadoop-yarn-*-2.0.2.1-alpha.jar files into
server/webapps/sqoop/WEB-INF/lib , and then sqoop server started as
expected. You saved me a lot of time and headache.

Thanks,

-Kyle
On Thu, May 2, 2013 at 2:02 PM, vasanth kumar <[EMAIL PROTECTED]>wrote:

> Hi Kyle,
> Hadoop core jar is missing. Check whether core jar is added in server in
> path sqoop2_home/server/webapps/sqoop/WEB-INF/lib.
>
> Other possibility is, addtowar.sh script sometimes copies source
> core-src.jar. Better you manually copy the hadoop core binary jar into that
> location. Already issue raised for this SQOOP-897<https://issues.apache.org/jira/browse/SQOOP-897>
> .
>
> You got exception due to log4j, for fixing that add below line at end in
> catalina.properties in sqoop2_home/server/conf/
> "org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES > false"
>
>
> Thanks
> Vasanth kumar
>
>
> On Fri, May 3, 2013 at 2:08 AM, Kyle B <[EMAIL PROTECTED]> wrote:
>
>> Following are the sqoop & catalina logs. They're a bit lengthy. The only
>> thing that stands out to me is "SEVERE: Exception sending context
>> initialized event to listener instance of class
>> org.apache.sqoop.server.ServerInitializer. java.lang.NoClassDefFoundError:
>> org/apache/hadoop/conf/Configuration". However, I did specify the
>> -hadoop-auto flag when running addtowar.sh, which seems to have grabbed the
>> war files and included them in sqoop.war. Maybe it didn't grab all of the
>> ones it needed?
>>
>>
>> -------------------------------------------------------------------------------------
>> - @LOGDIR@/sqoop.log -
>> 2013-05-02 13:28:40,358 INFO  repository.RepositoryManager
>> [org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:78)]
>> Setting system properties: {derby.stream.error.file=@LOGDIR@
>> /derbyrepo.log}
>> 2013-05-02 13:28:40,369 INFO  repository.JdbcRepositoryContext
>> [org.apache.sqoop.repository.JdbcRepositoryContext.<init>(JdbcRepositoryContext.java:159)]
>> [repo-ctx]
>> handler=org.apache.sqoop.repository.derby.DerbyRepositoryHandler,
>> create-schema=true, conn-url=jdbc:derby:@BASEDIR@/repository/db;create=true,
>> driver=org.apache.derby.jdbc.EmbeddedDriver, user=sa, password=*****,
>> jdbc-props={}, tx-isolation=READ_COMMITTED, max-conn=10
>> 2013-05-02 13:28:40,649 INFO  derby.DerbyRepositoryHandler
>> [org.apache.sqoop.repository.derby.DerbyRepositoryHandler.initialize(DerbyRepositoryHandler.java:149)]
>> DerbyRepositoryHandler initialized.
>> 2013-05-02 13:28:41,335 DEBUG derby.DerbyRepositoryHandler
>> [org.apache.sqoop.repository.derby.DerbyRepositoryHandler.schemaExists(DerbyRepositoryHandler.java:229)]
>> SQOOP schema ID: 341cc09e-013e-66a0-568d-00002745c360
>> 2013-05-02 13:28:41,338 INFO  repository.JdbcRepositoryProvider
>> [org.apache.sqoop.repository.JdbcRepositoryProvider.initializeRepositoryHandler(JdbcRepositoryProvider.java:168)]
>> JdbcRepositoryProvider initialized
>> 2013-05-02 13:28:41,338 INFO  repository.JdbcRepositoryProvider
>> [org.apache.sqoop.repository.JdbcRepositoryProvider.initialize(JdbcRepositoryProvider.java:68)]
>> JdbcRepository initialized.
>> 2013-05-02 13:28:41,338 INFO  repository.RepositoryManager
>> [org.apache.sqoop.repository.RepositoryManager.initialize(RepositoryManager.java:114)]
>> Repository initialized: OK
>> 2013-05-02 13:28:41,340 INFO  connector.ConnectorManager
>> [org.apache.sqoop.connector.ConnectorManager.initialize(ConnectorManager.java:162)]
>> Connector config urls:
>> [jar:file:/home/kyle/sqoop-1.99.2-bin-hadoop200/server/webapps/sqoop/WEB-INF/lib/sqoop-connector-generic-jdbc-1.99.2.jar!/sqoopconnector.properties]
>> 2013-05-02 13:28:41,342 DEBUG connector.ConnectorHandler
>> [org.apache.sqoop.connector.ConnectorHandler.<init>(ConnectorHandler.java:58)]
>> Connector configuration:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB