Two scripts, one runs, the other does not?

[ytddewqf]

Hello all, 

 

I was hoping that someone might be able to point me in the right direction regarding scripts. 

 

I have only two that are active, one to backup Bitwarden and one that utilises rclone to backup four folders. Both are set to run at 2am daily, however the Bitwarden script runs fine but the rclone one does not run at all? It works if I manually select "run in background" though. 

 

Below is a copy of my system log which references Bitwarden but not rclone. 

 

Any ideas would be much appreciated. 

 

Quote

Aug 21 02:00:01 Tower root: Fix Common Problems Version 2020.08.02

Aug 21 02:00:16 Tower crond[1776]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

Aug 21 02:00:22 Tower atd[1233]: pam_unix(atd:session): session opened for user root(uid=0) by (uid=2)

Aug 21 02:00:22 Tower atd[1242]: pam_unix(atd:session): session opened for user root(uid=0) by (uid=2)

Aug 21 02:00:22 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/docker stop bitwardenrs

Aug 21 02:00:33 Tower kernel: veth0a6d94f: renamed from eth0

Aug 21 02:00:33 Tower kernel: br-4c0faae789bf: port 4(vethc0058e3) entered disabled state

Aug 21 02:00:33 Tower avahi-daemon[7581]: Interface vethc0058e3.IPv6 no longer relevant for mDNS.

Aug 21 02:00:33 Tower kernel: br-4c0faae789bf: port 4(vethc0058e3) entered disabled state

Aug 21 02:00:33 Tower avahi-daemon[7581]: Leaving mDNS multicast group on interface vethc0058e3.IPv6 with address fe80::e407:61ff:fea0:614.

Aug 21 02:00:33 Tower kernel: device vethc0058e3 left promiscuous mode

Aug 21 02:00:33 Tower kernel: br-4c0faae789bf: port 4(vethc0058e3) entered disabled state

Aug 21 02:00:33 Tower avahi-daemon[7581]: Withdrawing address record for fe80::e407:61ff:fea0:614 on vethc0058e3.

Aug 21 02:00:37 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/docker start bitwardenrs

Aug 21 02:00:37 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered blocking state

Aug 21 02:00:37 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered disabled state

Aug 21 02:00:37 Tower kernel: device vethb8183fb entered promiscuous mode

Aug 21 02:00:37 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered blocking state

Aug 21 02:00:37 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered forwarding state

Aug 21 02:00:37 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered disabled state

Aug 21 02:00:40 Tower kernel: eth0: renamed from veth5ec5971

Aug 21 02:00:40 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb8183fb: link becomes ready

Aug 21 02:00:40 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered blocking state

Aug 21 02:00:40 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered forwarding state

Aug 21 02:00:41 Tower atd[1233]: pam_unix(atd:session): session closed for user root

Aug 21 02:00:42 Tower avahi-daemon[7581]: Joining mDNS multicast group on interface vethb8183fb.IPv6 with address fe80::84ba:ecff:fe2a:e123.

Aug 21 02:00:42 Tower avahi-daemon[7581]: New relevant interface vethb8183fb.IPv6 for mDNS.

Aug 21 02:00:42 Tower avahi-daemon[7581]: Registering new address record for fe80::84ba:ecff:fe2a:e123 on vethb8183fb.*.

Aug 21 02:19:56 Tower atd[1242]: pam_unix(atd:session): session closed for user root

 

 

***EDIT - For reference, when I manually run the rclone script, the following is displayed in the system log;

Quote

Aug 21 12:56:38 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh /tmp/user.scripts/tmpScripts/rclone_custom_plugin/script
Aug 21 12:56:38 Tower atd[20671]: pam_unix(atd:session): session opened for user root(uid=0) by (uid=2)

 

Edited August 21, 2020 by LoneTraveler

[BRiT]

Rclone might not be in the default path, so try setting the path variable to include it before first calling rclone or try using absolute path to rclone on each line.

[ytddewqf]

51 minutes ago, BRiT said:

Rclone might not be in the default path, so try setting the path variable to include it before first calling rclone or try using absolute path to rclone on each line.

Hello, 

 

Thanks for the suggestion. Unfortunately, as this is all still quite new to me, I'm not entirely sure how to action this. Do you mean to place;

