I can login just fine to the slave and it seems to be operational now (the fedora one seems to be borked, though :-().
Having access to AWS web interface is a sore point -- none of us have it. All we've got is ACCESS KEY and SECRET KEY. Anything that works with that -- works, but that doesn't include AWS web interface. Folks at Cloudera (Andrew, Aida) probably know more. Thanks, Roman. On Tue, Jul 8, 2014 at 1:15 PM, Mark Grover <[email protected]> wrote: > Hey Julien, > I tried SSH'ing (as root and ec2-user) and pinging to the box ( > ec2-54-221-150-123.compute-1.amazonaws.com) but both seemed to fail. > > Something is listening on port 22 there since telnet passed. > > I don't have access to the webconsole to be able to do anything fancier but > I am open to suggestions? Can anyone with more privs help out here or > assign some AWS web interface creds to me? > > Thanks! > Mark > > > On Tue, Jul 8, 2014 at 1:04 PM, Julien Eid <[email protected]> wrote: > >> >> http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Hadoop/label=centos6/667/console >> >> >> The JRE keeps crashing for builds and if you go to >> http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Hadoop/label=centos6/ws/ >> the Jenkins slave is having lots of trouble. >> >> Can we see if a Jenkins slave restart fixes these issues and then kick off >> a build? >>
