Metatagging questions (previous from the How To FAQ for tagging)

[roofuskit]

Sure, I'm not one to say no to documentation help (I suck at it, I'll be the first to admit). If you could do it up and do the pull request to the development branch, I can scope things out and get it in there Thanks!

How does one install pip and comictagger in pyenv?

[roofuskit]

Think i figured that part out. (switched shells to 2.7.9)

Now I got "there was an error"

and this is in the logs:

Code: Select all

16-Jul-2015 18:58:21 - INFO    :: CP Server Thread-9 : tagging : <sqlite3.Row object at 0x7f58a4f3ea70>
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] dirName:/media/Kevinmovies/Comics/Spider-Gwen (2015)
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] UNRAR path set to : /usr/bin/unrar
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Paths / Locations:
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] scriptname : Mylar.py
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] downloadpath : /media/Kevinmovies/Comics/Spider-Gwen (2015)
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] sabnzbdscriptpath : /opt/Mylar
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] comicpath : /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] unrar_folder : /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp/unrard
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Running the ComicTagger Add-on for Mylar
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Attempting to create directory @: /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Created directory @ : /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Filename is : /media/Kevinmovies/Comics/Spider-Gwen (2015)/Spider-Gwen 001 (2015).cbr
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] The path where the file is that I was provided is probably wrong - modifying it to : /media/Kevinmovies/Comics/Spider-Gwen (2015)/Spider-Gwen 001 (2015).cbr
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] moving : /media/Kevinmovies/Comics/Spider-Gwen (2015)/Spider-Gwen 001 (2015).cbr to /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp/Spider-Gwen 001 (2015).cbr
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Mylar.py: converting Spider-Gwen 001 (2015).cbr to be zip format
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] {0}: Comicpath is /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp/Spider-Gwen 001 (2015).rar
16-Jul-2015 18:58:21 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] {0}: Unrar is /media/Kevinmovies/Comics/Spider-Gwen (2015)/temp/unrard
16-Jul-2015 18:58:27 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Converted directory: /media/Kevinmovies/Comics/Spider-Gwen (2015)
16-Jul-2015 18:58:27 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Converted filename: Spider-Gwen 001 (2015).cbz
16-Jul-2015 18:58:27 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] Destination path: /media/Kevinmovies/Comics/Spider-Gwen (2015)/Spider-Gwen 001 (2015).cbz
16-Jul-2015 18:58:27 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] dirName: /media/Kevinmovies/Comics/Spider-Gwen (2015)
16-Jul-2015 18:58:27 - DEBUG   :: CP Server Thread-9 : [META-TAGGER] absDirName: /media/Kevinmovies/Comics/Spider-Gwen (2015)

It creates a cbz version in the temp directory then seems to die there. No metadata is added and it's never moved back.

[evilhero]

How are you trying to metatag the files? It doesn't look like it's from a normal post-processing run - from the group metatagging option?

Also need to know the build/commit of mylar you're running as a similar issue was fixed in the last few development commits.

If you run mylar from the command line instead of as a daemon and execute the metatagging request, is there any additional information that spits out in the console window?

[Kalinon]

How are you trying to metatag the files? It doesn't look like it's from a normal post-processing run - from the group metatagging option?

Also need to know the build/commit of mylar you're running as a similar issue was fixed in the last few development commits.

If you run mylar from the command line instead of as a daemon and execute the metatagging request, is there any additional information that spits out in the console window?

Resurrecting this post, i recently went through the steps to enable comictagger and start updating my libs. This issue is still present in the latest development branch:

Code: Select all

Latest commit efe447f on Nov 23, 2015

When using the Manual MetaTagging button it will randomly fail on a RAR conversion. It will move it to temp, but not move the zip back. Sometimes deleting the temp folder as well. Ive lost a few issues this way.

I found that switching to the following method works better to convert your files:

Code: Select all