Quote

/boot/config/plugins/user.scripts/scripts/rclone_custom_plugin

...at the start of my rclone script? 

 

It's strange however that it runs fine manually and when I call the command via CLI, however not via the script? 

Edited August 21, 2020 by LoneTraveler

[BRiT]

No. Not to where the plugin is installed from, but where the rclone is installed to.

 

From an unraid terminal, type in the following command to see where it's installed to, such as /usr/local/bin/ or /usr/local/sbin/ .

 

which rclone

 

For example, which mover, returns /usr/local/sbin/mover .

[ytddewqf]

Ah got ya. It returns the following path;

Quote

/usr/sbin/rclone

 

So would each line now be formatted to something like this;

Quote

rclone/usr/sbin/rclone copy /mnt/user/nextcloud GoogleDriveBackupCrypt:/unraid/nextcloud

 

[BRiT]

Try:

 

/usr/sbin/rclone copy /mnt/user/nextcloud GoogleDriveBackupCrypt:/unraid/nextcloud

[ytddewqf]

Hi, 

 

Just checked the system log, unfortunately no sign of rclone running at 2am;

 

Quote

Aug 22 02:00:02 Tower root: Fix Common Problems Version 2020.08.02
Aug 22 02:00:07 Tower crond[1776]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Aug 22 02:00:12 Tower atd[7667]: pam_unix(atd:session): session opened for user root(uid=0) by (uid=2)
Aug 22 02:00:12 Tower atd[7676]: pam_unix(atd:session): session opened for user root(uid=0) by (uid=2)
Aug 22 02:00:13 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/docker stop bitwardenrs
Aug 22 02:00:23 Tower kernel: veth5ec5971: renamed from eth0
Aug 22 02:00:23 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered disabled state
Aug 22 02:00:24 Tower avahi-daemon[7581]: Interface vethb8183fb.IPv6 no longer relevant for mDNS.
Aug 22 02:00:24 Tower avahi-daemon[7581]: Leaving mDNS multicast group on interface vethb8183fb.IPv6 with address fe80::84ba:ecff:fe2a:e123.
Aug 22 02:00:24 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered disabled state
Aug 22 02:00:24 Tower kernel: device vethb8183fb left promiscuous mode
Aug 22 02:00:24 Tower kernel: br-4c0faae789bf: port 4(vethb8183fb) entered disabled state
Aug 22 02:00:24 Tower avahi-daemon[7581]: Withdrawing address record for fe80::84ba:ecff:fe2a:e123 on vethb8183fb.
Aug 22 02:00:28 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/docker start bitwardenrs
Aug 22 02:00:28 Tower kernel: br-4c0faae789bf: port 4(veth4994ab8) entered blocking state
Aug 22 02:00:28 Tower kernel: br-4c0faae789bf: port 4(veth4994ab8) entered disabled state
Aug 22 02:00:28 Tower kernel: device veth4994ab8 entered promiscuous mode
Aug 22 02:00:30 Tower kernel: eth0: renamed from veth95f4569
Aug 22 02:00:30 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4994ab8: link becomes ready
Aug 22 02:00:30 Tower kernel: br-4c0faae789bf: port 4(veth4994ab8) entered blocking state
Aug 22 02:00:30 Tower kernel: br-4c0faae789bf: port 4(veth4994ab8) entered forwarding state
Aug 22 02:00:31 Tower atd[7667]: pam_unix(atd:session): session closed for user root
Aug 22 02:00:32 Tower avahi-daemon[7581]: Joining mDNS multicast group on interface veth4994ab8.IPv6 with address fe80::fc1b:5eff:fe8a:78a4.
Aug 22 02:00:32 Tower avahi-daemon[7581]: New relevant interface veth4994ab8.IPv6 for mDNS.
Aug 22 02:00:32 Tower avahi-daemon[7581]: Registering new address record for fe80::fc1b:5eff:fe8a:78a4 on veth4994ab8.*.
Aug 22 02:22:14 Tower atd[7676]: pam_unix(atd:session): session closed for user root
Aug 22 03:00:16 Tower crond[1776]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Aug 22 04:00:02 Tower crond[1776]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Aug 22 04:23:57 Tower webGUI: Successful login user root from 192.168.1.64