I think you should take a look at supervisord or sth similar. This is a much more reliable solution than using crons.
Am 12.01.2017 06:12 schrieb "Ajay Garg" <ajaygargn...@gmail.com>: On Wed, Jan 11, 2017 at 8:29 PM, Martin Schröder <mar...@oneiros.de> wrote: > 2017-01-11 15:42 GMT+01:00 Ajay Garg <ajaygargn...@gmail.com>: > > Tried everything. > > Then try > service cassandra start > or > systemctl start cassandra > > You still haven't explained to us why you want to start cassandra every > minute. > Hi Martin. Sometimes, the cassandra-process gets killed (reason unknown as of now). Doing a manual "service cassandra start" works then. Adding this in cron would at least ensure that the maximum downtime is 59 seconds (till the time root-cause of cassandra-crashing is known). > > Best > Martin > -- Regards, Ajay