Applicable to:
- SolusVM
Symptoms
SolusVM installation fails with the following error:
CONFIG_TEXT: Failed to start Command Scheduler.
: failed to execute 'systemctl start crond': failed "systemctl start crond" with stdErr: "Warning: The unit file, source configuration file or drop-ins of crond.service changed on disk. Run 'systemctl daemon-reload' to reload units.\nJob for crond.service failed.\nSee \"systemctl status crond.service\" and \"journalctl -xe\" for details.\n", stdOut: "", exitStatus: exit status 1
Cause
crond service failed to start during SolusVM installation
Resolution
- Connect to the server via SSH
- Start crond service:
# systemctl start crond
Comments
0 commentsPlease sign in to leave a comment.