Anyone encountered this before? Directory space is enough, permission is not an issue (runs the installer with node), yet the nodekeeper failed to start.
Also, notice that (in the first screenshot) before the nodekeeper start, the firewall service is able to be started, this is another I would tuled out the permission issue.
My last suspect (the installer is corrupted) has also been ruled out as few times of re-download-then-re-install has also been tried.
What could've gone wrong here? Appreciate any kind feedback, even if it is just direction to start investigation instead of straight answer.
Solved! Go to Solution.
Please open a support ticket. We will help you troubleshoot that issue.
Check nodekeeper log in your data dir \log\nodekeeper to get some more details.
For Cassandra I guess it was not started. Is that counted to NFS ? Try starting all services again maybe now Cassandra was able to be properly initialized.