FreeNAS 11.1 cron job not running

Status
Not open for further replies.

blackwing01

Cadet
Joined
Jan 16, 2018
Messages
2
I am new in the FreeNAS and I am running 11.1 version.

From the gui, I entered several cron jobs and one of those is just a simple scp command.
Code:
scp -P 22567 -p -r 192.168.100.55:/path/path/path/backup /mnt/billiards/backup-path/

which run every day at 8am

also a rsync command
Code:
rsync --update -az -e "ssh -p 22650" root@192.168.100.55:/ /mnt/billiards/backup-path2/

which run every day at 12nn

neither of this two runs and update my file in my backup folder.

I also did try to put it on my crontab
Code:
00	  08	  *	   *	  2	   root   rsync --update -az -e "ssh -p 22650" root@192.168.100.55:/ /mnt/billiards/backup-path2/

but still, it didn't run

But if I try to run it on my backup server terminal this command all runs smoothly.

On my /var/log/cron it has this

Code:
Jan 16 08:00:00 nasty /usr/sbin/cron[48026]: (billiards) CMD (PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/root/bin" scp -P 22567 -p -r 192.168.100.55:/path/path/path/backup /mnt/billiards/backup-path/> /dev/null)

But the file on the local FreeNAS didn't get updated, even there is a new file on the remote server.

Can anyone please help me, why my cron job doesn't run.

This is a fresh install system.
 
Last edited by a moderator:

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
FreeNAS is an appliance. It keeps many settings in a database, so changes to the traditional configuration files don't work.

The traditional cure to problems with cron jobs is to give a full path for the commands:
Code:
/usr/local/bin/rsync --update ...
 
Status
Not open for further replies.
Top