Jboss 4.2 not starting on win 7 64 bit - java
I have JBoss-4.2.3.GA,
Which is unable to start in a given time even if I increase the start time and stop time to 500 Seconds.
I later tried with other versions of JBOSS 4.2 but it is not starting either.
Long back (In some other system) i was getting similar problem in windows 7 64 bit, for which i changed XX:MaxPermSize which solved the issue. But it is not helping here.
I am using eclipse indigo
Version: Indigo Service Release 2
Build id: 20120216-1857
to start the server.
The console after starting the server says:
13:05:08,325 INFO [Server] Starting JBoss (MX MicroKernel)...
13:05:08,325 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
13:05:08,327 INFO [Server] Home Dir: C:\jboss-4.2.3.GA
13:05:08,327 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/
13:05:08,327 INFO [Server] Patch URL: null
13:05:08,327 INFO [Server] Server Name: default
13:05:08,328 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default
13:05:08,328 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3.GA/server/default/
13:05:08,328 INFO [Server] Server Log Dir: C:\jboss-4.2.3.GA\server\default\log
13:05:08,328 INFO [Server] Server Temp Dir: C:\jboss-4.2.3.GA\server\default\tmp
13:05:08,328 INFO [Server] Root Deployment Filename: jboss-service.xml
13:05:08,492 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.
13:05:08,492 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.
13:05:08,493 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
13:05:08,728 INFO [Server] Core system initialized
13:05:09,745 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
13:05:09,746 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:05:09,969 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
13:05:09,969 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
13:05:10,077 INFO [TransactionManagerService] Starting recovery manager
13:05:10,117 INFO [TransactionManagerService] Recovery manager started
13:05:10,117 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
13:05:11,387 INFO [EJB3Deployer] Starting java:comp multiplexer
13:05:12,542 INFO [NativeServerConfig] JBoss Web Services - Native
13:05:12,542 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
13:05:13,070 INFO [Embedded] Catalina naming disabled
13:05:13,149 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;c:\Program Files (x86)\Intel\iCLS Client\;c:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Windows Live\Shared.;C:\Program Files\Java\jdk1.6.0_35\bin;C:\Program Files\TortoiseSVN\bin;.
13:05:13,182 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:13,183 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:13,183 INFO [Catalina] Initialization processed in 113 ms
13:05:13,183 INFO [StandardService] Starting service jboss.web
13:05:13,185 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
13:05:13,215 INFO [Catalina] Server startup in 31 ms
13:05:13,280 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:05:13,602 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
13:05:13,714 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
13:05:13,819 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
13:05:14,231 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
13:05:14,510 INFO [MailService] Mail Service bound to java:/Mail
13:05:14,589 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
13:05:14,607 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
13:05:14,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
13:05:14,642 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
13:05:14,673 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
13:05:14,692 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
13:05:14,722 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
13:05:14,730 INFO [QuartzResourceAdapter] start quartz!!!
13:05:14,768 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
13:05:14,784 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
13:05:14,785 INFO [RAMJobStore] RAMJobStore initialized.
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
13:05:14,785 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:05:15,309 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
13:05:15,444 INFO [A] Bound to JNDI name: queue/A
13:05:15,445 INFO [B] Bound to JNDI name: queue/B
13:05:15,446 INFO [C] Bound to JNDI name: queue/C
13:05:15,447 INFO [D] Bound to JNDI name: queue/D
13:05:15,448 INFO [ex] Bound to JNDI name: queue/ex
13:05:15,457 INFO [testTopic] Bound to JNDI name: topic/testTopic
13:05:15,458 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
13:05:15,459 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
13:05:15,461 INFO [testQueue] Bound to JNDI name: queue/testQueue
13:05:15,479 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
13:05:15,494 INFO [DLQ] Bound to JNDI name: queue/DLQ
13:05:15,549 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
13:05:15,567 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
13:05:15,688 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:15,706 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:15,717 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 7s:388ms
It says started but it is not completely starting.
My server overview is as follows:
I am getting same error as below for 500 seconds, but I am attaching a snapshot for 10 seconds.
I am attaching contents of run.bat, run.conf files in bin folder of Jboss :
run.bat
#echo off
rem -------------------------------------------------------------------------
rem JBoss Bootstrap Script for Win32
rem -------------------------------------------------------------------------
rem $Id: run.bat 73584 2008-05-22 12:09:26Z dimitris#jboss.org $
#if not "%ECHO%" == "" echo %ECHO%
#if "%OS%" == "Windows_NT" setlocal
set DIRNAME=.\
if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
set PROGNAME=run.bat
if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%
pushd %DIRNAME%..
set JBOSS_HOME=%CD%
popd
REM Add bin/native to the PATH if present
if exist "%JBOSS_HOME%\bin\native" set PATH=%JBOSS_HOME%\bin\native;%PATH%
if exist "%JBOSS_HOME%\bin\native" set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path="%PATH%"
rem Find run.jar, or we can't continue
set RUNJAR=%JBOSS_HOME%\bin\run.jar
if exist "%RUNJAR%" goto FOUND_RUN_JAR
echo Could not locate %RUNJAR%. Please check that you are in the
echo bin directory when running this script.
goto END
:FOUND_RUN_JAR
if not "%JAVA_HOME%" == "" goto ADD_TOOLS
set JAVA=java
echo JAVA_HOME is not set. Unexpected results may occur.
echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
goto SKIP_TOOLS
:ADD_TOOLS
set JAVA=%JAVA_HOME%\bin\java
rem A full JDK with toos.jar is not required anymore since jboss web packages
rem the eclipse jdt compiler and javassist has its own internal compiler.
if not exist "%JAVA_HOME%\lib\tools.jar" goto SKIP_TOOLS
rem If exists, point to the JDK javac compiler in case the user wants to
rem later override the eclipse jdt compiler for compiling JSP pages.
set JAVAC_JAR=%JAVA_HOME%\lib\tools.jar
:SKIP_TOOLS
rem If JBOSS_CLASSPATH or JAVAC_JAR is empty, don't include it, as this will
rem result in including the local directory in the classpath, which makes
rem error tracking harder.
if not "%JAVAC_JAR%" == "" set RUNJAR=%JAVAC_JAR%;%RUNJAR%
if "%JBOSS_CLASSPATH%" == "" set RUN_CLASSPATH=%RUNJAR%
if "%RUN_CLASSPATH%" == "" set RUN_CLASSPATH=%JBOSS_CLASSPATH%;%RUNJAR%
set JBOSS_CLASSPATH=%RUN_CLASSPATH%
rem Setup JBoss specific properties
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%
rem Add -server to the JVM options, if supported
"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
if not errorlevel == 1 (set JAVA_OPTS=%JAVA_OPTS% -server)
rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m
rem With Sun JVMs reduce the RMI GCs to once per hour
set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%
rem Setup the java endorsed dirs
set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed
echo ===============================================================================
echo.
echo JBoss Bootstrap Environment
echo.
echo JBOSS_HOME: %JBOSS_HOME%
echo.
echo JAVA: %JAVA%
echo.
echo JAVA_OPTS: %JAVA_OPTS%
echo.
echo CLASSPATH: %JBOSS_CLASSPATH%
echo.
echo ===============================================================================
echo.
:RESTART
"%JAVA%" %JAVA_OPTS% ^
-Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" ^
-classpath "%JBOSS_CLASSPATH%" ^
org.jboss.Main %*
if ERRORLEVEL 10 goto RESTART
:END
if "%NOPAUSE%" == "" pause
:END_NO_PAUSE
run.conf
## -*- shell-script -*- ######################################################
## ##
## JBoss Bootstrap Script Configuration ##
## ##
##############################################################################
### $Id: run.conf 62747 2007-05-02 17:43:36Z dimitris#jboss.org $
#
# This file is optional; it may be removed if not needed.
#
#
# Specify the maximum file descriptor limit, use "max" or "maximum" to use
# the default, as queried by the system.
#
# Defaults to "maximum"
#
#MAX_FD="maximum"
#
# Specify the profiler configuration file to load.
#
# Default is to not load profiler configuration file.
#
#PROFILER=""
#
# Specify the location of the Java home directory. If set then $JAVA will
# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
#
#JAVA_HOME="/opt/java/jdk"
#
# Specify the exact Java VM executable to use.
#
#JAVA=""
#
# Specify options to pass to the Java VM.
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
fi
# Sample JPDA settings for remote socket debuging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
# Sample JPDA settings for shared memory debugging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"
Please help me resolve this issue, so that I can start working on my server.
Look at the line in the log:
13:05:13,182 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080.
It states that the http listens to port 8080 (not port 8090), so you should access through the address localhost:8080.
Where have you configured the http port? You shouldn't change directly the ports of the services, instead use JBoss Service binding Set, Take in mind JBoss opens several ports, so to avoid port conflicts you should change them all.
Check: https://community.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine
UPDATE: The Eclipse screen you've posted doesn't change the port of the JBoss, it's used by Elcipse to know where Jboss http is listening, so you've not really changed the port in JBoss.
On the other hand, a part from the port problem, if you startup the JBoss server from Eclipse, you've to increase the time Eclipse waits JBoss to get started (if JBoss takes more time than the "Server timeout delay" property of the server in Eclipse, it will return an error).
Related
Error when starting HBase standalone on Linux Fedora Hyper-V Virtual Machine
UPDATE UPDATE I have fixed the issue below thank you to Mike for pointing out however, now when I ran the command "jps" to check HMaster process as per the quick start guide suggested, I got the error command not found: I search for this and this command is related to java. Therefore here is my java configuration on my machine: In .bashrc and .bash_profile: export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.fc31.x86_64/jre export JRE_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.fc31.x86_64/jre export PATH=$PATH:$HOME/bin:$JAVA_HOME/bin In hbase-env.sh: export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.fc31.x86_64/jre Location of my java: [hadoop#new-hbase-shuti logs]$ whereis java java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.fc31.x86_64/jre/bin/java /usr/share/man/man1/java.1.gz My java version: [hadoop#new-hbase-shuti logs]$ java -version openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) Here is the new log file from Hbase (hbase-hadoop-master-new-hbase-shuti.log): I follow the quick start guide to just install HBase standalone. Here is my configuration: I was not quite sure which HBase pkg to use but it said to choose the stable one, so I downloaded this: http://mirrors.standaloneinstaller.com/apache/hbase/stable/hbase-2.2.3-bin.tar.gz The conf/hbase-env.sh where I just have JAVA_HOME env path: The conf/hbase-site.xml <configuration> <property> <name>hbase.rootdir</name> <value>file:///home/testuser/hbase</value> </property> <property> <name>hbase.zookeeper.property.dataDir</name> <value>/home/testuser/zookeeper</value> </property> <property> <name>hbase.unsafe.stream.capability.enforce</name> <value>false</value> <description> Controls whether HBase will check for stream capabilities (hflush/hsync). Disable this if you intend to run on LocalFileSystem, denoted by a rootdir with the 'file://' scheme, but be mindful of the NOTE below. WARNING: Setting this to false blinds you to potential data loss and inconsistent system state in the event of process and/or node failures. If HBase is complaining of an inability to use hsync or hflush it's most likely not a false positive. </description> </property> </configuration> Then run from bin, the script start-hbase.sh But I get this error: /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2360: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_USER: invalid variable name /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2455: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_OPTS: invalid variable name SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/hadoop/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/hadoop/hbase-2-2-3/hbase-2.2.3/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.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 [org.slf4j.impl.Log4jLoggerFactory] running master, logging to /home/hadoop/hbase-2-2-3/hbase-2.2.3/bin/../logs/hbase-hadoop-master-new-hbase-shuti.out /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2360: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_USER: invalid variable name /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2455: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_OPTS: invalid variable name SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/hadoop/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/hadoop/hbase-2-2-3/hbase-2.2.3/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.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 [org.slf4j.impl.Log4jLoggerFactory] I have also attached the error log files from HBase below. Could anyone who is familiar with HBase help me please? Thank you very much in advance. Error from "hbase-hadoop-master-new-hbase-shuti.log" Thu 26 Mar 2020 08:59:07 PM CET Starting master on new-hbase-shuti core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 7523 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 7523 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited 2020-03-26 20:59:07,933 INFO [main] master.HMaster: STARTING service HMaster 2020-03-26 20:59:07,934 INFO [main] util.VersionInfo: HBase 2.2.3 2020-03-26 20:59:07,934 INFO [main] util.VersionInfo: Source code repository git://hao-OptiPlex-7050/home/hao/open_source/hbase revision=6a830d87542b766bd3dc4cfdee28655f62de3974 2020-03-26 20:59:07,934 INFO [main] util.VersionInfo: Compiled by hao on 2020年 01月 10日 星期五 18:27:51 CST 2020-03-26 20:59:07,934 INFO [main] util.VersionInfo: From source with checksum 097925184b85f6995e20da5462b10f3f 2020-03-26 20:59:08,190 INFO [main] master.HMasterCommandLine: Starting a zookeeper cluster 2020-03-26 20:59:08,204 INFO [main] server.ZooKeeperServer: Server environment:zookeeper.version=3.4.10-39d3a4f269333c922ed3db283be479f9deacaa0f, built on 03/23/2017 10:13 GMT 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:host.name=new-hbase-shuti.mshome.net 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.version=1.8.0_222 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.vendor=Oracle Corporation 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.home=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.fc31.x86_64/jre 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: vices-core-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-applications-unmanaged-am-launcher-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-tests-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-api-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-client-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-timeline-pluginstorage-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-resourcemanager-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-applicationhistoryservice-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-sharedcachemanager-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-server-common-3.1.3.jar:/home/hadoop/hadoop/share/hadoop/yarn/hadoop-yarn-common-3.1.3.jar:/home/hadoop/hbase-2-2-3/hbase-2.2.3/bin/../lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.jar 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.library.path=/home/hadoop/hadoop//lib/native 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.io.tmpdir=/tmp 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:java.compiler=<NA> 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:os.name=Linux 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:os.arch=amd64 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:os.version=5.3.7-301.fc31.x86_64 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:user.name=hadoop 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:user.home=/home/hadoop 2020-03-26 20:59:08,205 INFO [main] server.ZooKeeperServer: Server environment:user.dir=/home/hadoop/hbase-2-2-3/hbase-2.2.3/bin 2020-03-26 20:59:08,207 ERROR [main] master.HMasterCommandLine: Master exiting java.io.IOException: Unable to create data directory /home/testuser/zookeeper/zookeeper_0/version-2 at org.apache.zookeeper.server.persistence.FileTxnSnapLog.<init>(FileTxnSnapLog.java:85) at org.apache.zookeeper.server.ZooKeeperServer.<init>(ZooKeeperServer.java:224) at org.apache.hadoop.hbase.zookeeper.MiniZooKeeperCluster.startup(MiniZooKeeperCluster.java:229) at org.apache.hadoop.hbase.zookeeper.MiniZooKeeperCluster.startup(MiniZooKeeperCluster.java:187) at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:210) at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:140) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:149) at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2940) Error from "hbase-hadoop-master-new-hbase-shuti.out": /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2360: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_USER: invalid variable name /home/hadoop/hadoop/bin/../libexec/hadoop-functions.sh: line 2455: HADOOP_ORG.APACHE.HADOOP.HBASE.UTIL.GETJAVAPROPERTY_OPTS: invalid variable name SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/hadoop/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/hadoop/hbase-2-2-3/hbase-2.2.3/lib/client-facing-thirdparty/slf4j-log4j12-1.7.25.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 [org.slf4j.impl.Log4jLoggerFactory]
After digging in... hadoop I found that, in my case, it has something to do
with ubuntu user permission ...
vi /opt/hadoop/libexec/hadoop-functions.sh
function hadoop_verify_user_resolves
{
...
}
so I've decided to add those lines in
/opt/hbase/conf/hbase-env.sh
export HBASE_SSH_OPTS="-p 22 -l daniel"
export HBASE_OPTS="$HBASE_OPTS -XX:+UseConcMarkSweepGC"
I have corrected my JAVA_HOME path environment to make sure it points to jdk instead of jre.
Nifi commands on windows
In my current project, I have been using apache-nifi on Windows operating system. I have extracted nifi-0.7.0-bin.zip file in C:\. Now, when I run \bin\run-nifi.bat as an administrator I see the following message on the command line and I am not able to run nifi. Could you please suggest what should I do in order to run the nifi. the content of app.log file as follows 2016-08-08 11:41:57,716 INFO [main] org.apache.nifi.NiFi Launching NiFi... 2016-08-08 11:41:57,851 INFO [main] org.apache.nifi.BootstrapListener Started Bootstrap Listener, Listening for incoming requests on port 50050 2016-08-08 11:41:57,877 INFO [main] org.apache.nifi.BootstrapListener Successfully initiated communication with Bootstrap 2016-08-08 11:42:59,485 WARN [Timer-0] org.apache.nifi.NiFi NiFi has detected that this box is not responding within the expected timing interval, which may cause Processors to be scheduled erratically. Please see the NiFi documentation for more information. The content of nifi-bootstrap.log file is as follows: 2016-08-08 11:41:57,279 INFO [main] o.a.n.b.NotificationServiceManager Successfully loaded the following 0 services: [] 2016-08-08 11:41:57,286 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_STARTED 2016-08-08 11:41:57,286 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_STOPPED 2016-08-08 11:41:57,286 INFO [main] org.apache.nifi.bootstrap.RunNiFi Registered no Notification Services for Notification Type NIFI_DIED 2016-08-08 11:41:57,298 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi... 2016-08-08 11:41:57,299 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: C:\NIFI-0~1.0 2016-08-08 11:41:57,299 INFO [main] org.apache.nifi.bootstrap.Command Command: C:\Program Files\Java\jdk1.8.0_102\bin\java.exe -classpath C:\NIFI-0~1.0\.\conf;C:\NIFI-0~1.0\.\lib\jcl-over-slf4j-1.7.12.jar;C:\NIFI-0~1.0\.\lib\jul-to-slf4j-1.7.12.jar;C:\NIFI-0~1.0\.\lib\log4j-over-slf4j-1.7.12.jar;C:\NIFI-0~1.0\.\lib\logback-classic-1.1.3.jar;C:\NIFI-0~1.0\.\lib\logback-core-1.1.3.jar;C:\NIFI-0~1.0\.\lib\nifi-api-0.7.0.jar;C:\NIFI-0~1.0\.\lib\nifi-documentation-0.7.0.jar;C:\NIFI-0~1.0\.\lib\nifi-nar-utils-0.7.0.jar;C:\NIFI-0~1.0\.\lib\nifi-properties-0.7.0.jar;C:\NIFI-0~1.0\.\lib\nifi-runtime-0.7.0.jar;C:\NIFI-0~1.0\.\lib\slf4j-api-1.7.12.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.properties.file.path=C:\NIFI-0~1.0\.\conf\nifi.properties -Dnifi.bootstrap.listen.port=50049 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=C:\NIFI-0~1.0\bin\..\\logs org.apache.nifi.NiFi 2016-08-08 11:41:57,866 WARN [NiFi Bootstrap Command Listener] org.apache.nifi.bootstrap.RunNiFi Failed to set permissions so that only the owner can read status file C:\NIFI-0~1.0\bin\..\run\nifi.pid; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file 2016-08-08 11:41:57,876 INFO [NiFi Bootstrap Command Listener] org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for Bootstrap requests on port 50050
I recommend running NiFi with the current directory context in the bin directory: Open a new command prompt window Change to the NiFi bin directory, cd c:\nifi-0.7\bin From c:\nifi-0.7\bin, execute run-nifi.bat I believe run-nifi.bat depends on finding nifi-env.bat in the current directory, rather than finding it relative to its own path. If you ran C:\...\nifi-0.7.0\bin\run-nifi.bat, I think you would see that error.
Cannot Start Sonarqube Server with the latest Version
Facing Java process launcher error while starting Sonar server. Please note that we are have used Sonarqube-4.5.7, sonarqube-5.0.1, Sonarqube 5.6 and JDK 7,8 combinations . but still no luck below is the log : 2016.06.20 18:31:24 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[search]: C:\Program Files\Java\jre7\bin\java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djava.net.preferIPv4Stack=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=C:\Users\swmuthuk\Documents\sonarqube-5.0.1\temp -cp ./lib/common/*;./lib/search/* org.sonar.search.SearchServer C:\Users\swmuthuk\AppData\Local\Temp\sq-process2908084003470791693properties 2016.06.20 18:31:25 INFO sea[o.s.p.ProcessEntryPoint] Starting search 2016.06.20 18:31:25 INFO sea[o.s.s.SearchServer] Starting Elasticsearch[sonarqube] on port 9001 2016.06.20 18:31:25 INFO sea[o.elasticsearch.node] [sonar-1466427684530] version[1.1.2], pid[4912], build[e511f7b/2014-05-22T12:27:39Z] 2016.06.20 18:31:25 INFO sea[o.elasticsearch.node] [sonar-1466427684530] initializing ... 2016.06.20 18:31:25 INFO sea[o.e.plugins] [sonar-1466427684530] loaded [], sites [] 2016.06.20 18:31:27 INFO sea[o.elasticsearch.node] [sonar-1466427684530] initialized 2016.06.20 18:31:27 INFO sea[o.elasticsearch.node] [sonar-1466427684530] starting ... 2016.06.20 18:31:27 WARN sea[o.s.p.ProcessEntryPoint] Fail to start search org.elasticsearch.transport.BindTransportException: Failed to bind to [9001]
I was able to resolve the issue. Issue is the port assigned could be used by any other process. Hence you could not bind that port. To use the free port. follow the below : In ../conf/sonar.properties, Assign 0 to sonar.search.port and remove #. Save the file and start the sonar again
You already have a process bound to the 9001 port, most probably an Elastic Search from a previous SonarQube set up, and that was not stopped properly. Search for that process id, kill it, and then start SonarQube again, it should work.
Start JBoss Server with NetBeans
I am trying to run the JBoss server on Netbeans but the log is blocked at something like: [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting The entire log is : Calling "C:\jboss-as-7.1.1.Finale\bin\standalone.conf.bat" "JAVA_OPTS already set in environment; overriding default settings with values : -Xms128mx -Xmx512ms -XX:MaxPermSize=256m" ___________________________ JBoss Bootstrap Environment JBOSS_HOME: C:\jboss-7.1.1.Final JAVA: C:\Program Files\Java\jdk1.8.0_65\bin\java JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat - Xms128m -Xmx512m -XX:MaxPermSize=256m __________________________ INFOS [org.jboss.modules]JBoss Modules version 1.1.1.GA INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting I saw that the jboss repertory should be at the source (C:); I did. My environment variables must be good : JAVA_HOME : C:\Program Files\Java\jdk1.7.0_65 JBOSS_HOME : C:\jboss-as-7.1.1.Final JBOSS_CONF : default When I added the server on Netbeans : 1- I chose the "JBoss Application Server 2- I chose the Server Location : c:\jboss-as-7.1.1.Final 3- The properties : Domain : standalone ; Domain Path : C:\jboss-as-7.1.1.Final\standalone ; Host : localhost ; Port : 8081 Can someone help me and tell me what's wrong ? Thanks
Looks like you are trying to start JBoss 7.1.1 with Java 8, which is not supported. You wrote that your JAVA_HOME is set to C:\Program Files\Java\jdk1.7.0_65, but the log shows that JBoss was started with jdk1.8.0_65. JAVA: C:\Program Files\Java\jdk1.8.0_65\bin\java So it seems that the JAVA_HOME variable is not picked up by the start script. Try starting JBoss with Java 7.
Hadoop on Mac OS X 'HadoopIllegalArgumentException: An XAttr name must be prefixed' error
Today I tried to install Hadoop on my Mac OS X Lion following the instructions at Setting up Hadoop 2.4 and Pig 0.12 on OSX locally I have correctly set the JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home set both ~/.bash_profile and .bashrc and successfully installed the latest version of Hadoop (2.6.0) using brew and edited those 4 configuration files: hdfs.site.xml, core-site.xml, mapred-site.xml, yarn-site.xml accordingly. But running: ./bin/hdfs namenode -format gives: 15/01/29 17:42:01 INFO namenode.NameNode: STARTUP_MSG: /************************************************************ STARTUP_MSG: Starting NameNode STARTUP_MSG: host = Venuses-Mac-mini.local/192.168.1.51 STARTUP_MSG: args = [-format] STARTUP_MSG: version = 2.6.0 STARTUP_MSG: classpath = /usr/local/Cellar/hadoop/2.6.0/libexec /etc/hadoop:/usr/local/Cellar/hadoop/2.6.0/libexec/share/hadoop/common /lib/activation-1.1.jar <TRUNCATED - Big Chunk of Code Containing .jar Filenames> STARTUP_MSG: build = https://git-wip-us.apache.org/repos /asf/hadoop.git -r e3496499ecb8d220fba99dc5ed4c99c8f9e33bb1; compiled by 'jenkins' on 2014-11-13T21:10Z STARTUP_MSG: java = 1.6.0_29 <TRUNCATED - Big Chunk of .jar Filnames TRUNCATED> ************************************************************/ 15/01/29 17:42:01 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT] 15/01/29 17:42:01 INFO namenode.NameNode: createNameNode [-format] 2015-01-29 17:42:02.551 java[1016:1903] Unable to load realm info from SCDynamicStore 15/01/29 17:42:02 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable Formatting using clusterid: CID-aaa7a5a6-3e82-4166-8039-16046f1b4761 <TRUNCATED> 15/01/29 17:42:03 ERROR namenode.FSNamesystem: FSNamesystem initialization failed. org.apache.hadoop.HadoopIllegalArgumentException: An XAttr name must be prefixed with user/trusted/security/system/raw, followed by a '.' at org.apache.hadoop.hdfs.XAttrHelper.buildXAttr(XAttrHelper.java:72) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.<init>(FSDirectory.java:137) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:894) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:755) at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:934) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504) 15/01/29 17:42:03 INFO namenode.FSNamesystem: Stopping services started for active state 15/01/29 17:42:03 INFO namenode.FSNamesystem: Stopping services started for standby state 15/01/29 17:42:03 FATAL namenode.NameNode: Failed to start namenode. <TRUNCATED> 15/01/29 17:42:03 INFO util.ExitUtil: Exiting with status 1 15/01/29 17:42:03 INFO namenode.NameNode: SHUTDOWN_MSG: 2 versions of Java is installed on my Mac Hadoop takes the older version, 1.6.0_29, not the current version, 1.7.0_72. I don't know hot to make Hadoop take the current Java version into account. NOTE: I 've made an extensive search on Google and could not find a solution for this particular error. Thanks.
What do you get when you run the following in a Terminal shell? /usr/libexec/java_home If that returns your 1.6 JDK, then it could be that somewhere hadoop is using that command to determine which java to use. For example, one place that might be happening, is the file '/usr/local/Cellar/hadoop/2.6.0/libexec/etc/hadoop/hadoop-env.sh'. Line 25 is: export JAVA_HOME="$(/usr/libexec/java_home)" Try changing that to: export JAVA_HOME="$(/usr/libexec/java_home -v1.7)" In order to set JAVA_HOME to your 1.7 JDK. Or it could be that some other hadoop file is doing a similar thing to find Java.