Instead try:

sv up crond

And see if that gives you any information.

You might try running crond with different command line arguments. There doesn't seem to be a cron group by default and this might also be an issue.