aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sweeney <kevi...@apache.org>
Subject Re: unknown job error
Date Wed, 15 Oct 2014 21:12:25 GMT
Looks like something is already listening on port 9999

One way to find out what that is is with netstat

sudo netstat -tlnp | grep 9999

will tell you the PID of whatever is listening on that port.



On Wed, Oct 15, 2014 at 1:16 PM, Joe Stein <joe.stein@stealth.ly> wrote:

> Hi Kevin, yes, I am trying to use Aurora on a real CentOS 6.5 x 9 node
> Mesos 0.20.1 cluster
>
> I copied (and edited) the upstart scripts and that worked, thanks!!!
>
> Two new issues
>
> 1) still getting mesos-log error.  Mesos is running on that box and
> mesos-log works from the command line. Not sure why the script is having
> issue???
>
> /opt/apache/incubator-aurora$mesos-log
> Usage: mesos-log <command> [OPTIONS]
>
> Available commands:
>     help
>     replica
>     read
>     initialize
>     benchmark
>
> 2) aurora schedular isn't starting... bind exception :(
>
> I changed the port -http_port=9999 and I am sure nothing is running on it
> but still error.  maybe another port trying to bind also? JMX or something?
>
> here is my config
>
> /opt/apache/incubator-aurora$cat /etc/init/aurora-scheduler.conf
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> #     http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> #
> description "aurora scheduler"
> start on stopped rc RUNLEVEL=[2345]
> respawn
> post-stop exec sleep 5
>
> # Environment variables control the behavior of the Mesos scheduler driver
> (libmesos).
> env GLOG_v=0
> env LIBPROCESS_PORT=8083
> env LIBPROCESS_IP=172.31.128.251
> env AURORA_HOME=/usr/local/aurora
> env DIST_DIR=/opt/apache/incubator-aurora/dist
>
> # Flags that control the behavior of the JVM.
> env JAVA_OPTS='-Djava.library.path=/usr/local/lib
> -Dlog4j.configuration="file:///etc/zookeeper/conf/log4j.properties"'
>
> exec $DIST_DIR/install/aurora-scheduler/bin/aurora-scheduler \
>   -cluster_name=example \
>   -http_port=9999 \
>   -native_log_quorum_size=1 \
>   -zk_endpoints=172.31.128.251:2181,172.31.128.252:2181,
> 172.31.128.253:2181
> \
>   -mesos_master_address=zk://172.31.128.251:2181,172.31.128.252:2181,
> 172.31.128.253:2181/mesos-gobig \
>   -serverset_path=/aurora/scheduler \
>   -native_log_zk_group_path=/aurora/replicated-log \
>   -native_log_file_path=$AURORA_HOME/scheduler/db \
>   -backup_dir=$AURORA_HOME/scheduler/backups \
>   -thermos_executor_path=$DIST_DIR/thermos_executor.sh \
>   -gc_executor_path=$DIST_DIR/gc_executor.pex \
>   -enable_beta_updater=true \
>   -vlog=INFO \
>   -logtostderr
>
> 1015 19:59:00.705 THREAD1 com.twitter.common.application.AppLauncher.run:
> Executing startup actions.
> E1015 19:59:00.775 THREAD1 com.twitter.common.application.AppLauncher.run:
> Startup action failed, quitting.
> java.lang.IllegalStateException: Failed to launch
>
> org.apache.aurora.scheduler.http.JettyServerModule$HttpServerLauncher@e966006
> at
>
> com.twitter.common.application.modules.LocalServiceRegistry.ensureLaunched(LocalServiceRegistry.java:138)
> at
>
> com.twitter.common.application.modules.LifecycleModule$LocalServiceLauncher.execute(LifecycleModule.java:195)
> at
>
> com.twitter.common.application.StartupRegistry.execute(StartupRegistry.java:52)
> at com.twitter.common.application.AppLauncher.run(AppLauncher.java:94)
> at com.twitter.common.application.AppLauncher.launch(AppLauncher.java:181)
> at com.twitter.common.application.AppLauncher.launch(AppLauncher.java:142)
> at
> org.apache.aurora.scheduler.app.SchedulerMain.main(SchedulerMain.java:227)
> Caused by:
> com.twitter.common.application.modules.LifecycleModule$LaunchException:
> Failed to start jetty server: java.net.BindException: Address already in
> use
> at
>
> org.apache.aurora.scheduler.http.JettyServerModule$HttpServerLauncher.launch(JettyServerModule.java:284)
> at
>
> com.twitter.common.application.modules.LocalServiceRegistry.ensureLaunched(LocalServiceRegistry.java:134)
> ... 6 more
>
>
> /*******************************************
>  Joe Stein
>  Founder, Principal Consultant
>  Big Data Open Source Security LLC
>  http://www.stealth.ly
>  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> ********************************************/
>
> On Wed, Oct 15, 2014 at 3:40 PM, Kevin Sweeney <kevints@apache.org> wrote:
>
> > It looks like you're trying to install on a system outside the vagrant
> > image? The aurorabuild scripts are more for development in a vagrant
> image
> > and will need some work to work on another system. What distribution and
> > version is this?
> >
> > The start: Unknown job error messages come from upstart - you need to
> > create /etc/init/aurora-scheduler.conf (if you're running on a
> distribution
> > that uses upstart). There are some example configs in the repo under
> > examples/vagrant/upstart.
> >
> > Another thing that jumps out: you're missing the mesos-log command (part
> of
> > the mesos distribution). You'll need that to initialize the replicated
> log
> > for a new installation.
> >
> > On Wed, Oct 15, 2014 at 12:31 PM, Joe Stein <joe.stein@stealth.ly>
> wrote:
> >
> > > Hey, getting further :)
> > >
> > > Building is working well now but getting error at the end when
> deploying
> > to
> > > server.
> > >
> > > stop: Unknown job: aurora-scheduler
> > > start: Unknown job: aurora-scheduler
> > >
> > > Thanks in advance!!!
> > >
> > > /opt/apache/incubator-aurora$aurorabuild scheduler
> > > :buildSrc:compileJava UP-TO-DATE
> > > :buildSrc:compileGroovy UP-TO-DATE
> > > :buildSrc:processResources UP-TO-DATE
> > > :buildSrc:classes UP-TO-DATE
> > > :buildSrc:jar UP-TO-DATE
> > > :buildSrc:assemble UP-TO-DATE
> > > :buildSrc:compileTestJava UP-TO-DATE
> > > :buildSrc:compileTestGroovy UP-TO-DATE
> > > :buildSrc:processTestResources UP-TO-DATE
> > > :buildSrc:testClasses UP-TO-DATE
> > > :buildSrc:test UP-TO-DATE
> > > :buildSrc:check UP-TO-DATE
> > > :buildSrc:build UP-TO-DATE
> > > :bootstrapThrift UP-TO-DATE
> > > :checkPython
> > > :generateSources UP-TO-DATE
> > > :compileGeneratedJava UP-TO-DATE
> > > :processGeneratedResources UP-TO-DATE
> > > :generatedClasses UP-TO-DATE
> > > :compileJava UP-TO-DATE
> > > :processResources UP-TO-DATE
> > > :classes UP-TO-DATE
> > > :jar UP-TO-DATE
> > > :startScripts UP-TO-DATE
> > > :installApp UP-TO-DATE
> > >
> > > BUILD SUCCESSFUL
> > >
> > > Total time: 11.005 secs
> > > sudo: mesos-log: command not found
> > > Replicated log initialization failed with code 1 (likely already
> > > initialized).
> > > stop: Unknown job: aurora-scheduler
> > > start: Unknown job: aurora-scheduler
> > >
> > > /*******************************************
> > >  Joe Stein
> > >  Founder, Principal Consultant
> > >  Big Data Open Source Security LLC
> > >  http://www.stealth.ly
> > >  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > > ********************************************/
> > >
> >
>

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