I once had the same problem. In my case it was the coloured output of grep that injected ansi codes into the CS startup command.
Am 19.03.2017 18:07 schrieb "Long Quanzheng" <prc...@gmail.com>: > Hi > It still doesn't work. > > The real problem is this error: > > Error: Could not find or load main class -ea > > Thanks > Long > > On Sun, Mar 19, 2017 at 3:16 AM Vinci <vi...@protonmail.com> wrote: > >> You need to have a log directory to be able to run cassandra. >> >> mkdir logs >> >> then start the cassandra process. >> >> -------- Original Message -------- >> Subject: Running cassandra >> Local Time: 19 March 2017 11:31 AM >> UTC Time: 19 March 2017 06:01 >> From: prc...@gmail.com >> To: user@cassandra.apache.org <user@cassandra.apache.org> >> >> >> Hi >> I am trying to get started to play with Cassandra follow this doc: >> http://cassandra.apache.org/doc/latest/getting_started/ >> installing.html#prerequisites >> >> But I always get the error: >> >> qlong@~/ws/cas/apache-cassandra-3.10 $ ./bin/cassandra -f >> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file >> ./bin/../logs/gc.log due to No such file or directory >> >> Error: Could not find or load main class -ea >> qlong@~/ws/cas/apache-cassandra-3.10 $ ./bin/cassandra >> Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file >> ./bin/../logs/gc.log due to No such file or directory >> >> qlong@~/ws/cas/apache-cassandra-3.10 $ Error: Could not find or load >> main class -ea >> >> Did I miss something? >> >> My java is 1.8: >> qlong@~ $ java -version >> java version "1.8.0_121" >> Java(TM) SE Runtime Environment (build 1.8.0_121-b13) >> Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) >> >> Thanks for any help, >> Long >> >> >>
