Page 1 of 1
Failed status in sbanzbd
Posted: 05 Sep 2016, 06:57
by saitoh183
I created a cmd file to call FB for post-processing. The script runs fine and completes the rename and file movement but the status in the sabnzb history still says failed.
My FB script moves the file to my Google Drive which is mounted as a local drive using Netdrive 2
As you can see it says done in green...but followed by some weird characters...
Here is the log:
Code: Select all
C:\Program Files (x86)\SABnzbd>filebot.launcher -script fn:amc --def seriesFormat="D:/Videos/tv/{n}/{'Season '+s}/{n} - {sxe} - {t}" --action move -non-strict P:/usenet/tvshows --log-file tv.log --def clean=y --db TheTVDB --def ut_label=TV -no-xattr
Locking C:\Windows\System32\config\systemprofile\AppData\Roaming\FileBot\logs\tv.log
Run script [fn:amc] at [Sun Sep 04 08:37:51 EDT 2016]
Parameter: seriesFormat = D:/Videos/tv/{n}/{'Season '+s}/{n} - {sxe} - {t}
Parameter: clean = y
Parameter: ut_label = TV
Argument: P:\Usenet\tvshows
Input: P:\Usenet\tvshows\Aquarius.2015.S02E10.HDTV.x264-FLEET\Nrkq7POK9F741AuaCF09FkG.mkv
Exclude: P:\Usenet\tvshows\Aquarius.2015.S02E10.HDTV.x264-FLEET\66764662.txt
Group: [tvs:aquarius 2015] => [Nrkq7POK9F741AuaCF09FkG.mkv]
Rename episodes using [TheTVDB]
Auto-detected query: [Aquarius 2015]
Fetching episode data for [Aquarius (2015)]
[MOVE] Rename [P:\Usenet\tvshows\Aquarius.2015.S02E10.HDTV.x264-FLEET\Nrkq7POK9F741AuaCF09FkG.mkv] to [D:\Videos\tv\Aquarius (2015)\Season 2\Aquarius (2015) - 2x10 - Blackbird.mkv]
Processed 1 files
Clean clutter files and empty folders
Delete P:\Usenet\tvshows\Aquarius.2015.S02E10.HDTV.x264-FLEET\66764662.txt
Delete P:\Usenet\tvshows\Aquarius.2015.S02E10.HDTV.x264-FLEET
Done Òâ¥(´~áÔîÆÒâ~ÔîÆ´~á)ÒâÄ
Re: Failed status in sbanzbd
Posted: 05 Sep 2016, 16:10
by rednoah
FileBot is working fine, and seems to have finished it's task succesfully. Your console encoding is off though. Also, the GUI launcher doesn't have a console so the fact that you get output at all is strange.
This is clearly about how to integrate 3rd party tools with sabnzb, so you should ask the sabnzb developers for some docs on that.
Re: Failed status in sbanzbd
Posted: 05 Sep 2016, 21:47
by saitoh183
I guess I will have to check with another script. Also check encoding
Re: Failed status in sbanzbd
Posted: 06 Sep 2016, 13:29
by saitoh183
On a side not...should i use filebot launcher or just filebot in the script?
Re: Failed status in sbanzbd
Posted: 06 Sep 2016, 14:21
by rednoah
If you use the MSI installer, then filebot.exe will be the suitable command-line executable.
Re: Failed status in sbanzbd
Posted: 06 Sep 2016, 18:25
by saitoh183
Thanks,
And just a FYI about the initial issue, it was related to Filebot...it was the ヾ(＠⌒ー⌒＠)ノ at the end of the log file that was generating the error.
https://forums.sabnzbd.org/viewtopic.ph ... 26#p108024
Using the latest RC4
Re: Failed status in sbanzbd
Posted: 07 Sep 2016, 00:39
by rednoah
1.
This log message will only be printed when you pass in --log ALL (default) so you could just define your own log level that is higher, for example FINE or INFO.
2.
If sbanzbd can't deal with ヾ(＠⌒ー⌒＠)ノ printed to console, then you may will have similar issues when FileBot logs unicode filenames to the console.
Re: Failed status in sbanzbd
Posted: 08 Sep 2016, 11:43
by saitoh183
1. Ok... Good to know
2. Well the latest RC of sab works and and i didnt see the problem with any other Unicode files.
Re: Failed status in sbanzbd
Posted: 08 Sep 2016, 14:04
by saitoh183
Actually...i do see the same odd unicode problem when i use the script in a cmd window. Btw im on W2012 R2 Std
Re: Failed status in sbanzbd
Posted: 08 Sep 2016, 14:11
by rednoah
Looks like FileBot is using UTF-8 encoding and Windows CMD is interpreting the bytes with Windows-1252 encoding.
I'm not sure that CMD can display Unicode characters at all actually. If you pipe the output to a text file and then look at it with good Editor you'll probably see that it looks just fine.
Re: Failed status in sbanzbd
Posted: 08 Sep 2016, 14:57
by saitoh183
rednoah wrote:Looks like FileBot is using UTF-8 encoding and Windows CMD is interpreting the bytes with Windows-1252 encoding.
I'm not sure that CMD can display Unicode characters at all actually. If you pipe the output to a text file and then look at it with good Editor you'll probably see that it looks just fine.
Yup it does look good in the log file. Well its all good, i added the --log Fine and no more issues. Thanks Rednoah...you always dive great support
