From mboxrd@z Thu Jan  1 00:00:00 1970
X-Received: by 10.182.221.196 with SMTP id qg4mr5659398obc.43.1426460506876;
        Sun, 15 Mar 2015 16:01:46 -0700 (PDT)
X-BeenThere: voidlinux@googlegroups.com
Received: by 10.140.104.241 with SMTP id a104ls2660043qgf.11.gmail; Sun, 15
 Mar 2015 16:01:46 -0700 (PDT)
X-Received: by 10.140.94.170 with SMTP id g39mr901766qge.34.1426460506758;
        Sun, 15 Mar 2015 16:01:46 -0700 (PDT)
Date: Sun, 15 Mar 2015 16:01:46 -0700 (PDT)
From: JD Robinson <jdrobi...@gmail.com>
To: voidlinux@googlegroups.com
Message-Id: <5f18d075-5fd9-4914-852c-3455b1ee23ec@googlegroups.com>
In-Reply-To: <7361c5d5-2574-4c5b-9215-d81c6e8360f6@googlegroups.com>
References: <7361c5d5-2574-4c5b-9215-d81c6e8360f6@googlegroups.com>
Subject: run dcron down
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_610_71948586.1426460506306"

------=_Part_610_71948586.1426460506306
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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. 
------=_Part_610_71948586.1426460506306--