richt 94 Posted December 2, 2022 Posted December 2, 2022 I recently set up a Linux Emby server 4.7.10.0 and have set a comskip post processing task. The task fails with a "No such file or directory" message. See attached log file "embyserver-63805568536.txt" at 2022-12-02 07:30:00.021 for an example of the raw error. I did a little creative troubleshooting by creating a script that contains this line. echo "$1" > /var/lib/emby/scripts/results.txt The result.txt file shows the {PATH} variable is getting truncated at the first space in the file path/name. This only happens on the stable version. The latest beta does not demonstrate this problem. This attempt is shown in the attached "embyserver.txt" log file. cat /var/lib/emby/scripts/results.txt /embydata/TVShows/Chicago Can you confirm this is an issue? Post Processing config: embyserver-63805568536.txt embyserver.txt
richt 94 Posted December 2, 2022 Author Posted December 2, 2022 Additional comments The problem does NOT occur in the Windows Emby 4.7.10.0 I installed the Scritper-X plugin and was able to get comskip to run correctly using the %recording.path% argument.
Solution Q-Droid 989 Posted December 2, 2022 Solution Posted December 2, 2022 Here's something odd. I have three releases, 4.7.1 - 4.7.9, and they all have the command line argument enclosed in quotes: "{path}". I didn't change it though that could explain why your value is truncated. Have you tried your echo test using $@ or adding more positional variables - $1 $2 $3...?
richt 94 Posted December 3, 2022 Author Posted December 3, 2022 Well it is definitely the little things that count. I changed it to "{path}" and all is working. Thanks for catching that! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now