/opt/mylar/comictagger.py --export-to-zip --delete-rar -R ./*

[evilhero]

Resurrecting this post, i recently went through the steps to enable comictagger and start updating my libs. This issue is still present in the latest development branch:

Code: Select all

Latest commit efe447f on Nov 23, 2015

When using the Manual MetaTagging button it will randomly fail on a RAR conversion. It will move it to temp, but not move the zip back. Sometimes deleting the temp folder as well. Ive lost a few issues this way.

I found that switching to the following method works better to convert your files:

Code: Select all

/opt/mylar/comictagger.py --export-to-zip --delete-rar -R ./*

I've seen this happen just recently myself - where if you did a manual metatagging, it creates the temp in the right directory, but when it goes to move the zip back it actually moves it back 2 levels up (so in the root of Comic Location), and then dies following due to not being able to physically locate the file in the expected location. If you happen to see the portion where it deletes the temp file after an unsuccessful conversion/move, can you try to gather the log for it? I'd like to see where it's failing exactly - whether in the move and not returning a failed response, or if it's deleting the temporary file even if it's already gotten the failed response from the move. I do have a patch coming for comictagger that fixes the problem with it failing on some systems (mainly those that don't have CT installed from what I can gather), but it patches it so it should work regardless of the system now at least.

I didn't know the export to zip command existed within CT - I'll have to check that out too

[evilhero]

Resurrecting this post, i recently went through the steps to enable comictagger and start updating my libs. This issue is still present in the latest development branch:

Code: Select all

Latest commit efe447f on Nov 23, 2015

When using the Manual MetaTagging button it will randomly fail on a RAR conversion. It will move it to temp, but not move the zip back. Sometimes deleting the temp folder as well. Ive lost a few issues this way.

I found that switching to the following method works better to convert your files:

Code: Select all

/opt/mylar/comictagger.py --export-to-zip --delete-rar -R ./*

Ok, in response to this and some others having issues (as well as myself today) - I've removed all of the cbr/cbz conversions that Mylar was doing, as well as the whole temp directory/moving/cd'ing thing. Now it just uses the command Kalinon posted above to export to zip, then runs the tagging commands on said issues. No more deleting files, folders that are temporary but not empty, or other problems - and I also added in a bunch of checks that should now ensure that everything runs abit more smoothly especially when dealing with types of errors.

This will be in the next development commit, along with a whack of other stuff as well as the general patch to get comictagger working on some systems (it had stopped working for some).

[dbznokia]

Have I got this set up correctly because post processing keeps failing for me: http://imgur.com/a/OQBzn

Code: Select all

ll /usr/local/lib/python2.7/dist-packages
total 52
drwxrwsr-x 10 root staff 4096 Aug  5 11:48 ./
drwxrwsr-x  4 root staff 4096 Jul 27 21:39 ../
drwxr-sr-x  3 root staff 4096 Jul 29 17:37 backports/
drwxr-sr-x  2 root staff 4096 Jul 29 17:38 beautifulsoup4-4.5.0.dist-info/
drwxr-sr-x  4 root staff 4096 Jul 29 17:38 bs4/
drwxr-sr-x  2 root staff 4096 Jul 29 17:38 comictagger-1.1.15b0.egg-info/
drwxr-sr-x  5 root staff 4096 Jul 29 17:38 comictaggerlib/
drwxr-sr-x  2 root staff 4096 Jul 29 17:37 configparser-3.5.0.egg-info/
-rw-r--r--  1 root staff  314 Jul 29 17:37 configparser-3.5.0-nspkg.pth
-rw-r--r--  1 root staff 1508 May 21 16:56 configparser.py
-rw-r--r--  1 root staff 1870 Jul 29 17:37 configparser.pyc
drwxr-sr-x 10 root staff 4096 Jul 29 17:37 pip/
drwxr-sr-x  2 root staff 4096 Jul 29 17:37 pip-8.1.2.dist-info/

Code: Select all

ll /usr/local/bin
total 20368
drwxr-xr-x  2 root root     4096 Aug  3 18:51 ./
drwxr-xr-x 10 root root     4096 Jul 27 20:57 ../
-rwxr-xr-x  1 root root       94 Jul 29 17:38 comictagger.py*
-rwxr-xr-x  1 root root 20828512 Aug  3 18:51 nzbget*
-rwxr-xr-x  1 root root      204 Jul 29 17:37 pip*
-rwxr-xr-x  1 root root      204 Jul 29 17:37 pip2*
-rwxr-xr-x  1 root root      204 Jul 29 17:37 pip2.7*

[evilhero]

Unless you're running another script after post-processing, you don't need to have 'Extra scripts After' enabled pointing to the bin dir. Just leave metatagging enabled as you have it, disable the extra scripts part and it should be good to go.

Mylar uses the included comictagger, as it has enhancements and some improvements over the last official release - so you cannot change it out and expect things to work, because they won't