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 <wfar...@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 <henry.sapu...@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
