Please Help! Error message: log4j:WARN No appenders could be found for logger (org.apache.hive.jdbc.Utils)

[Anonymous]

Hi friends.

When i run my job from shell (execute the ".sh"), i see the next error message.

    log4j:WARN No appenders could be found for logger (org.apache.hive.jdbc.Utils).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info

My job is very simple, just a table input to Impala DB with a file output .

[lojdr]

Hello,

Can you post here the complete log output of the job when you run it?

Regards

Lojdr

[Anonymous]

Hi lojdr.

Thanks for your help.

This is the compelte log output (I run in Linux server).

[mdmusr@sdimdmd1 tj_impala_conn_test]$
[mdmusr@sdimdmd1 tj_impala_conn_test]$ sh -x tj_impala_conn_test_run.sh
++ dirname tj_impala_conn_test_run.sh
+ cd .
++ pwd
+ ROOT_PATH=/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_ conn_test
+ java -Xms256M -Xmx1024M -cp .:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn _test_1.1/tj_impala_conn_test:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_t est_1.1/tj_impala_conn_test/../lib/routines.jar:/u01/app/mdmusr/MDM/Batch/Execut e/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/antlr-runtime-3.4.jar:/u01/ app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/ avro-1.7.6-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1. 1/tj_impala_conn_test/../lib/commons-cli-1.2.jar:/u01/app/mdmusr/MDM/Batch/Execu te/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/commons-codec-1.9.jar:/u01 /app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib /commons-collections-3.2.2.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_ test_1.1/tj_impala_conn_test/../lib/commons-configuration-1.6.jar:/u01/app/mdmus r/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/commons-h ttpclient-3.0.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj _impala_conn_test/../lib/commons-io-2.4.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj _impala_conn_test_1.1/tj_impala_conn_test/../lib/commons-lang-2.6.jar:/u01/app/m dmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/commo ns-logging-1.2.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_ impala_conn_test/../lib/curator-client-2.6.0.jar:/u01/app/mdmusr/MDM/Batch/Execu te/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/curator-framework-2.6.0.ja r:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/ ../lib/datanucleus-api-jdo-3.2.6.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala _conn_test_1.1/tj_impala_conn_test/../lib/datanucleus-core-3.2.10.jar:/u01/app/m dmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/datan ucleus-rdbms-3.2.9.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1 /tj_impala_conn_test/../lib/derby-10.11.1.1.jar:/u01/app/mdmusr/MDM/Batch/Execut e/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/dom4j-1.6.1.jar:/u01/app/md musr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/guava- 12.0.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_c onn_test/../lib/hadoop-auth-2.6.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute /tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hadoop-common-2.6.0-cdh5.8.1 .jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_te st/../lib/hadoop-hdfs-2.6.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_im pala_conn_test_1.1/tj_impala_conn_test/../lib/hadoop-mapreduce-client-common-2.6 .0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_imp ala_conn_test/../lib/hadoop-mapreduce-client-core-2.6.0-cdh5.8.1.jar:/u01/app/md musr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hadoop -mapreduce-client-jobclient-2.6.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute /tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hadoop-yarn-api-2.6.0-cdh5.8 .1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_ test/../lib/hadoop-yarn-client-2.6.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Exec ute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hadoop-yarn-common-2.6.0- cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala _conn_test/../lib/hadoop-yarn-server-web-proxy-2.6.0-cdh5.8.1.jar:/u01/app/mdmus r/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hive-exec -1.1.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj _impala_conn_test/../lib/hive-jdbc-1.1.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/ Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/hive-metastore-1.1.0- cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala _conn_test/../lib/hive-service-1.1.0-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Exec ute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/htrace-core-3.2.0-incubat ing.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn _test/../lib/htrace-core4-4.0.1-incubating.jar:/u01/app/mdmusr/MDM/Batch/Execute /tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/httpclient-4.2.5.jar:/u01/ap p/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/ht tpclient-4.3.3.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_ impala_conn_test/../lib/httpcore-4.2.5.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_ impala_conn_test_1.1/tj_impala_conn_test/../lib/httpcore-4.3.3.jar:/u01/app/mdmu sr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/jackson- core-asl-1.8.8.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_ impala_conn_test/../lib/jackson-jaxrs-1.8.8.jar:/u01/app/mdmusr/MDM/Batch/Execut e/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/jackson-mapper-asl-1.8.8.ja r:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/ ../lib/jackson-xc-1.8.8.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_tes t_1.1/tj_impala_conn_test/../lib/jdo-api-3.0.1.jar:/u01/app/mdmusr/MDM/Batch/Exe cute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/jersey-client-1.9.jar:/u 01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../l ib/jersey-core-1.9.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1 /tj_impala_conn_test/../lib/libfb303-0.9.2.jar:/u01/app/mdmusr/MDM/Batch/Execute /tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/libthrift-0.9.2.jar:/u01/app /mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/log 4j-1.2.16.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impal a_conn_test/../lib/log4j-1.2.17.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_ conn_test_1.1/tj_impala_conn_test/../lib/protobuf-java-2.5.0.jar:/u01/app/mdmusr /MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/servlet-ap i-2.5.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_co nn_test/../lib/slf4j-api-1.7.5.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_c onn_test_1.1/tj_impala_conn_test/../lib/slf4j-log4j12-1.7.5.jar:/u01/app/mdmusr/ MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test/../lib/talendcsv.j ar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala_conn_test_1.1/tj_impala_conn_test /../lib/zookeeper-3.4.5-cdh5.8.1.jar:/u01/app/mdmusr/MDM/Batch/Execute/tj_impala _conn_test_1.1/tj_impala_conn_test/tj_impala_conn_test_1_1.jar: local_project.tj _impala_conn_test_1_1.tj_impala_conn_test --context=Default
log4j:WARN No appenders could be found for logger (org.apache.hive.jdbc.Utils).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo.

