We Keep Coding

arquillian test does not start

The arquillian test fails to start with the following message:
"Error: The LogManager accessed before the java.util.logging.manager
system property was set to org.jboss.logmanager.LogManager. Results
may be unexpected SLF4J: Failed to load class
org.slf4j.impl.StaticLoggerBinder SLF4J: Defaulting to no-operation
(NOP) logger implementation SLF4J: See
http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details"
Unfortunately I don't understand the messages. I've researched but haven't found a solution

Hbase error while executing ./bin/start-hbase.sh (windows)

I installed Hadoop with this tutorial https://www.youtube.com/watch?v=g7Qpnmi0Q-s and it´s working. I installed it in C:/hadoop.
I installed it only because I read that hadoop is a prerequisite for executing (no single mode) and the error messages are regarding some hadoop configurations. But it didn´t help.
I tried to install Hbase with this tutorial https://ics.upjs.sk/~novotnyr/blog/334/setting-up-hbase-on-windows. But I´m getting this error while executing ./bin/start-hbase.sh
Output in cygwin terminal:
$ ./bin/start-hbase.sh
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
s.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
s.
: Name or service not knownstname laptop-l6543teb
running master, logging to /cygdrive/c/java/hbase-2.2.4-bin/hbase-2.2.4//logs/hbase-maiwa-master-LAPTOP-L6543TEB.out
: running regionserver, logging to /cygdrive/c/java/hbase-2.2.4-bin/hbase-2.2.4//logs/hbase-maiwa-regionserver-LAPTOP-L6543TEB.out
hbase-site-xml
<configuration>
<property>
<name>hbase.rootdir</name>
<value>file:///C:/cygwin/root/tmp/hbase/data</value>
</property>
<property>
<name>hbase.zookeeper.property.dataDir</name>
<value>C:\Java\hbase-2.2.4-bin\hbase-2.2.4\logs</value>
</property>
<property>
<name>hbase.cluster.distributed</name>
<value>false</value>
</property>
<property>
<name>hbase.rootdir</name>
<value>hdfs://localhost:9000/hbase</value>
</property>
</configuration>
Environment variables:
Path variables:

The error output produced by start-hbase.sh has three different errors.
1. Issue with HADOOP_HOME variable
WARNING: DEFAULT_LIBEXEC_DIR ignored. It has been replaced by HADOOP_DEFAULT_LIBEXEC_DIR. WARNING: log4j.properties is not found. HADOOP_CONF_DIR may be incomplete.
ERROR: Invalid HADOOP_COMMON_HOME
Update the Environment variables with HADOOP_HOME pointing to the Hadoop installation folder (not the bin folder within the installation folder).
As per your setting,
HADOOP_HOME=C:\hadoop\
Additionally, set the location of the configuration files
HADOOP_CONF_DIR=C:\hadoop\etc\hadoop\
2. Issue with interpreting Linux style path or Invalid path
cygpath: can't convert empty path
In hbase-env.sh (under C:\Java\hbase-2.2.4-bin\hbase-2.2.4\conf\), update the values for HBASE_HOME and HBASE_CLASSPATH
As per your installation,
export HBASE_HOME=/cygdrive/c/Java/hbase-2.2.4-bin/hbase-2.2.4/
export HBASE_CLASSPATH=/cygdrive/c/Java/hbase-2.2.4-bin/hbase-2.2.4/lib/
And in your environment variables, make sure HBASE_HOME is configured similar to HADOOP_HOME.
3. Unable to resolve hostname
: Name or service not knownstname laptop-l6543teb
Update your hosts file with correct IP - Hostname mapping.

com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed

Im facing the below issue when trying to connect to cassandra cluster and display table contents:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /175.14.3.164:9042 (com.datastax.driver.core.TransportException: [/172.16.3.163:9042] Cannot connect))
at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:223)
at com.datastax.driver.core.ControlConnection.connect(ControlConnection.java:78)
at com.datastax.driver.core.Cluster$Manager.init(Cluster.java:1272)
at com.datastax.driver.core.Cluster.init(Cluster.java:158)
at com.datastax.driver.core.Cluster.connect(Cluster.java:248)
at com.datastax.driver.core.Cluster.connect(Cluster.java:281)
at com.X.Y.App.main(App.java:27)
In my cassandra.yaml file
native_transport_port: 9042
My listen_address : 172.14.3.164
seeds: 172.14.3.164
rpc_address: 172.14.3.164
And code :
cluster=Cluster.builder().addContactPoint("172.14.3.164").build();
I had seen other links related to it but followed them but still could n't fix it. Kindly help

Hadoop CDH4 Error:SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"

I am using ubuntu 14.04. CDH4.7
I am installing as per the procedure given in the link below
http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Quick-Start/cdh4qs_topic_3_2.html
The problem is I am not able to start the data node . I am getting the error as
naveensrikanthd#ubuntu:/$ for x in `cd /etc/init.d ; ls hadoop-hdfs-*` ; do sudo service $x start ; done
[sudo] password for naveensrikanthd:
* Starting Hadoop datanode:
starting datanode, logging to /var/log/hadoop-hdfs/hadoop-hdfs-datanode-ubuntu.out
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
* Starting Hadoop namenode:
namenode running as process 15437. Stop it first.
* Starting Hadoop secondarynamenode:
secondarynamenode running as process 3061. Stop it first.
naveensrikanthd#ubuntu:/$ jps
7467 RunJar
8048 RunJar
18363 Jps
No Hadoop process is running and this three statements given above[slf4J] are shuffling between namenode,datanode:
Below given is the log file for the path:
/var/log/hadoop-hdfs/hadoop-hdfs-datanode-ubuntu.out
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
ulimit -a for user hdfs
What should I do to rid of this error anyone please help in crossing this error

The output shows that in fact the namenodes are already running. You should double-check where you think they are supposed to run and what your config says, because it's saying you already succeeded.
The error from log4j has nothing to do with Hadoop functionality.

slf4j and log4j log messages visible in the console but not appending into logfile

I have a problem with slf4j and log4j.. I can see the log messages in the console but those messages are not appending to the file
i am using the following jars.
slf4j-log4j12-1.7.5.jar
slf4j-api-1.7.1.jar
log4j-1.2.17.jar
My log4j.properties file is below.
# Root logger option
log4j.rootLogger=INFO, file
# Direct log messages to a log file
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.File=C:\\myLogFile.log
log4j.appender.file.MaxFileSize=1MB
log4j.appender.file.MaxBackupIndex=1
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss}
%-5p %c{1}:%L - %m%n
and I am getting the following warning in console when i am running my java class
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/1018835/.m2/repository/ch/qos/logback/logback-classic/1.0.10/logback-classic-1.0.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/1018835/.m2/repository/org/slf4j/slf4j-log4j12/1.7.5/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

Please check if file is present at the location.
Also see if your application has write access to the file.