Off-machine node fails with NO OUTPUT FILE PRODUCED when transcoding #362
Labels
bug
Something isn't working
Comments
|
Hi are you able to please try with this sample file? https://github.com/mediaelement/mediaelement-files/blob/master/big_buck_bunny.mp4 Your files may be copyright protected which HandBrake does not deal with. |
|
All my files are procured via usenet, so they shouldn't have any copyright protection. I also encountered the same error with Big Buck Bunny. Node Logs
|
|
Seems the path translators are not working on your node. In the Node log, I've updated the path translating in 2.00.05 - still in pre-release so you need to set the version manually in the Tdarr Updater config: Let me know if you still have the same issue, thanks. |
|
Thanks for the quick fix! There's no more path translation errors, but now the transcode doesn't seem to start at all on both the remote node and the node on the same machine: |
|
Turn on verbose logs on the Logs tab and then post the node and server logs when that issue happens. |
|
I deleted the directories with the binaries and ran the updater again, which fixed the problem of the transcode not starting. Now the off-machine node still reports that no output file was produced, however. Verbose Off-machine Node Logs
The file properties in the verbose object dump seem to indicate the path translation is being applied properly to the media directory, but not to the transcode cache. I should probably note I'm rolling my own plugins. Those worked fine on v1, but I'm not sure if I should be making any changes for v2. |
|
I have not seen this issue before. Perhaps you have a hidden character in the path translators Node config json file? You can check for hidden characters here: Perhaps try typing out the paths manually or paste your Tdarr_Node_Config.json file here |
|
I checked for hidden characters, but there's nothing but the usual carriage returns and line breaks. (Off-machine) Node Config {
"nodeID": "Parsec",
"nodeIP": "10.10.10.130",
"nodePort": "8267",
"serverIP": "10.10.10.6",
"serverPort": "8266",
"handbrakePath": "",
"ffmpegPath": "",
"mkvpropeditPath": "",
"pathTranslators": [
{
"server": "C:/TransCache/Television",
"node": "Y:/Television"
},
{
"server": "E:/Television",
"node": "X:/Television"
}
]
}Server and node config from the master machine {
"serverIP": "0.0.0.0",
"serverPort": "8266",
"handbrakePath": "",
"ffmpegPath": ""
}{
"nodeID": "Daphnis",
"nodeIP": "127.0.0.1",
"nodePort": "8267",
"serverIP": "127.0.0.1",
"serverPort": "8266",
"handbrakePath": "",
"ffmpegPath": "",
"mkvpropeditPath": "",
"pathTranslators": [
{
"server": "",
"node": ""
}
]
} |
HaveAGitGat
added
bug
|
I think I may have found the issue. Am I right in thinking you are using back slashes in the transcode cache path in the library settings? Try using forward slashes: I've fixed that for the next release. This was to do with the change allowing Windows UNC paths a few weeks ago. |
|
Chiming in: I have an almost identical issue when using a windows node connecting to the server (docker container) on a linux host. Also happen to be running 2.00.05. From reddit thread here: https://www.reddit.com/r/Tdarr/comments/lkw7ly/unable_to_get_a_win10_node_transcoding_with_a/ Windows Node Log: Output of that file from the webui: The odd / interesting part here is the line beginning: "/mediaz:/tv_shows_shows/" That's just not even close to the node config file (below), and appears to be some conflation of the server side docker mapping (/media/tv_shows) and the windows node config (z:\tv_shows). Is this related to this bug report, or should I be opening a new one? Windows node config: |
You are absolutely correct, switching the backslashes for slashes resolved my issue! Thank you so much for your time and effort. This may also extend to @Scaredycrow, it might work as expected using slashes rather than escaped backslashes in the node config. |
Note: This did not fix my issue, although forward slashes do now seem to work when mapping paths, the error on my end remains the same. |
Great :) Thanks for the help. |
Yours is a different issue. Please open a new issue if you're still having that problem, thanks. |
|
@Scaredycrow I have the same issue and have created a new issue (I didnt see you create one after your comments in this thread). Issue: #1132 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have a remote gaming server lying around that doesn't see much use, so I decided to put it to work transcoding my library alongside the media server itself. When issuing transcodes this node fails with a warning that no output file was produced. As per the docs I mapped the transcode cache and media share as a network drive on the node and I have verified I can read and write to both. The logs below seem to indicate that the path translation is not being applied, so I would suspect this is a configuration error on my end, or an issue with the path translators.
Node Logs
Server Logs
To Reproduce
Expected behavior
The off-machine node should translate the paths correctly so that it can read and write to the transcode cache and media library.
Screenshots
The screenshot below shows that the mapped network drives can be accessed as expected
Desktop (please complete the following information):
Server:
Node:
Additional context
Steps already taken:
The text was updated successfully, but these errors were encountered: