Closed Slugger closed 4 years ago
Thank you for logging this issue, I'll look into it right now.
I have tested baseline with windows, and scheduled task operations work, ie
Scheduled Task Run on MediusDev2 - embyver: 4.4.3.0 - scripterxver: 3.0.3.1
I'm now downloading a fresh copy of ubuntu to install in a VM to test fresh environment, I just need to catch what exactly was null at that point, because the exception is thrown because some value is null;; I'll find it though, without a doubt :)
So far on a fresh ubuntu install I am not able to replicate the issue, which is very unfortunate, but I want to figure this one out for you.
Which operating system and version are you using mate?
Ubuntu latest:
cripterx@ubuntu:~/Emby/Scripts$ tail scheduledtask.log
onScheduled Task called - [Server Name: ubuntu] [Server Version: 4.4.3.0] [ScripterX Version: 3.0.3.1] scripterx@ubuntu:~/Emby/Scripts$
Running Emby in a docker on Debian 10. Using this docker image: https://hub.docker.com/r/linuxserver/emby
Thank you @Slugger I'll see if I can replicate it now.
Hi mate, so I have installed a fresh copy of Debian 10 in a virtual machine. I've installed docker, pulled the image you specified, created a container and ran it.
I've installed ScripterX and configured authFailed and ScheduledTask, and all are working as per:
anthony@embydocker:/media/scripts$ ls authfail.log auth_fail.sh scheduledtask.log scheduledtask.sh anthony@embydocker:/media/scripts$ pwd /home/anthony/media/scripts
The docker create command I used:
docker create \
--name=emby \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Australia/Sydney \
-e UMASK_SET=022 #optional
\
-p 192.168.29.132:8096:8096 \
-p 192.168.29.132:8920:8920 #optional
\
-v /home/anthony/media:/config \
-v /home/anthony/media/tv:/data/tvshows \
-v /home/anthony/media/movies:/data/movies \
-v /home/anthony/media/transcode:/transcode #optional
\
-v /home/anthony/media/scripts:/data/scripts \
-v /opt/vc/lib:/opt/vc/lib #optional
\
--restart unless-stopped \
linuxserver/emby
The configuration for onAuthenticationFailed:
The configuration for onScheduledTask:
The scripts:
auth_fail.sh: echo Authentication Failed: Device: $1 - Username: $2 >> /data/scripts/authfail.log
scheduledtask.sh: echo Scheduled Task Called: Server Name: $1 - >> /data/scripts/scheduledtask.log
Outputs respectively (the contents of the .log files):
authfail.log: Authentication Failed: Device: Firefox - Username: anthony
scheduledtask.log: Scheduled Task Called: Server Name: sxdocker -
edit: I also tried run with bash too, instead of /bin/bash and it still worked.
I'm not running the latest docker image so I guess I'll try upgrading to that and see if that fixes it and will report back.
No problems mate, thank you for that :)
Upgraded to the latest emby docker image and all seems to be working good now. I was running 4.4.2 so not like it was that old a version, but I guess just old enough. Thanks.
Describe the bug Fresh install on Linux. Setup one event to test: onScheduledTask. Trigger the scheduled task from Emby dashboard and nothing happens.
To Reproduce Steps to reproduce the behavior:
Expected behavior The configured script to execute when the scheduled task is triggered I also tried setting up other events (Auth failed, etc.) and triggered those events in Emby but the script was never triggered by the plugin.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information): n/a
Additional context