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.
On Tue, Jul 8, 2014 at 1:15 PM, Mark Grover <[EMAIL PROTECTED]> wrote:
FWIW, I still can't ssh or ping ec2-54-221-150-123.compute-1.amazonaws.com, all the other instances are just fine. ping ec2-54-221-150-123.compute-1.amazonaws.com PING ec2-54-221-150-123.compute-1.amazonaws.com (220.127.116.11): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2
But, even barring that, all the few CentOS6 builds I checked were failing with the same error:
On Tue, Jul 8, 2014 at 4:59 PM, Mark Grover <[EMAIL PROTECTED]> wrote:
Ping never worked, but ssh works just fine for me. You key [EMAIL PROTECTED]l seems to be in place. Not quite sure what else could be happening. /tmp got clogged again. I think we just need to add rm -rf /var/tmp/* /tmp/* to our top level nitghly job.
Not sure if it was the reboot or Cos' magical hands but life is much better now:-) On Tue, Jul 8, 2014 at 9:30 PM, Roman Shaposhnik <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext