You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Henry Saputra <he...@gmail.com> on 2014/06/02 19:40:18 UTC
No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Hi Guys,
I did git pull last week and when I try to run and schedule job to my
Vagrant's setup of Aurora :
vagrant@192:~$ aurora create devcluster/www-data/devel/hello_world
/vagrant/hello_world.aurora
INFO] Creating job hello_world
INFO] Response from scheduler: OK (message: None)
INFO] Job url: http://192.168.33.7:8081/scheduler/www-data/devel/hello_world
However when I tried to connect to
http://192.168.33.7:8081/scheduler/www-data/devel/hello_world via
browser it finally gave me 404.
I do not see access logged to aurora-scheduler.log file.
Anyone else seen this behavior or just me?
I have been doing vagrant destroy and rebuild the stuff with no luck =(
- Henry
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Kevin Sweeney <ke...@apache.org>.
Hi Henry,
Were we able to help you get this working? I just tried out the tutorial on
master (467f842) after vagrant destroy -f and git clean -fdx and it worked
in my environment [1].
[1]
% dpkg -l virtualbox
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================-==============-==============-============================================
ii virtualbox 4.3.10-dfsg-1 amd64 x86 virtualization
solution - base binaries
% vagrant -v
Vagrant 1.4.3
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
On Thu, Jun 5, 2014 at 10:17 AM, Jay Buffington <me...@jaybuff.com> wrote:
> On Thu, Jun 5, 2014 at 10:02 AM, Henry Saputra <he...@gmail.com>
> wrote:
>
> >
> > But seemed like no TCP bound to http://192.168.33.7:8081
> >
> >
> Is the aurora-scheduler process running? You can check like this:
>
> $ ps aux |grep [a]urora
> root 19711 0.0 0.0 4116 488 ? S 16:47 0:00 cronolog
> --link=/var/log/aurora/aurora-scheduler.log
> /var/log/aurora/aurora-scheduler.%Y%m%d.log
> root 19728 0.0 0.2 48532 1432 ? S 16:47 0:00 su -s
> /bin/bash -c /usr/local/bin/aurora-scheduler.sh nobody
> nobody 19729 2.4 60.9 2124104 306132 ? Ssl 16:47 0:40
> /opt/oracle-jdk-1.7.0_45/bin/java -server -Xmx1g -Xms1g
> -Djava.library.path=/usr/lib64 -classpath
>
> /usr/local/aurora-scheduler/lib/quark-aurora-package-0.5.1-SNAPSHOT.jar:/usr/local/aurora-scheduler/lib/aopalliance-1.0.jar:/usr/local/aurora-scheduler/lib/jsr305-2.0.1.jar:/usr/local/aurora-scheduler/lib/guava-16.0.jar:/usr/local/aurora-scheduler/lib/guice-3.0.jar:/usr/local/aurora-scheduler/lib/protobuf-java-2.5.0.jar:/usr/local/aurora-scheduler/lib/h2-1.4.177.jar:/usr/local/aurora-scheduler/lib/jersey-core-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-json-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-server-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-servlet-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-guice-1.17.1.jar:/usr/local/aurora-scheduler/lib/commons-lang-2.6.jar:/usr/local/aurora-scheduler/lib/javax.inject-1.jar:/usr/local/aurora-scheduler/lib/servlet-api-2.5.jar:/usr/local/aurora-scheduler/lib/log4j-1.2.17.jar:/usr/local/aurora-scheduler/lib/stringtemplate-3.2.1.jar:/usr/local/aurora-scheduler/lib/mesos-0.18.0.jar:/usr/local/aurora-scheduler/lib/libthrift-0.9.1.jar:/usr/local/aurora-scheduler/lib/zookeeper-3.3.4.jar:/usr/local/aurora-scheduler/lib/mybatis-3.2.7.jar:/usr/local/aurora-scheduler/lib/mybatis-guice-3.6.jar:/usr/local/aurora-scheduler/lib/quartz-2.2.1.jar:/usr/local/aurora-scheduler/lib/slf4j-jdk14-1.6.1.jar:/usr/local/aurora-scheduler/lib/log4j-0.0.7.jar:/usr/local/aurora-scheduler/lib/bootstrap-0.0.4.jar:/usr/local/aurora-scheduler/lib/jquery-0.0.4.jar:/usr/local/aurora-scheduler/lib/client-flagged-0.0.5.jar:/usr/local/aurora-scheduler/lib/client-0.0.5.jar:/usr/local/aurora-scheduler/lib/candidate-0.0.64.jar:/usr/local/aurora-scheduler/lib/client-0.0.56.jar:/usr/local/aurora-scheduler/lib/group-0.0.69.jar:/usr/local/aurora-scheduler/lib/server-set-1.0.74.jar:/usr/local/aurora-scheduler/lib/singleton-service-0.0.85.jar:/usr/local/aurora-scheduler/lib/application-http-0.0.59.jar:/usr/local/aurora-scheduler/lib/application-module-applauncher-0.0.51.jar:/usr/local/aurora-scheduler/lib/application-module-http-0.0.62.jar:/usr/local/aurora-scheduler/lib/application-module-lifecycle-0.0.48.jar:/usr/local/aurora-scheduler/lib/application-module-log-0.0.56.jar:/usr/local/aurora-scheduler/lib/application-module-stats-0.0.44.jar:/usr/local/aurora-scheduler/lib/application-0.0.73.jar:/usr/local/aurora-scheduler/lib/args-0.2.9.jar:/usr/local/aurora-scheduler/lib/base-0.0.87.jar:/usr/local/aurora-scheduler/lib/collections-0.0.74.jar:/usr/local/aurora-scheduler/lib/dynamic-host-set-0.0.44.jar:/usr/local/aurora-scheduler/lib/inject-timed-0.0.11.jar:/usr/local/aurora-scheduler/lib/inject-0.0.35.jar:/usr/local/aurora-scheduler/lib/io-0.0.53.jar:/usr/local/aurora-scheduler/lib/jdk-logging-0.0.44.jar:/usr/local/aurora-scheduler/lib/logging-0.0.61.jar:/usr/local/aurora-scheduler/lib/net-http-filters-0.0.6.jar:/usr/local/aurora-scheduler/lib/net-util-0.0.80.jar:/usr/local/aurora-scheduler/lib/quantity-0.0.71.jar:/usr/local/aurora-scheduler/lib/stats-0.0.91.jar:/usr/local/aurora-scheduler/lib/testing-easymock-0.0.4.jar:/usr/local/aurora-scheduler/lib/thrift-0.0.68.jar:/usr/local/aurora-scheduler/lib/util-executor-service-shutdown-0.0.49.jar:/usr/local/aurora-scheduler/lib/util-system-mocks-0.0.72.jar:/usr/local/aurora-scheduler/lib/util-templating-0.0.25.jar:/usr/local/aurora-scheduler/lib/util-testing-0.0.10.jar:/usr/local/aurora-scheduler/lib/util-0.0.94.jar:/usr/local/aurora-scheduler/lib/zookeeper-testing-0.0.45.jar:/usr/local/aurora-scheduler/lib/cglib-2.2.1-v20090111.jar:/usr/local/aurora-scheduler/lib/jettison-1.1.jar:/usr/local/aurora-scheduler/lib/jaxb-impl-2.2.3-1.jar:/usr/local/aurora-scheduler/lib/jackson-core-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-mapper-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-jaxrs-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-xc-1.9.2.jar:/usr/local/aurora-scheduler/lib/asm-3.1.jar:/usr/local/aurora-scheduler/lib/guice-servlet-3.0.jar:/usr/local/aurora-scheduler/lib/antlr-2.7.7.jar:/usr/local/aurora-scheduler/lib/commons-lang3-3.1.jar:/usr
>
>
>
> If it is you can check if that process is listening on port 8081 like this:
>
> $ sudo lsof -P |grep 8081
> java 19729 nobody 132u IPv6 264719 0t0
> TCP *:8081 (LISTEN)
>
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Kevin Sweeney <ks...@twitter.com.INVALID>.
Hi Henry,
Were we able to help you get this working? I just tried out the tutorial on
master (467f842) after vagrant destroy -f and git clean -fdx and it worked
in my environment [1].
[1]
% dpkg -l virtualbox
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===================-==============-==============-============================================
ii virtualbox 4.3.10-dfsg-1 amd64 x86 virtualization
solution - base binaries
% vagrant -v
Vagrant 1.4.3
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
On Thu, Jun 5, 2014 at 10:17 AM, Jay Buffington <me...@jaybuff.com> wrote:
> On Thu, Jun 5, 2014 at 10:02 AM, Henry Saputra <he...@gmail.com>
> wrote:
>
> >
> > But seemed like no TCP bound to http://192.168.33.7:8081
> >
> >
> Is the aurora-scheduler process running? You can check like this:
>
> $ ps aux |grep [a]urora
> root 19711 0.0 0.0 4116 488 ? S 16:47 0:00 cronolog
> --link=/var/log/aurora/aurora-scheduler.log
> /var/log/aurora/aurora-scheduler.%Y%m%d.log
> root 19728 0.0 0.2 48532 1432 ? S 16:47 0:00 su -s
> /bin/bash -c /usr/local/bin/aurora-scheduler.sh nobody
> nobody 19729 2.4 60.9 2124104 306132 ? Ssl 16:47 0:40
> /opt/oracle-jdk-1.7.0_45/bin/java -server -Xmx1g -Xms1g
> -Djava.library.path=/usr/lib64 -classpath
>
> /usr/local/aurora-scheduler/lib/quark-aurora-package-0.5.1-SNAPSHOT.jar:/usr/local/aurora-scheduler/lib/aopalliance-1.0.jar:/usr/local/aurora-scheduler/lib/jsr305-2.0.1.jar:/usr/local/aurora-scheduler/lib/guava-16.0.jar:/usr/local/aurora-scheduler/lib/guice-3.0.jar:/usr/local/aurora-scheduler/lib/protobuf-java-2.5.0.jar:/usr/local/aurora-scheduler/lib/h2-1.4.177.jar:/usr/local/aurora-scheduler/lib/jersey-core-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-json-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-server-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-servlet-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-guice-1.17.1.jar:/usr/local/aurora-scheduler/lib/commons-lang-2.6.jar:/usr/local/aurora-scheduler/lib/javax.inject-1.jar:/usr/local/aurora-scheduler/lib/servlet-api-2.5.jar:/usr/local/aurora-scheduler/lib/log4j-1.2.17.jar:/usr/local/aurora-scheduler/lib/stringtemplate-3.2.1.jar:/usr/local/aurora-scheduler/lib/mesos-0.18.0.jar:/usr/local/aurora-scheduler/lib/libthrift-0.9.1.jar:/usr/local/aurora-scheduler/lib/zookeeper-3.3.4.jar:/usr/local/aurora-scheduler/lib/mybatis-3.2.7.jar:/usr/local/aurora-scheduler/lib/mybatis-guice-3.6.jar:/usr/local/aurora-scheduler/lib/quartz-2.2.1.jar:/usr/local/aurora-scheduler/lib/slf4j-jdk14-1.6.1.jar:/usr/local/aurora-scheduler/lib/log4j-0.0.7.jar:/usr/local/aurora-scheduler/lib/bootstrap-0.0.4.jar:/usr/local/aurora-scheduler/lib/jquery-0.0.4.jar:/usr/local/aurora-scheduler/lib/client-flagged-0.0.5.jar:/usr/local/aurora-scheduler/lib/client-0.0.5.jar:/usr/local/aurora-scheduler/lib/candidate-0.0.64.jar:/usr/local/aurora-scheduler/lib/client-0.0.56.jar:/usr/local/aurora-scheduler/lib/group-0.0.69.jar:/usr/local/aurora-scheduler/lib/server-set-1.0.74.jar:/usr/local/aurora-scheduler/lib/singleton-service-0.0.85.jar:/usr/local/aurora-scheduler/lib/application-http-0.0.59.jar:/usr/local/aurora-scheduler/lib/application-module-applauncher-0.0.51.jar:/usr/local/aurora-scheduler/lib/application-module-http-0.0.62.jar:/usr/local/aurora-scheduler/lib/application-module-lifecycle-0.0.48.jar:/usr/local/aurora-scheduler/lib/application-module-log-0.0.56.jar:/usr/local/aurora-scheduler/lib/application-module-stats-0.0.44.jar:/usr/local/aurora-scheduler/lib/application-0.0.73.jar:/usr/local/aurora-scheduler/lib/args-0.2.9.jar:/usr/local/aurora-scheduler/lib/base-0.0.87.jar:/usr/local/aurora-scheduler/lib/collections-0.0.74.jar:/usr/local/aurora-scheduler/lib/dynamic-host-set-0.0.44.jar:/usr/local/aurora-scheduler/lib/inject-timed-0.0.11.jar:/usr/local/aurora-scheduler/lib/inject-0.0.35.jar:/usr/local/aurora-scheduler/lib/io-0.0.53.jar:/usr/local/aurora-scheduler/lib/jdk-logging-0.0.44.jar:/usr/local/aurora-scheduler/lib/logging-0.0.61.jar:/usr/local/aurora-scheduler/lib/net-http-filters-0.0.6.jar:/usr/local/aurora-scheduler/lib/net-util-0.0.80.jar:/usr/local/aurora-scheduler/lib/quantity-0.0.71.jar:/usr/local/aurora-scheduler/lib/stats-0.0.91.jar:/usr/local/aurora-scheduler/lib/testing-easymock-0.0.4.jar:/usr/local/aurora-scheduler/lib/thrift-0.0.68.jar:/usr/local/aurora-scheduler/lib/util-executor-service-shutdown-0.0.49.jar:/usr/local/aurora-scheduler/lib/util-system-mocks-0.0.72.jar:/usr/local/aurora-scheduler/lib/util-templating-0.0.25.jar:/usr/local/aurora-scheduler/lib/util-testing-0.0.10.jar:/usr/local/aurora-scheduler/lib/util-0.0.94.jar:/usr/local/aurora-scheduler/lib/zookeeper-testing-0.0.45.jar:/usr/local/aurora-scheduler/lib/cglib-2.2.1-v20090111.jar:/usr/local/aurora-scheduler/lib/jettison-1.1.jar:/usr/local/aurora-scheduler/lib/jaxb-impl-2.2.3-1.jar:/usr/local/aurora-scheduler/lib/jackson-core-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-mapper-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-jaxrs-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-xc-1.9.2.jar:/usr/local/aurora-scheduler/lib/asm-3.1.jar:/usr/local/aurora-scheduler/lib/guice-servlet-3.0.jar:/usr/local/aurora-scheduler/lib/antlr-2.7.7.jar:/usr/local/aurora-scheduler/lib/commons-lang3-3.1.jar:/usr
>
>
>
> If it is you can check if that process is listening on port 8081 like this:
>
> $ sudo lsof -P |grep 8081
> java 19729 nobody 132u IPv6 264719 0t0
> TCP *:8081 (LISTEN)
>
--
Kevin Sweeney
@kts
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Henry Saputra <he...@gmail.com>.
This works but I just found out I cannot ping 192.168.33.7 from my local host:
$hsaputra > ping 192.168.33.7
PING 192.168.33.7 (192.168.33.7): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
^C
--- 192.168.33.7 ping statistics ---
6 packets transmitted, 0 packets received, 100.0% packet loss
Somehow my local machine cannot access the provisioned IP
- Henry
On Thu, Jun 5, 2014 at 10:17 AM, Jay Buffington <me...@jaybuff.com> wrote:
> On Thu, Jun 5, 2014 at 10:02 AM, Henry Saputra <he...@gmail.com>
> wrote:
>
>>
>> But seemed like no TCP bound to http://192.168.33.7:8081
>>
>>
> Is the aurora-scheduler process running? You can check like this:
>
> $ ps aux |grep [a]urora
> root 19711 0.0 0.0 4116 488 ? S 16:47 0:00 cronolog
> --link=/var/log/aurora/aurora-scheduler.log
> /var/log/aurora/aurora-scheduler.%Y%m%d.log
> root 19728 0.0 0.2 48532 1432 ? S 16:47 0:00 su -s
> /bin/bash -c /usr/local/bin/aurora-scheduler.sh nobody
> nobody 19729 2.4 60.9 2124104 306132 ? Ssl 16:47 0:40
> /opt/oracle-jdk-1.7.0_45/bin/java -server -Xmx1g -Xms1g
> -Djava.library.path=/usr/lib64 -classpath
> /usr/local/aurora-scheduler/lib/quark-aurora-package-0.5.1-SNAPSHOT.jar:/usr/local/aurora-scheduler/lib/aopalliance-1.0.jar:/usr/local/aurora-scheduler/lib/jsr305-2.0.1.jar:/usr/local/aurora-scheduler/lib/guava-16.0.jar:/usr/local/aurora-scheduler/lib/guice-3.0.jar:/usr/local/aurora-scheduler/lib/protobuf-java-2.5.0.jar:/usr/local/aurora-scheduler/lib/h2-1.4.177.jar:/usr/local/aurora-scheduler/lib/jersey-core-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-json-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-server-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-servlet-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-guice-1.17.1.jar:/usr/local/aurora-scheduler/lib/commons-lang-2.6.jar:/usr/local/aurora-scheduler/lib/javax.inject-1.jar:/usr/local/aurora-scheduler/lib/servlet-api-2.5.jar:/usr/local/aurora-scheduler/lib/log4j-1.2.17.jar:/usr/local/aurora-scheduler/lib/stringtemplate-3.2.1.jar:/usr/local/aurora-scheduler/lib/mesos-0.18.0.jar:/usr/local/aurora-scheduler/lib/libthrift-0.9.1.jar:/usr/local/aurora-scheduler/lib/zookeeper-3.3.4.jar:/usr/local/aurora-scheduler/lib/mybatis-3.2.7.jar:/usr/local/aurora-scheduler/lib/mybatis-guice-3.6.jar:/usr/local/aurora-scheduler/lib/quartz-2.2.1.jar:/usr/local/aurora-scheduler/lib/slf4j-jdk14-1.6.1.jar:/usr/local/aurora-scheduler/lib/log4j-0.0.7.jar:/usr/local/aurora-scheduler/lib/bootstrap-0.0.4.jar:/usr/local/aurora-scheduler/lib/jquery-0.0.4.jar:/usr/local/aurora-scheduler/lib/client-flagged-0.0.5.jar:/usr/local/aurora-scheduler/lib/client-0.0.5.jar:/usr/local/aurora-scheduler/lib/candidate-0.0.64.jar:/usr/local/aurora-scheduler/lib/client-0.0.56.jar:/usr/local/aurora-scheduler/lib/group-0.0.69.jar:/usr/local/aurora-scheduler/lib/server-set-1.0.74.jar:/usr/local/aurora-scheduler/lib/singleton-service-0.0.85.jar:/usr/local/aurora-scheduler/lib/application-http-0.0.59.jar:/usr/local/aurora-scheduler/lib/application-module-applauncher-0.0.51.jar:/usr/local/aurora-scheduler/lib/application-module-http-0.0.62.jar:/usr/local/aurora-scheduler/lib/application-module-lifecycle-0.0.48.jar:/usr/local/aurora-scheduler/lib/application-module-log-0.0.56.jar:/usr/local/aurora-scheduler/lib/application-module-stats-0.0.44.jar:/usr/local/aurora-scheduler/lib/application-0.0.73.jar:/usr/local/aurora-scheduler/lib/args-0.2.9.jar:/usr/local/aurora-scheduler/lib/base-0.0.87.jar:/usr/local/aurora-scheduler/lib/collections-0.0.74.jar:/usr/local/aurora-scheduler/lib/dynamic-host-set-0.0.44.jar:/usr/local/aurora-scheduler/lib/inject-timed-0.0.11.jar:/usr/local/aurora-scheduler/lib/inject-0.0.35.jar:/usr/local/aurora-scheduler/lib/io-0.0.53.jar:/usr/local/aurora-scheduler/lib/jdk-logging-0.0.44.jar:/usr/local/aurora-scheduler/lib/logging-0.0.61.jar:/usr/local/aurora-scheduler/lib/net-http-filters-0.0.6.jar:/usr/local/aurora-scheduler/lib/net-util-0.0.80.jar:/usr/local/aurora-scheduler/lib/quantity-0.0.71.jar:/usr/local/aurora-scheduler/lib/stats-0.0.91.jar:/usr/local/aurora-scheduler/lib/testing-easymock-0.0.4.jar:/usr/local/aurora-scheduler/lib/thrift-0.0.68.jar:/usr/local/aurora-scheduler/lib/util-executor-service-shutdown-0.0.49.jar:/usr/local/aurora-scheduler/lib/util-system-mocks-0.0.72.jar:/usr/local/aurora-scheduler/lib/util-templating-0.0.25.jar:/usr/local/aurora-scheduler/lib/util-testing-0.0.10.jar:/usr/local/aurora-scheduler/lib/util-0.0.94.jar:/usr/local/aurora-scheduler/lib/zookeeper-testing-0.0.45.jar:/usr/local/aurora-scheduler/lib/cglib-2.2.1-v20090111.jar:/usr/local/aurora-scheduler/lib/jettison-1.1.jar:/usr/local/aurora-scheduler/lib/jaxb-impl-2.2.3-1.jar:/usr/local/aurora-scheduler/lib/jackson-core-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-mapper-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-jaxrs-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-xc-1.9.2.jar:/usr/local/aurora-scheduler/lib/asm-3.1.jar:/usr/local/aurora-scheduler/lib/guice-servlet-3.0.jar:/usr/local/aurora-scheduler/lib/antlr-2.7.7.jar:/usr/local/aurora-scheduler/lib/commons-lang3-3.1.jar:/usr
>
>
>
> If it is you can check if that process is listening on port 8081 like this:
>
> $ sudo lsof -P |grep 8081
> java 19729 nobody 132u IPv6 264719 0t0
> TCP *:8081 (LISTEN)
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Jay Buffington <me...@jaybuff.com>.
On Thu, Jun 5, 2014 at 10:02 AM, Henry Saputra <he...@gmail.com>
wrote:
>
> But seemed like no TCP bound to http://192.168.33.7:8081
>
>
Is the aurora-scheduler process running? You can check like this:
$ ps aux |grep [a]urora
root 19711 0.0 0.0 4116 488 ? S 16:47 0:00 cronolog
--link=/var/log/aurora/aurora-scheduler.log
/var/log/aurora/aurora-scheduler.%Y%m%d.log
root 19728 0.0 0.2 48532 1432 ? S 16:47 0:00 su -s
/bin/bash -c /usr/local/bin/aurora-scheduler.sh nobody
nobody 19729 2.4 60.9 2124104 306132 ? Ssl 16:47 0:40
/opt/oracle-jdk-1.7.0_45/bin/java -server -Xmx1g -Xms1g
-Djava.library.path=/usr/lib64 -classpath
/usr/local/aurora-scheduler/lib/quark-aurora-package-0.5.1-SNAPSHOT.jar:/usr/local/aurora-scheduler/lib/aopalliance-1.0.jar:/usr/local/aurora-scheduler/lib/jsr305-2.0.1.jar:/usr/local/aurora-scheduler/lib/guava-16.0.jar:/usr/local/aurora-scheduler/lib/guice-3.0.jar:/usr/local/aurora-scheduler/lib/protobuf-java-2.5.0.jar:/usr/local/aurora-scheduler/lib/h2-1.4.177.jar:/usr/local/aurora-scheduler/lib/jersey-core-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-json-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-server-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-servlet-1.17.1.jar:/usr/local/aurora-scheduler/lib/jersey-guice-1.17.1.jar:/usr/local/aurora-scheduler/lib/commons-lang-2.6.jar:/usr/local/aurora-scheduler/lib/javax.inject-1.jar:/usr/local/aurora-scheduler/lib/servlet-api-2.5.jar:/usr/local/aurora-scheduler/lib/log4j-1.2.17.jar:/usr/local/aurora-scheduler/lib/stringtemplate-3.2.1.jar:/usr/local/aurora-scheduler/lib/mesos-0.18.0.jar:/usr/local/aurora-scheduler/lib/libthrift-0.9.1.jar:/usr/local/aurora-scheduler/lib/zookeeper-3.3.4.jar:/usr/local/aurora-scheduler/lib/mybatis-3.2.7.jar:/usr/local/aurora-scheduler/lib/mybatis-guice-3.6.jar:/usr/local/aurora-scheduler/lib/quartz-2.2.1.jar:/usr/local/aurora-scheduler/lib/slf4j-jdk14-1.6.1.jar:/usr/local/aurora-scheduler/lib/log4j-0.0.7.jar:/usr/local/aurora-scheduler/lib/bootstrap-0.0.4.jar:/usr/local/aurora-scheduler/lib/jquery-0.0.4.jar:/usr/local/aurora-scheduler/lib/client-flagged-0.0.5.jar:/usr/local/aurora-scheduler/lib/client-0.0.5.jar:/usr/local/aurora-scheduler/lib/candidate-0.0.64.jar:/usr/local/aurora-scheduler/lib/client-0.0.56.jar:/usr/local/aurora-scheduler/lib/group-0.0.69.jar:/usr/local/aurora-scheduler/lib/server-set-1.0.74.jar:/usr/local/aurora-scheduler/lib/singleton-service-0.0.85.jar:/usr/local/aurora-scheduler/lib/application-http-0.0.59.jar:/usr/local/aurora-scheduler/lib/application-module-applauncher-0.0.51.jar:/usr/local/aurora-scheduler/lib/application-module-http-0.0.62.jar:/usr/local/aurora-scheduler/lib/application-module-lifecycle-0.0.48.jar:/usr/local/aurora-scheduler/lib/application-module-log-0.0.56.jar:/usr/local/aurora-scheduler/lib/application-module-stats-0.0.44.jar:/usr/local/aurora-scheduler/lib/application-0.0.73.jar:/usr/local/aurora-scheduler/lib/args-0.2.9.jar:/usr/local/aurora-scheduler/lib/base-0.0.87.jar:/usr/local/aurora-scheduler/lib/collections-0.0.74.jar:/usr/local/aurora-scheduler/lib/dynamic-host-set-0.0.44.jar:/usr/local/aurora-scheduler/lib/inject-timed-0.0.11.jar:/usr/local/aurora-scheduler/lib/inject-0.0.35.jar:/usr/local/aurora-scheduler/lib/io-0.0.53.jar:/usr/local/aurora-scheduler/lib/jdk-logging-0.0.44.jar:/usr/local/aurora-scheduler/lib/logging-0.0.61.jar:/usr/local/aurora-scheduler/lib/net-http-filters-0.0.6.jar:/usr/local/aurora-scheduler/lib/net-util-0.0.80.jar:/usr/local/aurora-scheduler/lib/quantity-0.0.71.jar:/usr/local/aurora-scheduler/lib/stats-0.0.91.jar:/usr/local/aurora-scheduler/lib/testing-easymock-0.0.4.jar:/usr/local/aurora-scheduler/lib/thrift-0.0.68.jar:/usr/local/aurora-scheduler/lib/util-executor-service-shutdown-0.0.49.jar:/usr/local/aurora-scheduler/lib/util-system-mocks-0.0.72.jar:/usr/local/aurora-scheduler/lib/util-templating-0.0.25.jar:/usr/local/aurora-scheduler/lib/util-testing-0.0.10.jar:/usr/local/aurora-scheduler/lib/util-0.0.94.jar:/usr/local/aurora-scheduler/lib/zookeeper-testing-0.0.45.jar:/usr/local/aurora-scheduler/lib/cglib-2.2.1-v20090111.jar:/usr/local/aurora-scheduler/lib/jettison-1.1.jar:/usr/local/aurora-scheduler/lib/jaxb-impl-2.2.3-1.jar:/usr/local/aurora-scheduler/lib/jackson-core-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-mapper-asl-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-jaxrs-1.9.2.jar:/usr/local/aurora-scheduler/lib/jackson-xc-1.9.2.jar:/usr/local/aurora-scheduler/lib/asm-3.1.jar:/usr/local/aurora-scheduler/lib/guice-servlet-3.0.jar:/usr/local/aurora-scheduler/lib/antlr-2.7.7.jar:/usr/local/aurora-scheduler/lib/commons-lang3-3.1.jar:/usr
If it is you can check if that process is listening on port 8081 like this:
$ sudo lsof -P |grep 8081
java 19729 nobody 132u IPv6 264719 0t0
TCP *:8081 (LISTEN)
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Henry Saputra <he...@gmail.com>.
Seemed like I can ping the IP:
vagrant@192:~$ ping 192.168.33.7
PING 192.168.33.7 (192.168.33.7) 56(84) bytes of data.
64 bytes from 192.168.33.7: icmp_req=1 ttl=64 time=0.021 ms
64 bytes from 192.168.33.7: icmp_req=2 ttl=64 time=0.025 ms
64 bytes from 192.168.33.7: icmp_req=3 ttl=64 time=0.033 ms
64 bytes from 192.168.33.7: icmp_req=4 ttl=64 time=0.050 ms
^C
--- 192.168.33.7 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 0.021/0.032/0.050/0.011 ms
vagrant@192:~$
But seemed like no TCP bound to http://192.168.33.7:8081
- Henry
On Thu, Jun 5, 2014 at 7:02 AM, Bill Farner <wf...@apache.org> wrote:
> I'm curious what served the 404, are you able to repro and capture the
> response message?
>
> On Monday, June 2, 2014, Henry Saputra <he...@gmail.com> wrote:
>
>> Hi Guys,
>>
>> I did git pull last week and when I try to run and schedule job to my
>> Vagrant's setup of Aurora :
>>
>> vagrant@192:~$ aurora create devcluster/www-data/devel/hello_world
>> /vagrant/hello_world.aurora
>>
>> INFO] Creating job hello_world
>>
>> INFO] Response from scheduler: OK (message: None)
>>
>> INFO] Job url:
>> http://192.168.33.7:8081/scheduler/www-data/devel/hello_world
>>
>> However when I tried to connect to
>> http://192.168.33.7:8081/scheduler/www-data/devel/hello_world via
>> browser it finally gave me 404.
>>
>> I do not see access logged to aurora-scheduler.log file.
>>
>> Anyone else seen this behavior or just me?
>>
>> I have been doing vagrant destroy and rebuild the stuff with no luck =(
>>
>> - Henry
>>
>
>
> --
> -=Bill
Re: No longer be able to access Aurora scheduler UI in the Vargrant
vanilla after pull from master =(
Posted by Bill Farner <wf...@apache.org>.
I'm curious what served the 404, are you able to repro and capture the
response message?
On Monday, June 2, 2014, Henry Saputra <he...@gmail.com> wrote:
> Hi Guys,
>
> I did git pull last week and when I try to run and schedule job to my
> Vagrant's setup of Aurora :
>
> vagrant@192:~$ aurora create devcluster/www-data/devel/hello_world
> /vagrant/hello_world.aurora
>
> INFO] Creating job hello_world
>
> INFO] Response from scheduler: OK (message: None)
>
> INFO] Job url:
> http://192.168.33.7:8081/scheduler/www-data/devel/hello_world
>
> However when I tried to connect to
> http://192.168.33.7:8081/scheduler/www-data/devel/hello_world via
> browser it finally gave me 404.
>
> I do not see access logged to aurora-scheduler.log file.
>
> Anyone else seen this behavior or just me?
>
> I have been doing vagrant destroy and rebuild the stuff with no luck =(
>
> - Henry
>
--
-=Bill