Linux Run Levels - Task failed because server did not boot up upon reboot


This is an unpleasant experience.

I had set the run levels using systemctl and when I used systemctl get-default to check, it indeed is set to graphical target.

To confirm if after reboot the setting persist, I rebooted the first app server. After reboot, the server did not came up as ping did not reply.(I waited for about 5 mins) I think KodeCloud should fix this issue.

While I thought that I had completed this task successfully, if there is a limitation that server should not be rebooted it should be stated as well.


Hi @dkelim1

Sorry for this issue, we have updated the task description and reassigned the scenario to you. Please try again.