I read in internet similar errors in other projects (comun java projects), where say that not exists the log4j.xml and the log4j.properties files in the jar log4j, but i dont know where put this in Talend.

Regards

Chris

[lojdr]

Hello,

Is this really all? Did the process finish or you had to kill it? Can you also please post here screenshot of the job? I am expecting, that you exported it and now you are try to run it as standalone, aren't you?

Regards

lojdr

[Anonymous]

Yes, this is really all, the process finish almost immediately.

I export the job from "Talend for Open Studio for Big Data 6.4" im my PC (Windows), and later I upload it to a Linux Server (all the files, libraries, sh, etc generated by talend), is a data integrator server with acces to Impala DB, later I run the ".sh" standalone from putty.

I attached images that you want.

Thank you.

Regards.

Chris

putty.png
standalone.png

[lojdr · Accepted solution]

Hello,

There is log4j component in Exchange. You can setup the script configuration with this component.

Regards

Lojdr

[Anonymous]

Hello,

Can you successfully execute your job in studio? Are you using talend open studio? Did you enable "Activate log4j in components" in project Settings?

Note:The log4j feature is only available in Talend Subscription Version.

Best regards

Sabrina

[Anonymous]

It's working now in "standalone" mode.

I put the ".xml" file inside of the generated files for standalone job and use "tInitLog4j" for setting the location of this new file with a relative path.

Thank you very much.

Regards

Chris

[Anonymous]

Hello xdshi.

Yes, i can succefully execute my job in studio, just fail in "standalone" mode, I don't know if the option "Activate log4j in components" is enabled correctly, I will try, but the solution of lojdr works for me at the moment.

About your note, I don´t have a suscription version, but i don't want use "log4j", just want a simple query to impala but the error of "log4j" appears.

Regards

Chris

[Anonymous]

Hello,

Thanks for your feedback. Feel free to let us know if there is any further help we can give.

Best regards

Sabrina