I want Pig to use HCatalog in my Oozie workflow ... View more

I am working on adding a Squid telemetry to an Ambari-managed cluster on AWS. I've parsed and transformed the Squid message, but I am getting the following error message when I attempt to push it to Zookeeper: [root@ip-10-0-0-90 ~]# /usr/metron/0.2.0BETA/bin/zk_load_configs.sh -i /usr/metron/0.2.0BETA/config/zookeeper -m PUSH -z ec2-xx-xx-xxx-xxx.us-west-2.compute.amazonaws.com:2181 log4j:WARN No appenders could be found for logger (org.apache.curator.framework.imps.CuratorFrameworkImpl). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. I checked the referenced Apache FAQ and found the following answer: Why do I see a warning about "No appenders found for logger" and "Please configure log4j properly"? This occurs when the default configuration files log4j.properties and log4j.xml can not be found and the application performs no explicit configuration. log4j uses Thread.getContextClassLoader().getResource() to locate the default configuration files and does not directly check the file system. Knowing the appropriate location to place log4j.properties or log4j.xml requires understanding the search strategy of the class loader in use. log4j does not provide a default configuration since output to the console or to the file system may be prohibited in some environments. Not quite sure how to resolve this. Any help would be appreciated. Thanks! ... View more

I am trying to install Metron on a Vagrant single-node. I received the following error message during the application build step (mvn apache-rat:check && cd metron-streaming && mvn clean integration-test && cd ..,). I am running Maven 3.3.9. [ERROR] No plugin found for prefix 'apache-rat' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/root/.m2/repository), central (https://repo.maven.apache.org/maven2)] -> [Help 1] ... View more

I am getting the following error when I perform the Apache Metron deployment process: TASK [ambari_master : check if ambari-server is up on ec2-52-38-224-98.us-west-2.compute.amazonaws.com:8080] *** fatal: [ec2-52-38-224-98.us-west-2.compute.amazonaws.com]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for ec2-52-38-224-98.us-west-2.compute.amazonaws.com:8080"} Does this mean that one of my AWS EC2 users is not online or responsive or accessible? If so, how do I fix that? ... View more