Unresponsive GUI and console after cron job

[memel.parduin]

Hi,

I don't know if this is the right place to put this, and I don't even know if the title is descriptive enough..

I have a FreeNAS 7 server, trying to zfs send over ssh via a cron job to a FreeNAS 8 server. The command I'm using

Code:

zfs send -i snapshot@datetime-now snapshot@datetime-then | ssh remote_server zfs receive -dvF pool/dataset

Letting this run results in an unresponsive FreeNAS 8 server, both GUI, SSH and console.
However, when I choose 'run now' in the FreeNAS 7 cron menu, everything works fine. What could I be doing wrong? Has anyone encountered a similar problem? Any hints?

Thanks,
Memel

PS: I'll also post this in the FreeNAS 7 forum, just for sure.

 

[memel.parduin]

crond not running?

Ok, an update.

I've rescheduled my replication jobs to another hour, which seems to work. But instead of the daily run and a security run report my FreeNAS 8 server now sends me a daily mail complaining about

Code:

newsyslog: pid file doesn't exist: /var/run/syslog.pid

which it has every right to, because there really is no syslog.pid file in /var/run, only an empty syslogd.sockets file.

However, syslogd seems to be running

Code:

[root@daniel] ~# ps ax | grep syslogd
 1070  ??  Ss     0:00.02 /usr/sbin/syslogd -s -C

When I try to restart I get

Code:

[root@daniel] ~# /etc/rc.d/syslogd restart
syslogd not running? (check /var/run/syslog.pid).
Starting syslogd.
syslogd: child pid 6871 exited with return code 1
/etc/rc.d/syslogd: WARNING: failed to start syslogd

What does this all mean? How can I put this right?

Memel