Stack trace on login #12

mbulman opened this Issue Feb 27, 2013 · 1 comment


None yet
2 participants

mbulman commented Feb 27, 2013

After provisioning via opscenter (raidonly=true)

[automaton@ip-10-196-24-69 ~]$ ssh -i US_West_\(Northern_California\)-OpsCenterProvisioningKeyPair.pem ubuntu@
Last login: Wed Feb 27 01:10:10 2013 from

Cluster started with these options:

Waiting for nodetool...
The cluster is now in it's finalization phase. This should only take a moment...

Note: You can also use CTRL+C to view the logs if desired:
    AMI log: ~/datastax_ami/ami.log
    Cassandra log: /var/log/cassandra/system.log

Traceback (most recent call last):
  File "datastax_ami/", line 196, in <module>
  File "datastax_ami/", line 187, in run
  File "datastax_ami/", line 84, in waiting_for_nodetool
    retcode =['nodetool_statement']), stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/usr/lib/python2.7/", line 493, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.7/", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

joaquincasares commented Mar 4, 2013

All --raidonly, a hidden option, launches should now contain no more errors.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment