Tarsier

Bizarrely enough, it seems to be working fine now. No adblockers installed...

I played around with the Scheduler settings page I seem to have gotten it working now # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null I would guess that it's related to the way the Scheduler settings page refreshes when you select Scheduled parity check setting i.e. when you select Monthly, the page refreshes to give the monthly settings, but you need to actually change the settings, for them to be updated. Selecting Apply immediately after selecting Monthly, doesn't change the cron settings correctly. Hope that makes sense?

I get the output below # Custom cron scripts: # Runs Docs Backups on Tue and Fri 2am 0 2 0 * 2 logger Started DocsBackupTue && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsTue/ 2>&1 1>/dev/null 0 2 0 * 5 logger Started DocsBackupFri && rsync -av /mnt/disk1/ /mnt/disks/WDMyBook/DocsFri/ 2>&1 1>/dev/null# Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 0 * * 0 /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null

The settings stick on the Scheduler settings page, yes However, when i run cat /var/spool/cron/crontabs/root the parity check does not appear # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null

I upgraded from 5.05 to 6.2 and also noticed that my monthly parity check didn't run on the 1st of the month. I tried to upgrade using the automated plugin but it wouldn't boot after so I copied the syslinux folder over from the latest zip and ran make_bootable.bat I've tried disabling and re-enabling both notifications and the monthly parity check in Scheduler but the cron job doesn't appear. I noticed that when I disable the scheduled monthly parity check and re-enable the following message appears briefly at the bottom of the Scheduler page Warning: unlink(/tmp/memory.tmp): No such file or redirectory in /usr/local/emhttp/plugins/dynamix/include/update.parity.php on line 55 EDIT: Thought that a scheduled cron job for backup to external hdd not working may have been related, but it is now working

I'm also looking for a smarthistory successor for Unraid v6 On Unraid v5 smarthistory showed some of the SMART values for my parity drive had been slowly deteriorating over the past few months. I've since upgraded to Unraid v6 and can't find the graphs anymore to send to the drive manufacturer.

Hi there I'm not running a cache drive but have a non-array drive. Can I install pyload to that?

Thanks prostuff1 It's installed on a different array drive currently. I'm going to change my array and install it to a SNAP drive outside my array to allow my parity drive to spin down. Installing transmission to a SNAP drive would work right?

Hi there If I set the watch directory to a folder on an array drive, do you know if it will prevent that drive from spinning down? I'm trying to set the watch dir to my dropbox folder on an array drive so I can start torrents remotely. The dropbox plugin, according to the relevant thread, won't prevent spindown unless files are added/changed. I've searched around regarding transmission watchdir feature and drive spindowns but I can't find a definitive answer.

Thanks for looking into this prostuff1. I would be hoping for a Transmission version of at least 2.33. The reason being, many of my trackers don't allow older versions to be used and currently there are no other bittorrent clients supported for Unraid Thanks EDIT: Untorrent was mysteriously withdrawn a few months ago citing incompatibilities. Could it be due to the same issue?

Interesting but unfortunately it's not allowed on a few of my private trackers. It seems it doesn't identify its version correctly.

I couldn't get it to work prostuff1 suggested he might look at it but I understand it's towards the end of his to-do list and he might never get to it.

I just restarted and transmission starts up. Package Manager shows Currently Installed. Will NOT be automatically Re-Installed upon Re-Boot. EDIT: tried enabling and disabling Re-install on re-boot and then restarting Same outcome EDIT2: OK fixed. Manually deleted an autoinstall file in packages.. I think it was left over from a previous version of the package. Perhaps that was what was causing the multiple instances being run?

Hey prostuff1 Not sure if this is a bug as I'm still pretty new to unraid but transmission seems to remain installed when I restart even when I don't select Enable Re-Install on Re-Boot. Thanks for all your hard work.

I haven't had any crashes since but here is the output from those commands tower login: root Password: Linux 2.6.32.9-unRAID. root@tower:~# ls -al /var/run/ total 64 drwxr-xr-x 4 root root 0 2011-09-30 00:59 ./ drwxr-xr-x 14 root root 0 2011-09-30 01:00 ../ srw-rw-rw- 1 root root 0 2011-09-30 00:58 acpid.socket= -rw-r--r-- 1 root root 5 2011-09-30 00:58 atd.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 ifplugd.eth0.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 inetd.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 klogd.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 nmbd.pid drwxr-xr-x 2 root root 0 2011-03-24 19:19 nscd/ -rw-r--r-- 1 root root 4 2011-09-30 00:58 ntpd.pid -rw------- 1 root root 74 2011-09-30 00:58 portmap_mapping -rw-r--r-- 1 nobody root 5 2011-09-30 00:58 rpc.statd.pid -rw------- 1 root root 5 2011-09-30 00:58 sm-notify.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 smbd.pid -rw-r--r-- 1 root root 5 2011-09-30 00:59 snapNotify.pid -rw-r--r-- 1 root root 5 2011-09-30 00:59 snapSambaNotify.pid -rw-r--r-- 1 root root 5 2011-09-30 00:58 syslogd.pid drwxr-xr-x 2 root root 0 2011-10-01 01:27 transmission/ -rw-r--r-- 1 root root 6 2011-09-30 19:02 unmenu.pid -rw-rw-r-- 1 root utmp 4608 2011-10-01 01:30 utmp root@tower:~# ls -al /mnt/disk5/.transmission total 0 drwxr-xr-x 3 root root 72 2011-09-28 04:29 ./ drwx--x--x 6 root root 136 2011-09-28 04:30 ../ drwxr-xr-x 5 root root 232 2011-10-01 01:27 conf/ root@tower:~# ps -ef | grep trans root 1625 1122 0 01:31 pts/0 00:00:00 grep trans root 31488 1 0 01:27 ? 00:00:00 /usr/bin/transmission-daemon -g /mnt/disk5/.transmission/conf --pid-file /var/run/transmission/transmission-daemon.pid root@tower:~# The output for the last command was too long and got cut off so I. copy pasted the file contents. I'll PM it to you prostuff1 for security reasons EDIT: Just noting I have no issues with shutting down transmission