I have a script being run but I don't know where they are configured in. I want to turn the cron job off.

 

I am getting error because every 4 hours on the hour (12pm, 4pm, etc.), the script runs and I get an error notification.

 

Email contents is something like this:

Subject: cron for user root logger -tscriptSubliminal[$$] "Subliminal check" && /mnt/user/sub2/runscript.sh > /dev/null

Content: /bin/sh: /mnt/user/sub2/runscript.sh: No such file or directory.

 

Hopefully can get advice on where to find them.

 

I did have user.scripts but they are all set to Disabled so I don't think that is the place/cause. 

 

If I run crontab -e I get this:

# 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
0 5 * * 2 /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php &>/dev/null 2>&1

which does not seems to contain any of my script that is running (or runs every 4 hours, on the hour).

Is there any place else where we can configure cron scripts?

/etc/cron.d/root 

But usually you would manage cron jobs either via user scripts or by putting an applicable .cron file on the flash drive

Thanks! I saw it appear in cron now. Is that generated by some other scripts that placed it in there?

 

Will editing it survive a restart?

3 hours ago, CyberMew said:

Thanks! I saw it appear in cron now. Is that generated by some other scripts that placed it in there?

Giving us the entry that is showing up might help give a clue where it is coming from.   Likely being generated by a plugin if it is not User Scripts.

 

3 hours ago, CyberMew said:

Will editing it survive a restart?

No as that only changes the RAM copy.  You need to identify the culprit or a restart will simply re-instate the entry.

Ah I see.. 

 

The entries are as follows:

~# cat /etc/cron.d/root
# Generated docker monitoring schedule:
10 0 * * 1 /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null

# Generated system monitoring schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

# Generated mover schedule:
40 4 * * * /usr/local/sbin/mover &> /dev/null

# Generated parity check schedule:
0 0 1 * * /usr/local/sbin/mdcmd check  &> /dev/null

# Generated plugins version check schedule:
10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null

#Refresh plex at 3pm everyday 0 15
36 20 * * * logger -tscriptRefreshPlexLibrary[$$] "Refreshing Plex library" && curl "http://127.0.0.1:32400/library/sections[redacted]" &> /dev/null

# Generated array status check schedule:
20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

#Running subliminal At minute 0 past every 4th hour. cat /etc/cron.d/root
0 */4 * * * logger -tscriptSubliminal[$$] "Subliminal check" && /mnt/user/sub2/runscript.sh > /dev/null

# Generated cron settings for docker autoupdates
0 0 * * 0 /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1
# Generated cron settings for plugin autoupdates
0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1

# CRON for CA background scanning of applications
39 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1

# Generated ssd trim schedule:
0 3 * * * /sbin/fstrim -a -v | logger &> /dev/null

 

Still no idea what I modified/added to add those 2 plex/subliminal entries when I restart.. any idea what is -tscript from?

It is definitely something you have installed    It seems to be installed in the ‘sub2’ User Share if that helps you identify it.

 

if you provide your system’s diagnostics we could see if something obvious springs out.