When starting cassandra, it starts in the background, if it crashes or fails in some way, it may write the information on your screen, and it may not. If you setup the logs properly, it will be in the logs. However, until you get all those things right, you may have trouble starting Cassandra.
First of all, you can use the -f flag to start cassandra in the foreground, like this:
That way you should get the error information on your screen. From there you should understand what's wrong.
In my case, I had a first problem which was a crash. This was due to a stack ...