oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From BW <bw...@mysoftcloud.com>
Subject Re: OODT start
Date Sat, 07 Apr 2018 23:50:22 GMT
Yeah, killed PID’s for Java.  Clean restart. Filemgr shows up, workflow,
resource, crawler down all down.

On Sat, Apr 7, 2018 at 4:19 PM Chris Mattmann <mattmann@apache.org> wrote:

> Need to make sure that all java is off, PID files aren’t there for a clean
> restart
> then ./bin/oodt start.
>
>
>
> Should work fine.
>
>
>
>
>
>
>
> From: BW <bwebb@mysoftcloud.com>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Date: Saturday, April 7, 2018 at 1:55 PM
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
> Subject: Re: OODT start
>
>
>
> vim oodt.out
>
>
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
>
> found. Is File Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> ID file (/Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid)
>
> found with PID 3795 but no matching process was found. Removed
>
> /Users/bw/dev/workspace/oodt/filemgr/run/cas.filemgr.pid, now
>
> FileManager can be started.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found. Is Resource Manager still running? Start aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found. Is Workflow Manager still running? Start aborted.
>
>
>
> Using CATALINA_BASE:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_HOME:   /Users/bw/dev/workspace/oodt/tomcat
>
>
>
> Using CATALINA_TMPDIR: /Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> Using JRE_HOME:
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/resmgr/run/cas.resmgr.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> PID file (/Users/bw/dev/workspace/oodt/workflow/run/cas.workflow.pid)
>
> found but no matching process was found. Stop aborted.
>
>
>
> On Sat, Apr 7, 2018 at 1:29 PM, Chris Mattmann <mattmann@apache.org>
> wrote:
>
> Suggestion: ./bin/oodt stop
>
>
>
> Confirm that ps aux | grep java returns nothing (you may need to wait a
> few seconds)
>
> Then, ./bin/oodt start
>
>
>
> What is in the output of logs/oodt.out ?
>
>
>
>
>
>
>
> Cheers,
>
>
>
> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: BW <bwebb@mysoftcloud.com>
>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
> Date: Saturday, April 7, 2018 at 1:23 PM
>
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
> Subject: Re: OODT start
>
>
>
>
>
>
>
> Well, shut down odor, restarted.   filemgr resource shows up, other
>
>
>
> mangers down.
>
>
>
>
>
>
>
> ps aux |grep java
>
>
>
>
>
>
>
> bw               4168   0.3  2.1  8433916 348536 s000  S    12:50PM
>
>
>
> 0:19.47
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
>
>
>
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
>
>
>
>
> -Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/tomcat/conf/logging.properties
>
>
>
> -Djava.endorsed.dirs=/Users/bw/dev/workspace/oodt/tomcat/common/endorsed
>
>
>
> -classpath
> :/Users/bw/dev/workspace/oodt/tomcat/bin/bootstrap.jar:/Users/bw/dev/workspace/oodt/tomcat/bin/commons-logging-api.jar
>
>
>
> -Dcatalina.base=/Users/bw/dev/workspace/oodt/tomcat
>
>
>
> -Dcatalina.home=/Users/bw/dev/workspace/oodt/tomcat
>
>
>
> -Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/tomcat/temp
>
>
>
> org.apache.catalina.startup.Bootstrap start start
>
>
>
>
>
>
>
> bw               4175   0.1  0.6  8273820 105576 s000  S    12:50PM
>
>
>
> 0:03.66
> /Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
>
>
>
> -Djava.ext.dirs=/Users/bw/dev/workspace/oodt/filemgr/lib
>
>
>
>
> -Djava.util.logging.config.file=/Users/bw/dev/workspace/oodt/filemgr/etc/logging.properties
>
>
>
>
> -Dorg.apache.oodt.cas.filemgr.properties=/Users/bw/dev/workspace/oodt/filemgr/etc/filemgr.properties
>
>
>
> -Djava.io.tmpdir=/Users/bw/dev/workspace/oodt/temp
>
>
>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum 9000
>
>
>
>
>
>
>
> bw               3893   0.1  0.3  8229892  47624 s000  S    12:29PM
>
>
>
> 0:04.39 /usr/bin/java -Djava.ext.dirs=../lib
>
>
>
> org.apache.oodt.cas.resource.system.extern.XmlRpcBatchStub
>
>
>
> -Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode=true
>
>
>
> -Dorg.apache.oodt.cas.pge.task.status.legacyMode=true --portNum 2001
>
>
>
>
>
>
>
> bw               4202   0.0  0.0  2432804   1988 s000  S+    1:21PM
>
>
>
> 0:00.00 grep java
>
>
>
>
>
>
>
> Webbs-MacBook-Pro-2:bin bw$
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 1:03 PM, Chris Mattmann <mattmann@apache.org>
> wrote:
>
>
>
> What are the results of ps aux | grep filemgr
>
>
>
>
>
>
>
> Or ps aux | grep java?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: BW <webb@apache.org>
>
>
>
> Reply-To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
>
>
> Date: Saturday, April 7, 2018 at 12:58 PM
>
>
>
> To: "dev@oodt.apache.org" <dev@oodt.apache.org>
>
>
>
> Subject: Re: OODT start
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Using
> https://cwiki.apache.org/confluence/display/OODT/RADiX+Powered+By+OODT.
>
>
>
>
>
>
>
> Is that up to date?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 12:38 PM, BW <webb@apache.org> wrote:
>
>
>
>
>
>
>
> Opened http://localhost:8080/opsui/status/ which shows Managers are
>
>
>
>
>
>
>
> down.  Thoughts?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 12:25 PM, BW <webb@apache.org> wrote:
>
>
>
>
>
>
>
> Ok. Figured it out.  Had to set in profile.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>     echo "export JAVA_HOME=`/usr/libexec/java_home`" >> ~/.profile
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Webbs-MacBook-Pro-2:bin bw$ . ~/.profile
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Looks good.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 11:44 AM, BW <webb@apache.org> wrote:
>
>
>
>
>
>
>
> Did it.  But now reverted back to it not thinking JAVA_HOME, JRE_HOME
>
>
>
>
>
>
>
> is set; when they are set in etc/profile and echo's correctly.
>
>
>
>
>
>
>
> Confused.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 10:59 AM, Chris Mattmann <mattmann@apache.org>
> wrote:
>
>
>
>
>
>
>
> Got it.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I think that you should killall java, then make sure PID files are removed
> from */run (e.g., filemgr, workflow and resmgr).
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Then try restarting.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Cheers,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From: BW <webb@apache.org>
>
>
>
>
>
>
>
> Reply-To: <dev@oodt.apache.org>
>
>
>
>
>
>
>
> Date: Saturday, April 7, 2018 at 10:56 AM
>
>
>
>
>
>
>
> To: <dev@oodt.apache.org>
>
>
>
>
>
>
>
> Subject: Re: OODT start
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Ok. I had lower case.  Should of been "../Contents/Home"
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Now though File/Resource/Workflow managers fail to start.  Nothing in
> browser.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sat, Apr 7, 2018 at 10:27 AM, BW <webb@apache.org> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> After mvn install:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ./bin/oodt start
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At least one of these environment variable is needed to run this program
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Webbs-MacBook-Pro-2:bin bw$ echo $JAVA_HOME
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> /Library/Java/JavaVirtualMachines/jdk1.8.0.40.jdk/contents/home "
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Any ideas, anybody?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks. -BW
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message